README.md 3.0 KB
description: "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."
kind: "package-group"
interaction/ — the human-collaboration plane
English | 中文
Summary
The interaction/ group is where a human collaborates with a running agent. It provides the slash-command plane users type into, the one-shot approval decisions behind sensitive actions, named permission presets that bundle sandbox mode with an approval policy, and the question/answer service an agent pauses on when it needs a human decision. All five packages are product packages — the real interfaces a person drives — and the product dsh CLI composes them directly. Interactive applications drive the command, approval, and question interfaces directly, while automation uses the ACP transport. The subsystem references own the exhaustive contracts; this map points at each package and its neighbors.
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.