Files
deepseek-harness/packages/plan
Tianyi Cui 54bc084e5d Merge refreshed schema DSL into canonical tool output
# Conflicts:
#	docs/config-catalog.md
#	examples/headless-agent/tests/snapshots/advanced-toolchain/session.1.jsonl
#	examples/headless-agent/tests/snapshots/advanced-toolchain/session.2.jsonl
#	examples/headless-agent/tests/snapshots/advanced-toolchain/session.jsonl
#	packages/context/workspace-context/tests/workspace-context.spec.ts
#	packages/core/tools/tests/tools.spec.ts
#	packages/ui/tui/src/index.ts
#	packages/ui/tui/tests/tui.snapshot.ts
2026-07-22 21:31:16 +08:00
..

plan/ — plan collaboration state

Plan mode is one logged, per-agent collaboration state. It is a single product package, not a generic mode registry or a capability-seam trio.

Package Role ctx key
plan-mode/ plan/mode vocabulary + fold, boundary-applied state, the plan:policy guidance section, /plan [message], and the model-facing exit_plan_mode review tool ctx.planMode

The active state is a pure function of the session log, so resume and fork restore it without extra machinery. The deployment supplies plan instructions through Cordis config, while exit_plan_mode stays registered when planning is inactive to keep the request tool catalog stable. ACP maps this capability onto its generic default / plan picker; sandbox mode and approval policy remain independent enforcement settings. Design: plan-mode Agent Note and plan-specific state simplification.