Ask AI

AGENTS.md & CLAUDE.md Support

Bring your own AGENTS.md from Claude, Cursor, etc

How Sapience Supports Your AGENTS.md

Last Updated: 2026.07.07


Overview

If you've used a modern AI coding tool β€” Claude Code, OpenAI Codex, Cursor, or similar β€” you've probably kept a little instruction file at the root of your project that tells the AI how you want it to work: your tone, your formatting rules, the gotchas it should never forget. In the coding world that file has converged on a common name: AGENTS.md.

Sapience supports the exact same idea. Create a file called AGENTS.md at the root of your Sapience files, and every agent you talk to will automatically read it at the start of each conversation β€” no copy-pasting your preferences into every chat.

Think of AGENTS.md as your standing instructions to every Sapience agent. Write it once; it follows you everywhere.


Why This Exists

Every power user eventually finds themselves re-typing the same guidance to their agents:

"Keep answers short." Β· "Never use emojis." Β· "Always format tables in Markdown." Β· "When you draft an email for me, sign it 'Best, Ken.'" Β· "Assume I'm a finance person, not an engineer."

Retyping that on every new conversation is tedious and easy to forget. AGENTS.md solves it the same way CLAUDE.md solves it for Claude Code: you put your rules in one place, and the system quietly makes sure the agent sees them before it answers your first message.


The Basics: What Happens Behind the Scenes

When you start (or continue) a conversation with any Sapience agent, here's what happens the moment before the agent begins working:

  1. Sapience assembles your conversation's context β€” who you are, which skills and agents are available, your saved Memories, and any files you've attached.
  1. It looks for a file at the path /AGENTS.md in your personal file store (the root of your files, not inside a folder).
  1. If that file exists and its contents have been read, Sapience wraps them in a hidden system message and drops it into the conversation.
  1. The agent reads your instructions as authoritative context β€” as if you'd said them yourself at the top of the chat.
  1. From there, every reply respects your rules for the rest of that conversation.

You never see this happen. There's no extra button to press. The file just works, silently, on every conversation.


Setting It Up

Getting started takes about a minute.

Step 1 β€” Create the file

Create or upload a file named AGENTS.md and place it at the root of your Sapience files (not inside a folder).

The name is case-insensitive. AGENTS.md, agents.md, and Agents.md all work. We recommend the all-caps AGENTS.md to match the convention used by other tools.

Step 2 β€” Write your instructions

AGENTS.md is a plain Markdown file. Write it in whatever structure is natural for you. A good starter looks like this:

# My Agent Instructions

## About me
-I'm a finance leader, not a developer. Explain things in business terms.
-I work in Australian English. Use "organise", not "organize".

## How I like answers
-Be concise. Lead with the answer, then the reasoning.
-Use Markdown tables for any comparison of 3+ items.
-No emojis.

## When you draft things for me
-Emails: professional but warm. Sign off "Best, Ken."
-Reports: always include a one-line executive summary at the top.

## Things to remember
-My company is Main Beach Advisors (MBA).
-When I say "the deck", I mean our standard pitch template.

Step 3 β€” That's it

The next time you open a conversation with any agent, your instructions are already in play. There's nothing to enable per-agent and nothing to re-attach.


How It Behaves β€” The Details That Matter

A few behaviours are worth understanding so the feature never surprises you.

BehaviourWhat it means for youUser-scopedYour AGENTS.md applies to every agent in every conversation, across web, desktop, and mobile. It's tied to you, not to a single agent or project.Injected once per conversationThe file is added at the start of a conversation. Editing AGENTS.md affects new conversations; it won't retroactively rewrite a chat that's already underway. Start a fresh conversation to pick up your latest edits.Needs to be "read" firstSapience reads (parses) your uploaded files in the background. On the very first moment after upload, the content may not be parsed yet β€” in that rare case the agent simply proceeds without it, and the file is picked up automatically on your next conversation.Blank files are ignoredAn empty AGENTS.md is skipped β€” no harm done.Never breaks your chatIf anything goes wrong reading the file, Sapience logs it quietly and continues. A problem with AGENTS.md will never block or fail your message.


AGENTS.md vs. Memories

Sapience already has a Memories feature β€” short, discrete facts an agent can remember about you ("User prefers terse answers", "User's name is Ken"). So how does AGENTS.md relate?

They're complementary, and Sapience uses both together:

MemoriesAGENTS.mdShapeMany small, individual factsOne free-form documentBest forDiscrete things to recall ("my timezone is AEST")Rich, structured guidance ("here's my whole style guide")How you manage itAgents can add/update them for you as you chatYou author and edit it directly, like a documentFeels likeThe agent's memoryYour standing operating manual

When both are present, Sapience injects your Memories first, then your AGENTS.md β€” so the document you deliberately wrote is treated as the more recent, higher-priority signal. Use Memories for facts that accumulate naturally over time; use AGENTS.md for the deliberate, structured "here's how I want you to work" rules you want to own and edit yourself.


Familiar From Other Tools? Here's the Map

If you already keep an instructions file for a coding assistant, you'll feel right at home. AGENTS.md is part of a broader industry convergence on the idea of "a file that tells the agent how to behave."

ToolIts instructions fileWhere it livesOpenAI CodexAGENTS.mdRoot of your code repositoryClaude Code (Anthropic)CLAUDE.mdRepo root, plus a personal ~/.claude/CLAUDE.mdCursorProject Rules (.cursor/rules/*.mdc, legacy .cursorrules)Inside the projectGitHub Copilot.github/copilot-instructions.mdInside the repositoryGemini CLIGEMINI.mdRepo rootSapienceAGENTS.mdRoot of your Sapience files βœ…

The similarity: in all of these, a file of natural-language instructions is loaded into the model's context before it responds, so the assistant follows your rules without you repeating them.

The Sapience twist: the coding tools read the file from a folder on your computer, scoped to one code project. Sapience reads AGENTS.md from the root of your cloud file store, scoped to you β€” so a single file governs every agent, every conversation, on every device. We deliberately adopted the same AGENTS.md name so that if you already write one for Codex or your other tools, you can reuse the exact same habit (and often the exact same file) here.


Tips for a Great AGENTS.md

  1. Lead with the rules you care about most. Put your non-negotiables near the top.
  1. Be specific and concrete. "Be concise β€” answers under 150 words unless I ask for detail" beats "be brief."
  1. Give examples. Show the agent a sample email sign-off or table format rather than describing it.
  1. Keep it focused. A tight, one-page file the agent can fully absorb beats a sprawling document. It doesn't need to be exhaustive.
  1. Iterate. Notice an agent doing something you don't like? Add a line to AGENTS.md and start a new conversation. Over time it becomes your personal operating manual.

Quick Reference

QuestionAnswerWhat do I name the file?AGENTS.md (case-insensitive)Where does it go?The root of your Sapience files β€” not inside a folderWhich agents use it?All of them, automaticallyWhen does an edit take effect?On your next conversationDo I need to attach it each time?No β€” it's automaticWhat format?Plain MarkdownWhat if it has an error or is empty?It's skipped safely; your chat is never affected


Summary

AGENTS.md is your one-file, always-on instruction sheet for every Sapience agent. Write your preferences, style, and reminders once, drop the file at the root of your Sapience files, and every conversation you start β€” on any device, with any agent β€” will already know how you like to work.

It's the same idea coding tools like Codex, Claude Code, and Cursor use to shape their assistants β€” brought to your Sapience agents, and scoped to you rather than a single project.

Did this answer your question?
😞
😐
🀩