Цю сторінку ще не перекладено.

Make your team's coding agents follow an instruction

A coding agent is an AI tool that works on code in a project's folder, such as Claude Code, Codex or Cursor. This page explains how such a tool follows one of your instructions, which setup fits your team, and what to hand to a developer to set it up.

What following means for a project

When a project follows an instruction, the coding agent gets the instruction at the start of every session in that project's folder. When you publish a new version, a session that is already running gets it too, usually at the developer's next prompt. Nobody has to restart anything or copy text by hand.

The project keeps the instruction's address in a small file of its own, the follow file. The developer adds that file to the project's shared code, so everyone who works on the project follows the same instruction, at the same version.

A coding agent reads the instruction; it doesn't hold a live update. Reading is never limited, on any plan. So every developer's sessions can follow, even on a plan that gives live updates to only a few agents at a time.

Choose who follows it

Who How Who sets it up
One project The project's follow file, shared with the code. Everyone who works on the project follows it. A developer on the project, with one command from the editor.
Every project on one computer The coding agent's own settings on that computer. Good for a developer's personal instruction. The developer, on their own computer.
Every developer in the company Settings your IT team installs on every computer. Developers can't turn them off. Claude Code and Codex only. IT. See Roll out to developers.

Most teams start with one project. Choose company-wide settings when the instruction is a rule everyone must follow, such as a security policy.

Get the setup from the editor

The editor gives you the exact setup for each tool. You don't type it yourself: you copy it and give it to a developer, or run it if you are one.

  1. Open the dialog

    Open the instruction and choose Share ▸ Follow in your coding agent…. If it isn't published yet, the dialog says Publish it first: a project follows it by its address on instruction.md. Publish it, then come back.

  2. Pick the tool

    Under 1. Your coding tool, pick the tool your team uses: Claude Code, Codex, Cursor, GitHub Copilot CLI, Gemini CLI and others.

  3. Pick the version

    Under 2. The version to follow, pick one:

    • latest (and any other name the instruction has, such as stable (now v4)): Your agent moves to each new version this name points to.
    • Only v4 (the version people see now): Your agent stays on this version until you choose another.

    A stable version exists only once someone creates it. A stable version shows how.

  4. Copy the setup

    For most tools, the dialog says 3. Run this in your project's folder and shows one command. Choose Copy and give it to the developer, who runs it once in the project's folder. It adds a few small files, and the developer shares the follow file with the rest of the code.

    For a tool that is set up another way, the dialog says 3. Add this to …'s settings and shows what to add.

  5. Sign in, if it isn't public

    If the instruction isn't public, the dialog shows a second line: the developer signs in once on that computer with their instruction.md account. A public instruction says It's public: no sign-in needed.

A developer who would rather add the files by hand can open Show the files instead.

Share ▸ Follow in your coding agent… gives the setup for one tool and one version.

When a new version reaches a running session

Every tool gets the instruction when a session starts. They differ in when a session that is already running gets a new version.

Tool A new version arrives
Claude Code, Codex at your next prompt, or after the agent next uses a tool
Gemini CLI, Qwen Code, Factory Droid, Devin, Kiro, Cline at your next prompt
Antigravity before the agent's next step
GitHub Copilot CLI, Cursor, JetBrains Junie, Crush after the agent next uses a tool
OpenCode, Kilo Code, Goose, Aider when the tool reads its instructions file again. A small helper the developer leaves running keeps that file up to date.
VS Code when the developer asks the agent to follow it

Some tools ask the developer to trust the project's settings once, the first time. Claude Code does. The full table, with every tool's setup, is in Other coding agents.

What a developer sees when a version changes

When a new version arrives, the session shows one line, for example:

text
instruction.md: acme/support-agent v4 → v5

If the project only accepts signed versions, the line ends with (signature verified). The agent gets the new text, and goes on with the developer's request.

The session can also say:

  • a newer version … is held: the new version can't be used yet, so the agent keeps the one it has;
  • couldn't be read now … using the last good copy: instruction.md couldn't be reached, so the agent uses the last version it had;
  • couldn't read … this session goes on without it: there is no copy at all yet, for example on a computer that was never signed in.

The agent never stops because instruction.md is out of reach. It keeps the last version it had.

Tools that report back show up in the instruction's Agents card, with the version each one has and the app it runs in. See which agents follow an instruction.

What a developer sees when a new version arrives in a running session.

Common misunderstandings

  • Following a draft. Agents follow published versions, never the draft. Your changes reach them when you publish.
  • Pinning by accident. Only v4 never moves. Pick latest or stable if you want the agent to get new versions.
  • Following stable before it exists. The dialog lists stable only once someone has created it. A setup written by hand that names stable before then gives the agent nothing to read.
  • One computer, not the team. A tool's own settings on one computer reach only that developer. To reach the whole team, share the project's follow file.

Hand it to the right person

Questions

How do I make my team's Claude Code or Codex follow an instruction?

Open the instruction and choose Share ▸ Follow in your coding agent…. Pick the tool and the version, copy the command, and have a developer run it once in the project's folder. Everyone on the project then follows it. See Get the setup from the editor.

Does a running session get my new version?

Yes, in most tools. Claude Code and Codex get it at the developer's next prompt; other tools after their next step, or when they read their instructions file again. In VS Code, the agent reads it when the developer asks it to follow it. See When a new version reaches a running session.

Does following count against the free plan's live updates?

No. A coding agent reads the instruction; it doesn't hold a live update. Reading is never limited. See What following means for a project.

What happens if instruction.md can't be reached?

The agent keeps the last version it had, and says so in one line. It doesn't stop working. See What a developer sees when a version changes.

For developers: How following works explains the follow file, the setup each tool gets, and what happens offline.

Last checked against the product:

Was this page helpful? Report a problem