Does cursor-agent have an equivalent of Claude Code’s /background?

Not a native one as of July 2026. Claude Code can detach a session as a background agent with /background; with cursor-agent you compose the same effect from parts: tmux (or a daemon) for persistence, plus something that actually notifies you on prompts and completion — which is the part none of the classic Unix tools provide.

How do I get notified when cursor-agent finishes or needs approval?

For print-mode runs, chain a notifier onto the command exit. For interactive sessions there is no hook system to wire, so the reliable route is running the CLI under a wrapper that watches the terminal stream — that is exactly what Backgrind does: it owns the PTY, sees the approval prompt appear, and pings you on the overlay or your phone.

Guide

Running cursor-agent in the background (without losing its questions)

Q: Can the Cursor CLI run in the background?

Partially, out of the box. cursor-agent has a non-interactive print mode (agent -p "task") that runs fire-and-forget — ideal for scripted, pre-approved work. What it lacks is a detach-and-notify mode for interactive sessions: put one in tmux and it survives fine, but its approval prompts wait silently for you to remember to look.

Andrew Mercer July 23, 2026 · 6 min read

Running cursor-agent in the background (without losing its questions)

Same itch, different agent: you hand cursor-agent a task and want your terminal — and your attention — back. We've covered the background story for Claude Code, where /background detaches a whole session natively. The Cursor CLI plays it differently: brilliant at fire-and-forget, silent at running-but-reachable. Here's what each mode actually gives you, and how to assemble the missing piece. (New to the CLI? Start with installing cursor-agent.)

What cursor-agent gives you natively: print mode

For scripted, zero-decision work, the CLI is genuinely good at backgrounding itself:

agent -p "add JSDoc to every exported function in src/utils" --output-format text

Print mode runs non-interactively and exits — pipe it, cron it, chain it in CI. By default it only proposes edits (writing files takes an explicit --force), which makes it safely scriptable. If your task needs no judgment calls mid-flight, this is the whole answer: run it, check the diff when you're back.

Where it goes quiet: interactive sessions

Real agent work isn't zero-decision. An interactive cursor-agent session stops to ask before running commands — that's a feature — and the moment you detach it, those questions start waiting in a room you've left:

tmux / screen keep the session alive across terminal closes and SSH drops — persistence solved. But a detached pane can't tap your shoulder; the y/n prompt sits there while you're heads-down elsewhere. Same trap as with every agent.
nohup / & are actively wrong for an interactive agent: they orphan the prompt entirely, and the "background run" becomes a hang you discover an hour later.
A buried terminal window is the default failure mode: alive, working, waiting — and invisible behind your editor since 2:40 pm.

Claude Code fills this gap with hooks you can wire to notifiers. cursor-agent doesn't expose an equivalent hook system, so the notification layer has to live outside the agent — something that watches the terminal itself.

The assembled workflow

The pattern that works is the same one we've argued for across agents: a daemon owns the process (so closing the UI never kills the run), the session stays glanceable in a lightweight always-on-top surface instead of a buried tab, and an explicit ping fires on the two transitions that matter — needs approval and done. For fire-and-forget pieces, keep using print mode; for everything interactive, put the session somewhere that can reach you.

Frequently asked questions

Can the Cursor CLI run in the background?

Fire-and-forget: yes — print mode (agent -p) runs non-interactively and is safely scriptable. Interactive sessions persist fine under tmux, but their approval prompts wait silently — nothing notifies you.

Is there an equivalent of Claude Code's /background?

Not natively as of July 2026. You compose it: tmux or a daemon for persistence, plus an external watcher for notifications — the part the Unix toolbox doesn't provide.

How do I get notified on approvals and completion?

Print mode: chain a notifier on exit. Interactive: run the CLI under a wrapper that owns the PTY and watches the stream — Backgrind pings the overlay and your phone when the prompt appears.

Where Backgrind fits

Backgrind is that missing layer, agent-agnostic by design: it PTY-wraps the same agent CLI you already run, keeps it alive in a background daemon, floats it in an always-on-top overlay, and pings you the moment cursor-agent stops for a decision or finishes — with inline approve from the toast, or from your phone. Claude Code, cursor-agent, OpenCode: tabs in one window, one notification pipeline, zero babysitting. Feel it in the live demo.