dsh-roles-zeta

LIMITATIONS

Known limitations

- **The preset still loads whole plugins; the mask hides the extras.** A kept `dsh-tool-fs` row still mounts `write`, `edit`, and `read_image` for a reviewer allowed `read`, and host-plane tools (`delegate`, `working_directory`, the MCP resource tools, every connected MCP server's `mcp__*` tools) still exist outside the preset. Neither reaches the child: the per-tool mask hides every name its `allow` list does not give, and a role without one loses `delegate` and the delegation tools unless `delegation: true`. The mask is computed when the child is created, so an allowed tool that registers later (an MCP server that connects afterwards) stays hidden from that child, and a tool the child registers in its own scope (its structured-output tool) is never masked. - **Role presets show up next to the shipped ones.** They are ordinary Agent Presets, so the Web preset picker lists them after `standard`, `cordis`, and the rest. - **Resuming a background child after a restart needs its preset again.** Role presets are registered on first use. Messaging a role child that was started before the host restarted fails with an unknown-preset error until the same role has been delegated once from the same parent preset. - **The tool table follows dsh 0.2.1-rc.2.** A tool plugin the table does not list is kept whole, and a tool renamed in a later dsh release stops being recognized until the table is updated. - **A role cannot change the workspace instruction chain.** Every child loads the same `AGENTS.md`/`CLAUDE.md` chain as its parent. - **A slash command is a request, not a guarantee.** The model performs the delegation; the transcript shows whether it did. - **The settings page edits files, not sessions.** A running child is unaffected by a later edit; the next start reads the new file. - **No per-role memory.**