Erik Bjäreholt

Yeah this is kind of a bug, althought doesn't really impact normal use (unless you look at data that isn't AFK filtered). It's ultimately a side-effect of switching to event-based...

I think this is the intended sort order, as both aw-server-rust and aw-server-python (I checked) returns it this way. Vaguely remember doing it that way for some reason, I think...

Sorry I completely missed this very thoughtful question. Do you still need help with these? Happy to provide pointers. I can quickly say that (1) API browser not available with...

No worries, thanks for doing the work! Happy to review the deb build scripts you did write, even if they are not ready for prime time :)

Seems to be yet another duplicate of https://github.com/MatthieuBizien/roam-to-git/issues/47 I've apparently also had the same issue for 4 months (last commit).

In my case it seems to have been caused by logging in with Google (again) making it not possible to login with password. Resetting the password fixed it.

Got rid of the use of `get_tools` in prompt-generation in https://github.com/gptme/gptme/pull/503, now passing down `tools: list[ToolSpec]`.

Made the config and loaded tools globals into thread-locals in https://github.com/gptme/gptme/pull/506 Attempted switching from thread-locals to using context vars in https://github.com/gptme/gptme/pull/507 (mostly to improve typing, but some tests are failing...)

This issue is largely solved. Some rough edges remain, but far from as many as before.

I want you to review how this relates to the existing RAG functionality as well as the gptme-rag repo/codebase. You have committed some md files in places where they don't...