> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plungeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# plungeai_continue

> Continue a paused conversation: answer a question (message) or approve a pending action (approve:true). Only pass approve:true after the user explicitly confirmed — never approve on your own. To deny or change course, pass their words as message.


Continue a paused conversation: answer a question (`message`) or approve a pending action (`approve: true`). Pass `approve: true` only after the user explicitly confirmed; never approve on your own. To deny or change course, pass the user's words as `message`.

**Returns.** The agent's reply, then either a new ⏸ block or `✅ Conversation resolved (no further input needed).` It resumes an agent pause (`⏸ AWAITING USER APPROVAL` / `⏸ AWAITING USER`); a trust-fence `⏸ NEEDS APPROVAL` with no actions has no session and answers `No conversation session…` ([6.6](https://mcp.plungeai.com/docs#66-the-trust-fence--needs-approval)). Errors (`isError: true`): `` Provide `message` or `approve: true` ``, `Execution not found`, `No conversation session for this execution (expired or not a conversational agent)`, `This run isn't paused — it already completed. Use plungeai_followup …`, `Agent continuation failed`. Details: [9.6](https://mcp.plungeai.com/docs#96-paused-runs-plungeai_continue).

Runs the held action, which may spend money; send it only after the user said yes (not verified here):

```bash
curl -s https://mcp.plungeai.com/v1 \
  -H "Authorization: Bearer $PLUNGE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_continue","arguments":{"user_request":"yes, go ahead","execution_id":"<execution_id>","approve":true}}}'
```

<Note>
One parameter recurs across the tools: `user_request` (on every tool: a string of up to 4,000 characters, optional; clients should always send it). It is described once in [Recurring parameters](/mcp-reference/overview#recurring-parameters) on the MCP overview.
</Note>

## Input schema

```json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "user_request": {
      "description": "The user's original request, verbatim and in their own words, before you translated it into this call. Always include it — the platform uses it for request context, routing and support diagnostics.",
      "type": "string",
      "maxLength": 4000
    },
    "execution_id": {
      "type": "string",
      "maxLength": 256
    },
    "message": {
      "type": "string",
      "maxLength": 65536
    },
    "approve": {
      "type": "boolean"
    }
  },
  "required": [
    "execution_id"
  ]
}
```