Skip to main content
Glama

Continue Cursor chat

cursor_continue

Resume the Cursor chat rooted at a workspace directory and send a follow-up prompt to get the next turn of work, with sandbox permissions applied per turn.

Instructions

Continue the Cursor chat: resumes the thread rooted at this workspace (its chat 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 chat 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": "cursor_continue"
  }
}

Input Schema

NameRequiredDescriptionDefault
watchNoIf true, open the live "watch" view streaming cursor's steps (same viewer as cursor_ask). Default false.
promptYesFollow-up message for the existing chat.
sandboxNoPermission policy for THIS turn (default "read-only"). Same values and caveats as cursor_ask.read-only
timeout_sNoMax seconds to wait for cursor to complete. Default 180.
workspaceNoWorking root used by the prior chat. Defaults to the server cwd.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.21.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only flag non-read-only, open-world, non-idempotent. The description adds real behavior: missing workspace means the sub-agent sees no repo, restart recovery targets the newest on-disk chat for that directory, and sandbox is evaluated per turn. The 'trusted prompts only' warning is useful but terse about the actual risk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its identity (thread continuation), then the key constraint (same workspace). The sentence flow is slightly cramped across line breaks and the restart clause interrupts, but nearly every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation. The description covers the state-continuity model, the per-turn permission policy, restart recovery, and the safety caveat for autonomous use — everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description still adds meaning beyond it: workspace must match the prior chat's root or the sub-agent loses repo context, and sandbox is per-turn with a recommended read-only-to-workspace-write progression. These are semantic constraints the schema does not encode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Continue the Cursor chat: resumes the thread rooted at this workspace (its chat id)'. That distinguishes it from the *_ask siblings by emphasizing thread continuation rather than starting a chat, though it never names the ask sibling explicitly as the counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use guidance: pass the same workspace as the original ask, and it resumes the newest on-disk chat after a restart. It also sketches a two-phase workflow (read-only analyze, then continue with 'workspace-write' to apply). No explicit when-not-to-use case, but the operational context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.