imccyu
eb1713f856
* fix(session-projection): keep released units in checkpoints Since the Cordis rc.11 teardown order unloads the Web layer before the base layer, Session Controller and harness-dev-context release their projection units before their live Sessions detach. The projection cache is still alive at that point and wrote a checkpoint holding only the units that were still registered, replacing the complete record. A blank Session then lost sessionListMetadata and listed as an untitled conversation after every graceful restart. A released unit now stays in the registry as a predecessor: it leaves event drives, snapshots, restores, and change notifications, while checkpoint() keeps each Session's last cell of it without advancing it. Registering the same key again replaces the predecessor and refolds the log. The projection cache keeps replacing whole records. * test(session-projection): assert frozen released units across unload tests Update the remaining unload tests that still expected a released unit to vanish from checkpoint(): user-approval, agent-loop inbox and scope lifecycle, time-context, and the agent registry now assert that the same Session keeps its pre-unload row, that a later event does not advance it, and that a Session created after the unload has no row. The token-meter and goal unload tests also append an event after the unload. Document that a retained handle read still advances a released cell that checkpoint() serves, and that restore() folds only live units, so its refreshed rows omit released units. * docs(session-projection): sync the ProjectionHandle type-equiv block * docs(session-projection): record frozen released units and their upgrade Add the upgrade guide for checkpoint() keeping a released unit's last row, update the registration-handles Agent Note with the frozen-cell decision and the retained predecessor, list both consequences under the registry README's known limitations, note in the projection cache README that a stored row can be frozen at its unit's release, and say that restoreFloor() ignores released predecessors. Update the agent-loop resource-lifecycle unload test, which read checkpoints through an alias, to the frozen-row semantics. * docs(upgrade-guide): mark the released-checkpoint snippet ignore-check * docs(session-projection): state the retained-handle path and narrow a rejected alternative * docs(upgrade-guide): re-record the released-checkpoint guide pairing
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 pending-question lifecycle.
- ACP group — the automation-only transport that answers approval requests for its own agents.
Dev Note
Working context for maintainers — click to expand
None.