Guide

Agency setup: one Cursor account per client

Agencies that bill or segregate client work should give each client (or each billing seat) its own Cursor userdata directory. That keeps chat, rules, and subscriptions from leaking across clients. Persona maps repos to personas with .cursor/persona.json or folder rules, and can show per-window cost estimates when you need allocation clues.

Steps

1. Decide the isolation unit: per client, per team seat, or per engagement.
2. Create one persona / userdata directory per unit; sign into the matching Cursor account once.
3. Mark client repos with .cursor/persona.json or add path rules under ~/.cursor/persona/rules.json.
4. Open client work from the matching persona window. Use Cursor - Work launchers and Persona Helper / Dock launchers if sign-in links must stay on that account.
5. For spend allocation, use Persona’s window estimate or Persona Pro’s per-project ledger. Cursor Team exports still do not break billed dollars out by repo.

Common mistake

Sharing one Cursor Team seat across every client folder mixes chat history and makes it hard to prove which work used which subscription. Profiles alone do not fix that.

Related guides

• Work and personal at once
• Switch Cursor accounts
• Compare switching approaches