# Cursor

Cursor works fully with 0bridge: setup, history collection and resume. Level: full. Last checked 2026-10-01.

## Set it up

```
npm install -g 0bridge
0b setup
```

`0b setup` adds 0bridge to `~/.cursor/mcp.json`. Restart Cursor, then sign in from Cursor's MCP settings. By hand, add this to `~/.cursor/mcp.json`:

```
{"mcpServers": {"0bridge": {"url": "https://0bridge.dev/mcp"}}}
```

## What works

- **History:** with `0b history on`, Cursor conversations are collected from the app's local database. Reading it needs SQLite: Node 22.5 or newer, or the `sqlite3` command (Windows has neither by default); without it, `0b history on` and `0b history status` say Cursor is skipped. `0b history hooks on` adds a stop hook so a conversation uploads when a turn ends instead of waiting for the 15-minute job (that Cursor runs it on every turn isn't verified yet). Hooks also feed the [session board](/docs/sessions) with working and done; Cursor has no permission hook, so it never shows as needing you.
- **Resume into Cursor:** `0b resume 0b:k3f9x2 --tool cursor` starts Cursor's command-line agent with the handoff as its first message, when `cursor-agent` is installed. See [Resume anywhere](/docs/resume).
- **Cloud agents:** `0b project cloud --cursor` writes a `.cursor/mcp.json` for Cursor's cloud agents. The field names it uses for the token are not verified against Cursor's current documentation, so check the file before relying on it: [Cloud agents](/docs/cloud-agents).

## What doesn't

Conversations from Cursor's command-line agent are collected only when their bodies are on disk in a form we can read. If yours aren't picked up, `0b history sync --dry-run` shows what was found.

## Remove it

`0b history hooks off` removes the stop hook, and only the one 0bridge added.