onpath × Cu Cursor Agent integration

Monitor Cursor Agent,
locally.

Wrap cursor-agent with onpath and monitor each session you run through it. Detect stuck loops, get a recovery prompt, and let Cursor Agent inspect local findings over read-only MCP.

Get started Read the docs

Works with the Cursor Agent CLI from Cursor · stable

zsh — Cursor Agent command walkthrough

# one prefix — Cursor Agent runs exactly as normal

$ onpath run -- cursor-agent "migrate the auth service"

↳ illustrative session · local recording active

# onpath watches the stream and flags stuck loops

⚠ time-budget-exceeded · 20m exceeded · run blocked by policy

# configure and verify read-only MCP

$ onpath install cursor --workspace .

$ cursor-agent mcp list

What onpath catches in Cursor Agent

Repeated failures

Same test, same error, on repeat — caught by failure signature.

warn

Edit loops

The same path edited repeatedly without a successful command.

warn

No progress & time budget

Configured session budgets crossed without successful progress.

warn

How onpath works with Cursor Agent

Three steps. Nothing changes about how Cursor Agent runs.

onpath sits between you and the cursor-agent CLI — observing, recording, and reporting without altering the agent's behavior.

STEP 01

Wrap the command

Prefix any Cursor Agent invocation. onpath spawns it as a child process and watches the stream.

$ onpath run -- cursor-agent

STEP 02

Detect locally

Commands, exits, and edits stream to local SQLite. Detectors flag stuck patterns in real time.

→ .onpath/events.sqlite

STEP 03

Feed back over MCP

Install the read-only MCP server so Cursor Agent can read its own findings and recovery prompt.

$ onpath install cursor --workspace .

Read-only MCP

Cursor Agent can inspect local evidence — and cannot act through onpath.

The onpath MCP server exposes discovered projects, recent sessions, findings, reports, Work summaries, and deterministic recovery prompts. It has no tool that runs commands, edits files, or changes policy.

Active findingsOpen detections with severity, signature, and repeat count.

Recovery promptA concrete next step Cursor Agent can act on to break the loop.

Read-only by designNo write surface — onpath only answers questions about the session.

Cursor Agent · MCP

# configure and verify the server

$ onpath install cursor --workspace .

$ cursor-agent mcp list

# implemented read-only tools

onpath_list_findings

onpath_get_recovery_prompt

Compatibility

Cursor Agent support at a glance.

onpath wraps the cursor-agent CLI on macOS and Linux. Everything runs locally — no agent API keys are shared with onpath.

Invocationonpath run -- cursor-agent

Event capturecommands · exits · edits · timings

MCP serveronpath install cursor --workspace .

Data handlinglocal SQLite · sync opt-in

Statusstable

More integrations

onpath works with your whole agent stack.

Use the same prefix and the same dashboard across every coding agent on your team.

C Codexonpath run -- codex Cl Claude Codeonpath run -- claude O OpenCodeonpath run -- opencode

Put Cursor Agent on path.

Local-first. Open-core. Two minutes to install and one prefix to start.

$onpath run -- cursor-agent

Get started Read the docs