Guide

Cursor and Nook

Nook shows Cursor agent sessions next to your Claude Code sessions, status only. This page covers what you see, how to turn it on and what it never does.

Last updated · Nook 0.1.0 · Was this helpful? Report a problem

What you get

New in v0.1.x (unreleased build). Cursor support is not in the 0.1.0 installer. It arrives with the next release; no date is promised.

Cursor agent sessions show up in the same island as your Claude Code sessions, each with its own row and state (for example working or done).

  • Status only. You see what a Cursor agent is doing. You cannot approve or answer from the island; permissions and questions stay in Cursor.
  • Marks. Claude Code sessions wear the Claude sparkle, Cursor sessions wear the Cursor cube, so you can tell them apart at a glance.
  • Filter chips. The session list has All, Claude Code and Cursor chips to narrow it down.
  • Folded island. When the island is folded to a pill, each session is a small dot. Cursor dots have a hole in the middle, so they differ from Claude Code dots.
The session list with Claude Code and Cursor rows, the filter chips and the sparkle and cube marks

Set it up

  1. Open Nook’s Settings and go to the Cursor block.
  2. Click Install. Nook shows a preview of the exact diff and the path of the dated backup it will take.
  3. Click to confirm. Nothing is written until you do. Nook writes ~/.cursor/hooks.json (that is, %USERPROFILE%\.cursor\hooks.json).
  4. Restart Cursor so it reads the new hooks.

It follows the same rules as the Claude Code hooks: see how the install stays safe. The Cursor block can also remove its entries again, with the same preview, backup and click.

What it never does in Cursor

  • It listens only to observational events: things that already happened or are happening.
  • It never allows, denies or delays anything in Cursor. The relay always exits immediately, so Cursor never waits for Nook.
  • It uses no network and no telemetry, like the rest of Nook.

Claude Code inside Cursor’s terminal

This is separate and works as before. If you run claude in Cursor’s integrated terminal, that is an ordinary Claude Code session: the Claude Code hooks report it, and it appears with approvals, questions and usage limits like any other. The relay also notes which editor or terminal a session runs in (it recognises Cursor, VS Code, Windows Terminal, PowerShell and others), so the jump button can usually bring the right window forward. If it goes to the wrong window, run nook-hook --where from that terminal; see troubleshooting.

At a glance

Claude Code (incl. in Cursor’s terminal)Cursor’s own agent
Shown in NookYes (0.1.0)Yes (new in v0.1.x, unreleased build)
Approve and answer from the islandYes, same as any sessionNo: status only
Set up withSettings, Claude Code, Install hooksSettings, Cursor, Install (then restart Cursor)
MarkClaude sparkleCursor cube

Disclaimer: Nook is an independent project, not affiliated with or endorsed by Cursor or Anysphere. Cursor is a trademark of its owner.