Repository navigation
feat(planning): auto-check plan steps using turn file change summaries #10
Description
Context & Background
In OpenCode upstream commit 81d57087a4 (feat(session-ui): summarize each turn's changed files (#55064)), OpenCode added automated detection and summarization of all files added, modified, or deleted within each turn.
In our fork ecosystem, agents generate structured execution plans with checklist items (- [ ] 1. Scaffold API routes, - [ ] 2. Update UI component) via /plan or the plan-tracking skill, which are displayed in OpenChamber's Project Knowledge Plans view. Currently, agents must manually read their plan markdown file and edit the checkboxes (- [x]) by invoking file tools. If an agent forgets to update the checklist after editing files, the plan's progress indicator remains stale.
Feature Objective
Automatically update and infer plan step completion using turn file change summaries:
When an agent turn concludes with file changes matching the files or scopes referenced in a plan step, automatically suggest or check off the corresponding plan step in Project Knowledge (openchamber_knowledge / .openchamber/plans/), keeping plan progress continuously accurate.
Technical Specifications
1. Turn File Changes Event & Hook
- Upstream emits turn change summaries in
packages/core/src/session//packages/session-ui/. - In
packages/core/src/session/subagent-completion.tsor post-turn hooks inpackages/core/src/plugin/supervisor.ts:- Extract the list of files touched in the turn:
{ added: string[], modified: string[], deleted: string[] }.
- Extract the list of files touched in the turn:
2. Plan Step Scope Matcher in plan-tracking
- In
packages/core/src/plugin/skill/plan-tracking.mdand related plan parsing helpers:- If a plan step specifies target files or directories (e.g.
Implement routes in packages/web/server/routes.jsorAdd tests in packages/core/test/): - When all referenced files for that step have been modified/created in recent turns:
- Automatically check off the step (
- [x]) in the active plan file or mark it as completed. - If the plan is stored via
openchamber_knowledge, invokeknowledge.save(kind: 'plan', ...)with the updated checklist markdown.
- Automatically check off the step (
- If a plan step specifies target files or directories (e.g.
3. Agent Confirmation & Notification
- When a step is automatically checked off:
- Include a lightweight notice in the turn timeline (e.g.,
Plan step 2 checked off: Implement routes). - Allow the user or agent to uncheck or adjust if the step was only partially completed.
- Include a lightweight notice in the turn timeline (e.g.,
Key Files & References
packages/core/src/session/runner/step.ts: Turn completion, diff detectionpackages/core/src/plugin/skill/plan-tracking.md: Agent plan tracking workflow instructionspackages/core/src/tool/plugin/plan-info.ts: Plan information and update tool- OpenChamber Project Knowledge plans:
packages/web/server/lib/openchamber-control/project-knowledge.js
Acceptance Criteria
- The system extracts file modification summaries at the end of each turn.
- When modified files satisfy the targets of a plan step, the step is marked complete (
- [x]) in the plan markdown file. - OpenChamber's Project Knowledge Plans tab reflects the updated step completion count (e.g.
3/5 Done). - Unit tests in
packages/core/test/verify automated step matching against simulated file changes.
Activity
dezren39 commentedon Oct 27, 2026
Intake review
Still live (verified this run): no plan-step auto-checking exists in the session/turn code on current main (no plan integration found under
packages/core/src/session/) — plan checkboxes still move only when an agent edits them by hand, as filed.Related: this is the opencode half of a cross-repo feature — the plans themselves live in OpenChamber's Project Knowledge (
.openchamber/plans/); per the cross-repo set rule, implementation should be tracked from one origin issue with the OpenChamber side referenced, not re-filed. opencode #6–#9 are the sibling fork-feature specs from the same filing batch (no technical dependency).Notes / risks: priority low, effort/l. The main risk is false positives: checking a step because a turn touched a file the step merely mentions would make the progress indicator less trustworthy, not more — the filing's "suggest or check off" wording should resolve to suggest-first (or check only on strong matches) in the design. Also depends on the fork carrying upstream's turn file-change summaries (commit 81d5708) — confirm that is in this fork's base before designing the hook.
Suggested approach: verify the upstream turn-summary event exists in the fork, prototype matching (exact path > directory scope > keyword) in suggest-only mode, and measure precision against a few real plans before enabling auto-check.
— fleet monitor intake (repo-fleet-monitor, 2026-10-26 20:19 CDT run)
dezren39 commentedon Oct 28, 2026
Triage verdict: gap confirmed, but not routable as an opencode small fix — needs a design decision (queue task 2044)
Verified on current main
b0633cc697760085022fb5656ed92fac9ce49b9c(2026-10-28):git grepforcheckbox,- [x],auto-checkacrosspackages/core/srcreturns zero hits, and there is no plan integration underpackages/core/src/session/.plan-trackingskill (packages/core/src/plugin/skill/plan-tracking.md) and theplan_infotool (packages/core/src/tool/plugin/plan-info.ts, backed byModelPlan) track model/subscription plans — quotas, tiers, pool purposes. They have nothing to do with execution-plan checklists (- [ ] 1. Scaffold API routes).openchamber_knowledgeor.openchamber/plansanywhere underpackages/. Per the intake note, those plans live in OpenChamber's Project Knowledge — so this is a cross-repo feature whose data store, step-scope matching semantics, and suggest-vs-auto-check behavior are all undecided design questions, not a bounded fix.packages/session-ui/src/timeline/file-changes.stories.tsx;rows-current.test.ts: a turn's summary diffs from its opening prompt and lists changed files, empty turns get none).Routing: no follow-up packet enqueued — a small_fix here would have to invent the plan store and the matching rules. This issue stays open as the cross-repo set origin (opencode + openchamber), marked
status/blockedpending a design decision: (a) where execution plans live and who owns parsing them, (b) explicit file targets in steps vs inferred matching, (c) suggest-first vs auto-check. Once that's decided, the opencode slice (turn-summary hook emitting touched files) is small and can be packeted from here.dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
repo-worker-opencode), OpenChamber scheduled laneplan_infotracks provider/model quota plans; no execution-plan store or step parser exists here.94939076d9969770f942e2c6c8ee0f289b3da2e3; prior triage comment #6477953912dezren39 commentedon Nov 3, 2026
Current-main triage: blocked on design decisions
Verified on
main94939076d9969770f942e2c6c8ee0f289b3da2e3(2026-11-03). The coverage packet says “status/blocked with no recorded blocker,” but the existing 2026-10-28 triage comment already named the unresolved design decisions; that comment remains accurate.packages/core/src/plugin/skill/plan-tracking.mdandpackages/core/src/tool/plugin/plan-info.ts/packages/core/src/model-plan.tsare for provider subscriptions, quota windows, model tiers, and pool purposes — not execution-plan checklists..openchamber/plans/openchamber_knowledgeintegration exists underpackages/on current main.packages/session-ui; there is no plan integration in the OpenCode session code. No matching open PR was found.Drew decision needed before implementation:
This is a cross-repo product/design decision, not a bounded small fix. I did not invent a store, matching rules, or automatic user-facing behavior. Task 7032 is blocked as
escalated-to-user; issue labels areuser/escalated,queue/blocked,status/blocked.🤖 Agent note · escalated / blocked
repo-worker-opencode), OpenChamber scheduled lane94939076d9969770f942e2c6c8ee0f289b3da2e3