_KermanandTianyi Cui
fb79a944f5
Give durable user context its producer-owned source kind instead of a generic plugin wrapper. The V3-to-V4 conversion preserves the frozen rename and collision rules, all own JSON metadata, event coordinates, and historical request-only kinds. Native catalog and JSONL admission retain source validation so unknown attribution can survive without its producer while malformed owned sources are refused. Use an explicit user-only RequestUserInput for auxiliary LLM prompts that do not own durable message identity. Auto Review and compaction remove their request-only source registrations while retaining prompt content and freezing; provider serializers and projections keep the same wire data, assistant replay isolation, image ordering, and tool correlation. Session writes, Agent delivery, and recorded title requests continue to require identified durable messages. Bind the saved compatibility policy only to user sources and qualify tmux location attribution without weakening fixed system, model, or tool semantics. Rebuild the current inventory and unpublished V4 acknowledgement on the actual tool-role parent, preserving its rationale and all accepted historical records. The catalog format version records tooling metadata; Session remains V4. Developer-role policy and activation belong to their own feature. The latest-master Messages adapter, serialization, request-input typing, EpochHeader reservation, and attribution checks pass 103 tests across five files. The retained V3 Messages input-history snapshot passes through the source profile; Host/Client typechecks and all 41 documentation gates pass. The generated comparison records four changed roots and 447 unchanged type fingerprints. Latest-master ARIA changes are retained, with producer source labels applied independently; new Messages fixtures retain their producer names as declared source kinds and use the fixed system-message helper; recorded Session generations are unchanged by this regrouping. Co-authored-by: Tianyi Cui <[email protected]>
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.