_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 human-collaboration capability family: slash commands, one-shot approvals, permission presets, and the question/answer seam that lets a running agent pause for a human decision. | package-group |
interaction/ — the human-collaboration plane
English | 中文
Summary
The interaction/ group covers the ways a person can guide a running agent. Use slash commands for immediate actions that do not require a model round trip, one-shot approvals for sensitive operations, permission presets to choose sandbox and approval behavior together, and questions when the agent needs information or a decision. Interactive applications expose these capabilities to people; automation handles its own approvals through ACP. The package map below distinguishes each capability and links to its full behavior and configuration.
Table of Contents
Packages
Each package README and its subsystem reference own the exhaustive contracts.
| Package | Role | ctx key |
|---|---|---|
commands/ |
Lets users type slash commands that run directly against an agent without a model round trip | ctx.commands |
user-approval/ |
Asks composed answerers for one-shot allow/reject decisions and fails closed without one | ctx.approval |
permission-presets/ |
Bundles sandbox mode with an approval policy into one user-facing Permissions selector | ctx.permissionPresets |
user-questions/ |
Defines the validated question schema and scoped answerer waterfall an agent pauses on | ctx.userQuestions |
tool-ask-user/ |
Exposes the ask_user_question tool so the model can ask the human for a decision |
registers on ctx.tools |
Related documentation
Start with the subsystem references for the shared vocabularies, then the neighboring automation and composition surfaces.
- Commands subsystem — command registry semantics and the
ctx.commandsCordis surface. - Approval subsystem — request/outcome vocabulary, the answerer waterfall, and per-session policy.
- Permission presets subsystem — the preset table and the knob write-through.
- User interaction subsystem — question vocabulary, answerer waterfall, and presentation intent.
- ACP group — the automation-only transport that answers approval requests for its own agents.
Dev Note
Working context for maintainers — click to expand
None.