Start conversation
dsh_startCreates a disk-backed DSH coding-agent conversation that survives crashes and restarts, returning its ID and title so you can dispatch work to it later.
Instructions
Create a DSH conversation: a coding agent you can keep working with. The conversation lives on disk and the process is only a cache; if the process is reaped or crashes, the next dispatch brings it back with ACP session/resume and nothing is lost. Returns the conversation_id and the conversation title. Dispatch work to it with dsh_send.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "dsh_start"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Absolute path of the workspace. It decides the agent's working directory, where AGENTS.md and skills are discovered, and the root the sandbox may write to. A single local root can supply the default in a legacy MCP client. Pass cwd explicitly with multiple roots, no roots, or MCP 2026-07-28. | |
| model | No | Model name (for example deepseek-flash). When set, provider must be set too. | |
| review | No | Caller review policy, default advisory. advisory: every dispatch result and sentinel carries a review ticket (checklist, evidence, and the dsh_review entry point) but **does not block** later dispatches; off: no ticket. A single dsh_send can override it. | |
| provider | No | Model provider name (for example deepseek-official). Leave empty for the profile default. | |
| isolation | No | Workspace isolation, default none (work directly in cwd). worktree = create a new worktree and branch `dsh/<time>` for the git repository cwd is in and work there, leaving the main checkout alone, so you (the caller) can keep editing the original directory at the same time. It starts from the current HEAD: uncommitted changes in the main checkout are not carried over, and the new worktree has no node_modules or other dependencies, so DSH may reinstall them. The changes stay on that branch for you to review and merge yourself; dsh_release(forget=true) deletes the worktree directory if it is clean (the branch is kept). | |
| keep_alive | No | true = this conversation's process is exempt from idle-TTL and MAX_LIVE reaping (for a long-lived conversation that must keep holding the write lock). Default false: after 10 idle minutes the process is reaped and its memory freed, and the next dispatch resumes it with nothing lost. With true, remember to dsh_release when done, or it keeps a DSH process (about 300-480 MB) forever. | |
| permission | No | Permission tier. Default workspace-write. read-only suits untrusted material such as malware samples; workspace-write limits writes through the DSH sandbox. Escalation requests follow the machine approval policy. The tier is fixed at creation. A resumed DSH session keeps the permission it recorded, so changing this argument later does not change an existing conversation; create a new one to switch tiers. (The tier is really enforced: it comes from the environment passed at spawn time, and test/permission.mjs checks each tier against the session's own record.) | |
| title_hint | No | A readable label for the conversation (up to 200 characters). DSH's own title is a truncated prefix of the first message (about 13-15 characters) and is shown first; the value given here is not overwritten and comes back in dsh_get / dsh_start as the title hint. | |
| on_approval | No | How approval requests are handled. **read-only forces auto-deny** (auto-allow or ask is rejected outright, because it would let DSH's sandbox escalation through). The default tier has a machine ceiling of auto-deny. Callers can choose a stricter policy. The operator sets DSH_MCP_APPROVAL to permit a less restrictive policy. ask leaves each request pending until you decide it with dsh_approval_decide. | |
| reasoning_effort | No | Reasoning effort, default max. ACP's own default is "Provider default" (unset); this server sets max explicitly. Lower it to save money. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | Yes | ||
| permission | Yes | ||
| on_approval | Yes | ||
| conversation_id | Yes |