Demo agent: in view, legible, and quicker - #103
Open
jpcamara wants to merge 3 commits into
Open
Conversation
A bar pinned under the page header shows what the agent is doing, with a "jump to it" link and a follow switch that keeps its cursor in view as it moves, held for a few seconds after you type. Buttons put the things you can say on a new line at your caret. The agent introduces itself when it arrives and says "up next" before each task. The review and the first task now run at the same time: each is a StreamJob, a model stream paced and stepped by the watch loop, so text appears seconds after the invite rather than after the review. One status names everything in flight so the ledger does not flicker. Quick calls, the decision after a change and answers, go to a model without a reasoning phase (AGENT_FAST_MODEL, default MiniMax M3 on Fireworks, about two seconds); reviews and drafts keep the reasoning model. A change is only weighed once the sentence reads finished or the person has left it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017TeaovH2jyHARHJSyQ8Afo
…y under headings The pacer accrued credit while the model was silent, so the first chunk after a think paid out the whole wait at once. Credit now starts when text arrives; the first writes after a pause are a few characters. Follow holds for fifteen seconds after any typing, key, click or scroll, not four seconds after typing only, and selection changes do not count, since remote edits move the selection too. On the markdown page it compares the agent's resolved index, since the relative position it sends stays on the same character while it writes. On the Lexxy page only a heading names the agent's task list, and its own review section never does: a paragraph mentioning the agent had turned the review's suggestions into tasks and a mark landed inside one of them. Answers are brief (two or three sentences), go out at a brisker pace than drafts, and never become headings. A task handed over while it is busy says what it will start after. The instructions tell the model that a "[~]" task's section may end mid-sentence because it is being written. And a draft-this-section request with the caret still in the heading no longer crashes the work loop. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017TeaovH2jyHARHJSyQ8Afo
…are brief Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017TeaovH2jyHARHJSyQ8Afo
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.
Stacked on #102.
Three complaints from using it: the agent was often off screen, it was unclear how to interact with it or what it would do next, and too much time was spent waiting.
In view
EditorView.scrollIntoViewdoes the rest.Legible
@agent pause.Quicker
StreamJob: a model stream with its own pacer, stepped by the watch loop, so several run at once and the loop keeps reacting. The review and the first task from the list start together at the invite; draft text appears two to three seconds after the invite. While both run, one combined status ("writing a review and drafting Rollout") keeps the ledger and the bar from flickering, and the caret stays with the draft.AGENT_FAST_MODEL, defaultaccounts/fireworks/models/minimax-m3(2.4s to first token on the decision prompt, clean JSON;gpt-oss-120balso works). Reviews and drafts keep the reasoning model. Measured with the real models: a decision landed 3s after a sentence ended, against 20s before.Verified
@agentat the caret and the answer arrives.