How does Cursor CLI work in 1DevTool?

Step 1: Install cursor-agent — Put Cursor’s CLI on your PATH. 1DevTool detects it and adds it to the agent line-up without any configuration. Step 2: Open it from Add Terminal — Cursor appears beside Claude, Codex, Gemini and the rest, and can be part of a multi-select batch or a saved terminal set. Step 3: Pick its model — Use the same per-terminal model picker as the other agents, so Cursor can take a different role from the agent next to it. Step 4: Give it work like anyone else — Mention its terminal in Agent Input, assign it a task from the board, or resume it later from the dashboard or your phone.

AI Productivity

Cursor CLI

Cursor's agent joins the line-up alongside Claude, Codex, Gemini and the rest. Install `cursor-agent` and you can launch it, resume its sessions, pick its model, delegate to it, and see it in Add Terminal, the dashboard and the phone UI like any other agent.

Download 1DevTool All Features

Screenshot coming soon

Why You Need This

How this feature boosts your daily productivity

Every agent you use outside 1DevTool is an agent you babysit in its own window, with its own session list and no way to hand it work from anywhere else. Adding `cursor-agent` to the line-up means Cursor is a peer rather than a special case: it appears in Add Terminal, shows up on the Terminal Dashboard, can be resumed after a restart, can be delegated to by another agent, and is reachable from the phone UI. You pick the model per terminal, so Cursor can be the reviewer while Claude implements and Codex reads the repo — without leaving the workspace or copy-pasting between windows.

How It Works

Get started in 4 simple steps

Install cursor-agent

Put Cursor’s CLI on your PATH. 1DevTool detects it and adds it to the agent line-up without any configuration.

Open it from Add Terminal

Cursor appears beside Claude, Codex, Gemini and the rest, and can be part of a multi-select batch or a saved terminal set.

Pick its model

Use the same per-terminal model picker as the other agents, so Cursor can take a different role from the agent next to it.

Give it work like anyone else

Mention its terminal in Agent Input, assign it a task from the board, or resume it later from the dashboard or your phone.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# Cursor lives in its own window

# Its own session list

# Cannot be handed work by another agent

# Not on the dashboard

# Not reachable from your phone

# Copy-paste between two apps

The 1DevTool Way

Install cursor-agent — it is detected.

Open it from Add Terminal like any agent.

Delegate to it, assign it a task, resume it.

Key Capabilities

Everything included with Cursor CLI

Launch cursor-agent as a terminal from Add Terminal

Resume Cursor sessions after a restart

Pick which model that Cursor terminal runs

Delegate work to Cursor from another agent

See Cursor terminals on the Terminal Dashboard

Reach a Cursor terminal from the phone UI

Assign it a task from the Tasks board like any other agent

Why It Matters

The productivity impact of having ai productivity built into your workspace

A Peer, Not A Special Case

Cursor shows up in Add Terminal, on the dashboard and in the phone UI like every other agent, so it needs no separate window or workflow.

Resumable Like The Rest

Its sessions survive a restart, including through the agent-team resume flow when it worked alongside other agents.

Delegate To It

Another agent can hand it work and the Tasks board can assign to it, so Cursor can review while Claude implements.

Nothing To Configure

Install cursor-agent on your PATH and it is detected — no config file, no per-project setup.

More in AI Productivity

Other features in this category you might find useful

Ready to boost your workflow?

Download 1DevTool for free and experience Cursor CLI along with 170 other features — all in one app.

Download for Free View Changelog