Shared memory for Cursor

How do I share Cursor context across a team?

Cursor rules hold the conventions someone wrote down ahead of time. Wayform holds the decisions your team makes as it works, with the reason and who made it, and gives them to every teammate’s Cursor session through MCP. A decision made in someone else’s Claude Code or Codex session reaches your Cursor session too.

Wayform doesn’t replace Cursor rules or restore whole conversations. It shares the plans and decisions worth keeping. Compare the two.

Connect Cursor

Start with the quickstart to create or join an approved Wayform space. Run these commands from your product repository:

wayform init --remote --clients cursor
wayform login
agent mcp login wayform
wayform doctor

Setup writes .cursor/mcp.json and the supported hooks for this project only. You can approve the wayform connection in the Cursor IDE instead of running agent mcp login. Open a fresh session afterward.

Save one useful decision

Here is an illustrative example. In Cursor, type:

/remember team invitations use our existing GitHub login because we want one identity system.

Or say it in plain language: “Record this decision in Wayform: …”. Check that it was saved to the intended project.

Verify it in a fresh session

Open a new session in the same repo, or ask a teammate to, and ask:

Search Wayform for our team invitation decision. Explain the approach and the reason before proposing changes.

The answer should include both. If it doesn’t, check authentication and the project name.

Build with Cursor

Choose Build on a plan in the desktop app and pick Cursor. Each build gets its own branch, and Auto mode and automatic CI wakeups are available for Cursor. From the terminal:

wayform build 12 --client cursor

Replace 12 with your plan number.

If a guarded action (Shell, Write, StrReplace, Edit, or Delete) contradicts a team decision, Cursor blocks it and asks you. Only your confirmation lets the exception through. The guard can miss conflicts or flag ones that don’t apply, and it is not a security sandbox. How the guard works.