Reset Cursor Acp

Reset Cursor ACP in bb

For terminal sessions use cursor-cli; for general bb control use bb-cli.

How resets work

• bb's provider-acp plugin starts one cursor-agent acp subprocess per thread, on demand, owned by a bb-provider-bridge-worker.
• There is no global Cursor ACP server. Do not create one or keep it alive with a watchdog.
• Rules, skills, and .cursor/mcp.json reload when a new subprocess starts.
• bb thread stop <id> releases the runtime and stops its subprocess, preserving history. The next message starts a fresh agent.

Quick reset

Resolve scripts/reset-cursor-acp.sh relative to this SKILL.md. Run:

scripts/reset-cursor-acp.sh <thread-id>      # reset one Cursor thread
scripts/reset-cursor-acp.sh --self           # reset the current thread (BB_THREAD_ID)
scripts/reset-cursor-acp.sh                  # no thread: orphan cleanup + health check only
scripts/reset-cursor-acp.sh --dry-run        # show what would happen
scripts/reset-cursor-acp.sh <id> --kill-all  # also kill live agents of OTHER Cursor threads

Find Cursor thread ids with bb status (current thread) or:

bb thread list --json | python3 -c 'import json,sys; [print(t["id"], t["status"], t["title"]) for t in json.load(sys.stdin) if t.get("providerId")=="acp-cursor"]'

The script stops the selected thread, removes orphaned cursor-agent acp processes (parent gone or not a bb bridge worker), reports CLI version/login/update status, and asks for the next message. Other threads stay running unless --kill-all.

If sandboxing blocks ps with "operation not permitted", rerun the script outside the sandbox.

Verify

Send one short message to verify a fresh agent responds. If it hangs again, check the causes below before another reset.

Known causes

• Old Cursor CLI. If the health check shows an update, run bb updates apply, then reset.
• Expired login. Symptom "Failed to initialize session services". Fix: cursor-agent login, then reset.
• Pending permission. Cursor waits for session/request_permission. Check and resolve the thread's pending approval before resetting.
• Resume failure. For session/load → "Session not found", use a fresh session after bb thread stop rather than retrying the load.
• Team-level MCP servers from the Cursor dashboard do not work in ACP mode. Only project or user .cursor/mcp.json.
• Rate limits. Enable retries with bb plugin enable provider-retry.

Do not

• No launchd KeepAlive, cron, or watchdog for cursor-agent acp.
• Never blindly run pkill -f cursor-agent; it kills all Cursor threads and the interactive TUI. Use the script, which targets orphans by default.
• Do not restart bb for one stuck thread; use bb thread stop.
• Do not use bb thread compact; Cursor does not support it.