---
title: "Resume or stop a chat turn paused by a large-edit continue prompt."
method: POST
path: "/v1/chat/{session_id}/continue"
tags: ["v1", "mcp", "chat"]
---

# Resume or stop a chat turn paused by a large-edit continue prompt.

`POST /v1/chat/{session_id}/continue`

## Request

- Base URL: `https://api.superdocs.app`
- URL: `https://api.superdocs.app/v1/chat/{session_id}/continue`
- Auth: HTTP bearer

Used with chat_async when a large edit paused to ask whether to keep going.
Poll get_job until status=awaiting_approval AND metadata.awaiting_kind='continue_prompt';
then POST here with continue=true to resume (the AI picks up where it left off with a
fresh time/step budget) or continue=false to stop (everything applied so far is kept).
The job then resumes/finishes and reaches status=completed. This is NOT the change-
approval endpoint (that is approve_change) — it can only act on a continue-prompt pause.

## Path parameters

- `session_id` string, required

## Headers

- `authorization` string, nullable

## Request body

- ContinueRequest: Resume or stop a chat turn that paused to ask whether to continue.
  - `job_id` string, required: Job ID awaiting a continue decision.
  - `continue` boolean, required: True to resume with a fresh budget; false to stop here (work so far is kept).

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/superdocs/apis/universal-document-ai-api.md) · [All operations](https://skmtc.dev/superdocs/apis/universal-document-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/superdocs/apis/universal-document-ai-api/revisions/37d03122940b?raw)