feat: the live queue serves the whole instance - #84
Merged
Conversation
The file browser is its own session and every ref gets one, and a reader asking on one session while the only agent sat parked on another left both waiting forever. The queue, the listeners and the page's "listening" answer are now instance-wide: the request names its thread, so whichever agent is parked here takes it. Waiting and working stay per session — they describe the requests a page can see. WIP toward #51 — not yet reviewed or pushed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bwp5QefjsjMFeq6CK6cT6w
…and resolution The queue became instance-wide but the agent's thread commands still refused a thread outside the agent's own session, so a request claimed from another session could be received and not answered. Threads are addressable across the instance now; tours stay with their session. The cross-session claim test puts its thread on a second session, as its comment always said, and a CLI test replies to and resolves a thread from another session. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bwp5QefjsjMFeq6CK6cT6w
fiddur
changed the title
… on stderr Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bwp5QefjsjMFeq6CK6cT6w
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #51.
The file browser is its own diffity session and every ref gets one. A reader asking a question on one session while the only agent sat parked (via
diffity-live) on another left both waiting forever: the parked agent never saw the request, and the reader never got an answer.The live queue, its listeners, and the page's "listening" answer are now instance-wide: the request names its own thread, so whichever agent is parked anywhere on this instance takes it. Waiting and working counts stay per session, since they describe the requests a given page can see.
Self-review found the other half missing and fixed it: the agent's
reply,resolveanddismissrefused a thread outside the agent's own session, so a request claimed from another session could be received but not answered. Threads are addressable across the instance now; tours stay with their session. A CLI test covers reply and resolve on a thread from another session, and the cross-session claim test now really uses two sessions.Bumps to 0.10.14.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Bwp5QefjsjMFeq6CK6cT6w