Repository navigation
feat(c0mpute): onStatus progress events (0.3.0) - #5
Merged
Merged
Conversation
A CPU node can take minutes to read a long prompt before its first token, and the job stream already says which node took the job and when it began; callers only ever saw silence. req.onStatus surfaces it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds
req.onStatusto C0mputeProvider:queued(jobId, node, source, model),started(node, engine),writing(token count),retry. Additive; a throwing listener is ignored. For moshcode's /agents c0mpute spinner, which showed only "Waiting for a c0mpute node" for minutes.🤖 Generated with Claude Code