glossary · What it keeps

Agent instruction file (CLAUDE.md, AGENTS.md)

definition

An agent instruction file is a Markdown file in a project, such as CLAUDE.md or AGENTS.md, that an AI coding agent reads at the start of a session to learn the project's conventions, commands and rules.

in one line: CLAUDE.md or AGENTS.md: what every session reads first.

in context

Where does an agent instruction file fit?

Keep the file short. Facts stay in the file. The process moves into steps. Lessons move into memory.

Stable factsstay in the file
Proceduresbecome workflow steps
Lessonsbecome memory
Where each kind of instruction belongs.
two ways to say it

What is an agent instruction file, in plain words?

Same idea at two depths: the plain version, then what the engine actually does.

Every incident adds a rule, and the file becomes a rulebook the agent skims.

Keep facts in the file. Hand the process over one step at a time.

for engineers

With ConvOps the file can shrink to a few lines: get the current step, do only that step, advance and record why.

Policies arrive inside the step. Memory and routes bring back what past runs learned.

the longer answer

Why does an agent instruction file matter?

Instruction files exist because every new agent session starts without context. Claude Code reads CLAUDE.md files from the project and the user's settings. AGENTS.md is an open format meant as one predictable place for coding-agent instructions, and its site lists support in tools such as OpenAI Codex, Cursor, GitHub Copilot, Jules and many others. The content is similar everywhere: how to build and test, code style, where things live, what never to do.

They work well for stable, short facts. The trouble starts when they become the place where the process lives. Each incident adds a rule, each rule adds an exception, and the file grows into a rulebook the agent reads in full and follows in part. Thoughtworks named the pattern "agent instruction bloat" on its Technology Radar. A long file costs context on every session, mixes unrelated rules together, and gives no way to tell which rule applied to a given change.

A practical split keeps the file short. Facts that every session needs stay in it: what the project is, how to run it, where standards live. Procedures move out into something the agent can be handed one step at a time. Rules move into standards documents that a step points to when they apply. Lessons move into memory that is recalled when relevant.

in convops

How does an agent instruction file work in ConvOps?

With ConvOps, the instruction file can shrink to a few lines that say how to work: get the current step of your task, do only that step, advance and record why. The process lives in workflows the agent walks over MCP, policies arrive inside the step they govern, and what past runs learned comes back through memory and routes. The file stops growing, because new knowledge goes into the process instead of the prompt.

questions

What do people ask about an agent instruction file?

What is the difference between CLAUDE.md and AGENTS.md?

CLAUDE.md is the file Claude Code reads. AGENTS.md is an open format meant as one predictable place for coding-agent instructions, supported by tools such as OpenAI Codex and Cursor. The content is similar: how to build, test and work in the project.

How long should a CLAUDE.md file be?

As short as it can be while every line applies to every session: what the project is, how to build and test it, where standards live. A long file costs context on every session and mixes rules that apply only to some tasks.

What replaces a long instruction file?

A split. Procedures go into workflows handed over one step at a time, task-specific rules into policies or standards a step points to, and lessons into memory. With ConvOps the file shrinks to a few lines on how to work.