Repository navigation
feat(code): add persistent plans and scoped workspace discovery - #776
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
codenow tracks multi-step work with persisted plans and discovers the connected client's workspace, shell support, and applicable repository instructions before editing. Plan mode permits these inspections while continuing to block file changes and commands.local_infoandlocal_instructionsdeclarations, compatibility fallbacks for older clients, and guidance for reconciling concurrent edits and partial moves.Evidence re-verified at HEAD
The prior manifest could not use local read tools in plan mode and could not query client capabilities or retrieve scoped repository instructions. Authenticated HTTP tests exercise the actual compiler, governance wrappers, client bridge, and durable worker using scripted models.
Release scope
Keep the coding manifest, persisted plans, workspace capabilities/instructions, concurrent-change protections, and TUI results summary in the same release. Finish the coding feature work before rollout; an intermediate production deployment is not a prerequisite for further implementation. Companion-first deployment order, if needed, is within that shared release window. No staging environment is assumed.
Coding results summary
Completed
codeturns now show observed file operations, completed commands, issues, unconfirmed operations, and remaining plan steps. The summary never infers passing tests from model prose, keeps failed retries visible, and does not count pending approvals or missing results as completed work. Other agents retain their existing layout.Validation of the summary-only changes in an isolated checkout: 405 TUI tests passed, type checks and build passed. The real API/durable-worker/TUI smoke passed with
coding_summary_verified: true, four scripted calls and zero vendor calls. Concurrent UI and sandbox changes in the shared checkout were excluded from this update.Cross-turn coding report
/workopens a read-only report from loaded thread history in the existing pager. It combines recorded file operations and command attempts across continuation turns, keeps failed attempts visible after retries, and shows unfinished steps from each plan's latest observed state. It does not infer checks from model prose or fetch a live Git diff. The command makes no model call and changes no project files; the pager uses a private temporary report file. Large sections are bounded with an explicit remainder count, and control bytes in labels are neutralized.The isolated follow-up passed 410 TUI tests, type checks and build. The real API/durable-worker/TUI smoke passed with
coding_work_report_verified: true, four scripted model calls, zero vendor calls, and a clean exit. This remains part of the same coding release and the same two PRs.Changelog
Added
Coding workflow:
code1.1.0 records persisted plans and discovers client capabilities and scoped repository instructions through new read-only client tools.Coding results: completed terminal coding turns summarize tool-observed file operations, commands, issues, unconfirmed results and unfinished plan steps.
Coding work report:
/workin the terminal combines recorded operations, command attempts, and latest plan progress across continuation turns without invoking the model or changing project files.Fixed
Gates run
Production manifest validation and git diff whitespace checks also pass. The audit records the implementation, evidence, compatibility, and filesystem limits.
Not verified
The full harness suite and production deployment were not rerun for this manifest-only runtime change. The isolated smoke uses memory stores and a scripted model; it does not verify separate-process Postgres/Redis crash recovery or live model behavior.
Companions
Companion: felix-run/web#680
The companion client PR implements both new tools and the concurrent-change protections described in the manifest. Deploy the companion first; older clients fall back to existing file tools when a new tool is unknown. No mandatory configuration, database migration, or staging environment is required.
Felix-Thread: not applicable (human-directed Codex work)