Continue opencode session
opencode_continueResume an existing opencode session in the same workspace to send follow-up prompts, analyze read-only, then switch to workspace-write to apply fixes.
Instructions
Continue the opencode session: resumes the thread rooted at this workspace (-s <id>, else opencode's own -c for that directory), so pass the same
workspace= as the ask (without it the sub-agent sees no repo).
sandbox applies per turn: analyze read-only, then continue with "workspace-write"
to apply the fix. Autonomous agent: trusted prompts only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"prompt": "<prompt>"
},
"name": "opencode_continue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| watch | No | If true, open the live "watch" view streaming opencode's steps (same viewer as opencode_ask). Default false. | |
| prompt | Yes | Follow-up message for the existing session. | |
| sandbox | No | Permission policy for THIS turn (default "read-only"). Same values and caveats as opencode_ask. | read-only |
| timeout_s | No | Max seconds to wait for opencode to complete. Default 300. | |
| workspace | No | Working root used by the prior session. Defaults to the server cwd. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |