Keep Code Context follow-up watch active - #22
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.
Summary
After answering one follow-up Code Context round, coding agents could post a completion response and stop pulling, so a later round on the same TRD required the user to say
continue. The helper also treated every terminal round as a reason to stop.The skill now keeps the same agent turn alive for follow-up rounds, continues pulling with the original request code, follows the server-provided
next_action, and reports the transition from context collection to answer preparation. Pre-create rounds still stop when TRD creation owns the next step.Privacy and compatibility
Activity reports contain only round id, revision, and phase. No repository content is added. The helper retains fallback behavior for servers that do not yet return
next_action.Requires the lifecycle contract in getdoable/trd#476 and the MCP activity tool in getdoable/doable-mcp#16.
Verification
node --test tests/doable-code-context-helper.test.mjs(2 passed).doable/state included