Use your AgentSoul files with Cursor

To use an AgentSoul soul in Cursor, add the four files to your project and connect them through an AGENTS.md file at the project root, which Cursor reads as agent instructions. If you want more control, create a project rule that always applies and holds the essentials of your soul. Either way, Cursor’s agent starts each request knowing who it is, who you are and how you like to work.

Before you start

Forge a soul in the AgentSoul iPhone app with Flash Forge or Gao Dao, or on the web at agentsoul.market. On your result, tap “Get the four files”, then “Send to computer”, and AirDrop them to your Mac, save them to Files, or email them to yourself. You should end up with soul.md, identity.md, user.md and agents.md on the machine where Cursor runs.

Option 1: AGENTS.md at the project root

1. Create a folder in your repository for the soul and copy the four files into it.
2. At the project root, create AGENTS.md, or open the one you already have.
3. Add a short “Agent personality” section. Summarise the core of soul.md in a few lines: the agent’s temperament, its top values and what it pushes back on.
4. Add two or three lines from user.md about how you like answers — for example, conclusion first, then reasoning.
5. Paste the steps and escalation rule from agents.md, trimmed to what applies to coding.
6. Note the folder path of the full files, so you or the agent can open them when more detail is needed.

AGENTS.md has a practical advantage: it is a shared convention that several coding agents look for, so the same file can carry your soul across tools. AgentSoul names the file agents.md in lower case; the project-root convention uses capitals, so create AGENTS.md rather than relying on the original file name.

Option 2: a project rule

Cursor’s project rules live inside the project and can be set to apply always, automatically when relevant, or only when you mention them. Create a new project rule from Cursor’s settings, name it something like “agent soul”, set it to always apply, and paste the condensed personality from soul.md and user.md. You can keep the agents.md procedure in a second rule that applies only when you ask for it — handy if you want the personality everywhere but the step-by-step playbook only for larger tasks.

Keep it short

Instructions that are always on travel with every request. The full AgentSoul files are written to be read and understood by people too, so they include explanation an agent does not need every time. The best results come from a tight version: a paragraph of character, five or so ranked values, how you want to be addressed, and when the agent should stop and ask. Keep the full files in the repository as the reference you return to.

Sharing a soul with your team

Because AGENTS.md and project rules live in the repository, everyone who opens the project gets the same agent. That is useful when a team wants a consistent reviewer or pair programmer. It also means one person’s preferences become everyone’s defaults, so think about which parts are shared. soul.md, identity.md and agents.md describe the agent and travel well. user.md describes a specific person; keep it in your own user-level settings or out of the shared repository, and let each teammate add their own.

Testing the result

• Open a new chat and ask the agent to describe its working style. It should sound like your soul, not a generic assistant.
• Ask for a risky refactor and see whether it raises concerns the way your soul’s guardrails suggest.
• If a trait gets in the way — too cautious, too chatty — edit that line. The files are yours.

Your result is an AI-generated hypothesis, not a diagnosis. Use it as a well-made first draft of your agent, then shape it as you learn what helps you code.