Reference Docs
Install via Open VSX, since Cursor doesn't use the Marketplace.
Cursor doesn't read the VS Code Marketplace — it uses Open VSX as its default extension registry. Install focusanalyze-vscode from there instead; the extension works identically once installed.
Install from Open VSX.
Cursor's own built-in agent can also be pointed at the MCP server directly, without the extension — see the Claude article for the token you'll need.
The tree view is the visible part — the real point is that Claude Code or Cursor can attach notes to whichever task you're working on as you go, so the context of a working session isn't lost the moment the chat ends.
"FocusAnalyze: Set Active Task" writes a local pointer to whichever task you're focused on right now. It's a default, not a lock — the assistant can still touch other tasks by id when you name one, and a Claude Code chat and a Cursor chat can both write to the same task with nothing blocking either.
Instead of posting a new comment every single turn — which would leave a trail of near-duplicate comments over a long session — the assistant keeps one "Notes" or "Plan" doc on the task and updates it in place as the work develops. Come back days later, in a different chat, and it reads what was actually tried, decided, and left open.
Updating a doc in place is last-write-wins: if two sessions update the same doc around the same time, whichever call lands last silently overwrites the other. Fine for a running Notes doc; for anything that must never be lost, the assistant posts a separate comment instead, since comments can't collide.