Tianyi Cui
57885bd73d
Preserve system/message persistence while adopting named persona prefix/suffix and environment facts after reusable instructions. Resolve the Web assertion against the logged system message, not retired header.system. Keep the existing protected V3 integration PR as the root publication path; no rules are bypassed.
description, kind
| description | kind |
|---|---|
| Package map for the plan group: the plan-mode feature that guides the agent to explore and design before executing, for users and maintainers navigating the group. | package-group |
plan/ — plan collaboration state
English | 中文
Summary
The plan/ group provides plan mode: while it is active, the agent explores and designs before executing, guided by instructions the deployment writes, and presents the finished plan for your approval before carrying it out. You can enter and leave plan mode with the /plan command and approve the plan or send the agent back to keep planning. Plan mode guides rather than restricts: every tool stays available, and limits such as sandbox mode and approval prompts are configured separately. The group contains one package, plan-mode.
Table of Contents
Packages
One package provides the whole plan-mode feature; the subsystem reference owns the exhaustive contracts.
| Package | Role | ctx key |
|---|---|---|
plan-mode/ |
Provides plan mode: /plan enters and leaves it, deployment guidance steers the agent while planning, and exit_plan_mode presents the finished plan for your review |
ctx.planMode |
Related documentation
Start with the subsystem reference for the shared vocabulary, then read the design note for the decisions.
- Plan mode subsystem reference — how plan mode works, its configuration, and the exit tool's behavior.
- Plan-specific collaboration state — the design decision behind plan mode.
Dev Note
Working context for maintainers — click to expand
None.