Add lightweight update_plan tool - #19
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.
Summary
Adds a lightweight side-effect-free
update_plantool so LocalAgent can track and display multi-step work during an active run.What changed
Added an
update_planbuiltinSupports plan item states:
pendingin_progresscompletedRejects plans with more than one
in_progressitemKeeps bounded in-memory plan state on the agent
Emits
PlanUpdatedeventsAdds compact log summaries for plan updates
Renders the current plan in the chat TUI when present
Renders plan updates in the standalone event tail
Why
LocalAgent now has much better shell lifecycle behavior after recent PRs:
The next major opencode-style UX gap is structured task visibility. This PR gives the agent and user a shared view of the current plan without introducing heavy DAG/taskgraph orchestration.
Scope boundaries
This PR intentionally does not:
taskgraph.rsValidation
cargo fmt --checkcargo clippy --all-targets -- -D warningscargo test --libcargo test --test tool_call_accuracy_cicargo test --test artifact_goldenpython scripts/ci_release_readiness.pycargo testAll validation passed locally.
Follow-ups