Cursor for UI, Claude Code for the backend

Many agents, one playbookFull-stack builder who likes different tools for different work

We used Cursor for quick UI changes and Claude Code for API work. Cursor didn't know the API had changed shape that morning.

How do I keep Cursor up to date with API changes I made in Claude Code the same day?

Set up Cursor and Claude Code in the same project with arcroom init, and ArcRoom passes Claude's API changes to Cursor through recall. Claude's session records the change and saves the new response shape, so Cursor gets the latest shape when it works on the screen. Recall picks what fits the prompt, so a vague UI prompt may not get the API note.

Also asked as: Cursor doesn't know my backend changed this morning. How do I fix that? · How do I share context between Cursor and Claude Code in one project? · Can Cursor see API changes Claude Code made earlier?

The work

Both agents are set up in the same project with arcroom init.

ArcRoom keeps
  • Recall
The next agent gets

[cursor] Recent in this project (claude, 2 h ago):

Step by step

  1. Both agents are set up in the same project with arcroom init.
  2. Claude's session records the API change and saves the new response shape.
  3. When Cursor works on the screen, recall gives it the latest shape.

What the agent sees

[cursor] Recent in this project (claude, 2 h ago):
Changed api/orders.ts: response now { items, nextCursor } (was array)

Compared with today's tools

Shared API notes file, updated by hand

After an API change, update one notes file that both CLAUDE.md and the Cursor rules point to.

Setup
20 min
Ongoing
edit the file after each API change, ~5 min

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min per agent (npx arcroom init --agent …)
Ongoing
None

Works if someone updates it the same morning; ArcRoom's notes come from the backend session itself.

Where it stops

Recall picks what fits the prompt. A vague UI prompt may not get the API note.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in many agents, one playbook