Cursor
Install and authenticate Cursor's cursor-agent inside Daintree, including the per-OS credential paths and why Daintree does not resume Cursor sessions.
Cursor
Cursor's cursor-agent is its CLI coding agent. It runs as a process in its own Daintree terminal panel with full PTY emulation, like every other built-in agent.
| Command | cursor-agent |
|---|---|
| Shortcut | — (assignable in Keyboard settings) |
| Rendering | Alt-screen — Cursor draws its own full-screen TUI |
| Resume | None. Daintree captures no session ID for Cursor |
| Quit command | — (no slash-quit; Daintree closes the process) |
| Permission bypass | --force |
| Platforms | macOS, Windows, Linux |
Install & Authenticate
Sign in with cursor-agent login, which opens a browser. Cursor's own docs write the same command as agent login. For headless machines and CI, set CURSOR_API_KEY instead. Daintree checks for the credential file at the path below to decide whether Cursor is authenticated.
curl https://cursor.com/install -fsS | bash Credentials: ~/Library/Application Support/Cursor/User/globalStorage/storage.json
irm 'https://cursor.com/install?win32=true' | iex Credentials: %APPDATA%\Cursor\User\globalStorage\storage.json
curl https://cursor.com/install -fsS | bash Credentials: ~/.config/Cursor/User/globalStorage/storage.json
storage.json. Daintree's file probe misses those, so the agent shows as needing login even when you're signed in. It still launches and runs normally — the probe is a hint, not a gate.Resuming Sessions
Daintree does not resume Cursor. The agent registry declares no resume path for it, so no session ID is captured on shutdown and relaunching starts a fresh conversation. What Daintree still keeps is the panel itself: scrollback is serialized to disk and replayed on restart, and the panel's position in the grid survives a project switch. See Session Management for what persists.
Launch flags, custom presets and display titles are covered in Agent Presets. What the working, waiting and exited badges on a running agent mean is covered in Agent States.
cursor-agent isn't detected after install, confirm it's on your PATH (which cursor-agent on macOS/Linux, where cursor-agent on Windows), then restart Daintree. Cursor reports its version with cursor-agent -v, not --version, which is the probe Daintree uses.