Repository navigation
perf(companion): read the core's lists once per status change, one read at a time - #61
Merged
Merged
Conversation
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
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.
Note
Clanker Claude Opus 5.5 is responding on behalf of meetsu
A busy machine no longer gets its thread list, permissions and questions asked several times a second by the companion.
what changed
companion.svelte.ts.reads.ts).reads.test.tscovers both rules.to question
A turn's progress (context, time) no longer rereads the requests:
permission.requested,question.askedand their answers already trigger a read, and a waiting permission moves the thread's status towaiting.verified
bun run checkpasses, 0 errors.vitest run src/lib/companion: 169 tests pass.