Continue GitHub Copilot session
copilot_continueResume a prior coding session with the same workspace and a follow-up prompt, then switch sandbox permissions from read-only to workspace-write when you need fixes applied.
Instructions
Continue the Copilot session: resumes the thread rooted at this workspace (its
--session-id), so pass the same workspace= as the ask (without it the
sub-agent sees no repo). After a restart it resumes the newest on-disk session for
that directory. 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": "copilot_continue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| watch | No | If true, open the live "watch" view streaming copilot's steps (same viewer as copilot_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 copilot_ask. | read-only |
| timeout_s | No | Max seconds to wait for copilot to complete. Default 180. | |
| workspace | No | Working root used by the prior session. Defaults to the server cwd. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |