Skip to content

feat(code): add persistent plans and scoped workspace discovery - #776

Merged
blakebauman merged 4 commits into
mainfrom
feat/code-workflow
Nov 15, 2026
Merged

blakebauman merged 4 commits into
mainfrom
feat/code-workflow

Conversation

@blakebauman

@blakebauman blakebauman commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Summary

code now 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.

  • Version the bundled manifest as 1.1.0 and enable the existing deep pattern's plan tools.
  • Add read-only local_info and local_instructions declarations, compatibility fallbacks for older clients, and guidance for reconciling concurrent edits and partial moves.
  • Cover plan recovery across separate durable runs, plan-mode client dispatch/refusal, and the complete API/TUI capability → instructions → approved command flow.

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 code turns 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

/work opens 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: code 1.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: /work in the terminal combines recorded operations, command attempts, and latest plan progress across continuation turns without invoking the model or changing project files.

Fixed

  • Coding plan mode: local inspection tools can run while writes and shell commands remain blocked until plan approval.

Gates run

Targeted harness coding/permission/plan tests: 58 passed
ruff check: All checks passed!
ruff format --check: 2 files already formatted
bundle-manifests --strict: validated 19 manifests
Real API/durable-worker/TUI smoke: passed=true, model_calls=4, vendor_calls=0, tui_exit_code=0

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)

@blakebauman
blakebauman merged commit 380f420 into main Nov 15, 2026
22 checks passed
@blakebauman
blakebauman deleted the feat/code-workflow branch November 15, 2026 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant