Cette page n’est pas encore traduite.

Roll an instruction out to every developer

This page is for team leads and admins who want every developer's coding agent to follow the same instruction, such as a security policy. Your IT team installs a setting on every computer once. From then on, every Claude Code or Codex session on those computers gets your instruction, and each new version you publish, without anyone setting anything up.

How a company-wide rollout reaches every developer's coding agent.

What a company-wide rollout is

Most teams start with one project: a developer adds a small file to the project, and everyone who works on it follows the instruction. See Make your team's coding agents follow an instruction.

A company-wide rollout goes further. Claude Code and Codex each let a company install settings that apply to every session on a computer. IT puts them on every developer's computer the same way it installs other company settings, for example with the device management tool it already uses. These settings name your instruction. Developers don't have to do anything in their projects.

Once the settings are in place:

  • every new session gets the whole instruction when it starts;
  • a session that is already running gets a new version at the developer's next prompt, and shows one line saying so, such as instruction.md: acme/support-agent v4 → v5;
  • each computer reports which version it applied, so you can see it in the editor.

It works with Claude Code and Codex. For other coding agents, use a project's follow file instead.

What developers can and can't turn off

Developers can't change or remove settings their company installed. Those settings sit above their own and their projects' settings.

IT can also turn on an option so that only the company's settings of this kind run. A developer's own add-ons of the same kind then don't run, and neither do those of a project that follows its own instruction with a follow file.

What the rollout does, and doesn't do:

  • It gives the agent your instruction to follow. The agent reads it at the start of the session, and again after each new version.
  • It doesn't lock what the agent can do. The instruction is guidance the agent is told to follow. To stop an agent from running some commands or reading some files, IT uses Claude Code's or Codex's own permission settings as well.
  • It keeps working offline. If a computer can't reach instruction.md, the agent uses the last version it had. A computer that has never read the instruction has no copy yet, and its sessions go on without it. IT can choose to stop such sessions instead.

If the instruction is shared only with your organization, each developer signs in to instruction.md once on their computer. A public instruction can be read without signing in, but a computer that isn't signed in reports nothing, so it never shows on the Agents card. To see every computer, have each developer sign in.

The rollout reads your instruction. It doesn't take a live update, so it works on every plan, including Community. See Plans, limits and billing.

Signed versions only

Every version you publish is signed for you by your organization. The signature says who published it, and a computer can check it.

You can make sure only checked versions reach your developers, in two places:

  • On the computers. IT can set them to apply only a version whose signature checks out. A version that doesn't is held, and the agent keeps the one it has.
  • On the version they follow. If developers follow stable, turn on Signed only for it, so stable moves only to a signed version. See Keep agents on a stable version. An admin can require this for every instruction at once in Developer ▸ Signing.

Pick which version developers follow before IT installs the settings. latest moves with every publish. stable moves only when you say, and exists only once you create it. For a company-wide rule, stable lets you check a version before every developer gets it.

Seeing it work

Open the instruction and its Agents card. Each developer's computer shows up once its first signed-in session has read the instruction, with the version it has. A line counts them by app, such as By app: 12 in Claude Code and 3 in Codex. The card also shows who is Behind or Paused. See See which agents follow an instruction.

The activity log records each time a computer applies a new version, such as "Dana applied v5 of Support agent in Claude Code". To see only these, open Settings ▸ Activity and pick Agents. See See who did what.

Hand it to IT

IT needs four things from you:

  • the instruction's address, such as acme/support-agent, and which version to follow (latest, stable or one version);
  • which tools your developers use: Claude Code, Codex or both;
  • whether computers should apply only signed versions;
  • whether developers sign in to instruction.md on their computers, which a private instruction needs, and which lets you see every computer on the Agents card.

IT then gets the exact settings from instruction.md and installs them. Their page is Managed agents. Every computer needs Node.js, a program most developer computers have already.

Common misunderstandings

  • "Developers have to set it up in each project." They don't. The company's settings apply to every session on the computer, in every project.
  • "It blocks what the agent may do." It doesn't. It tells the agent what to follow. Use each tool's permission settings to block actions.
  • "It needs a paid plan." It doesn't. The rollout reads the instruction, and reading is never limited.
  • "A new version waits until the developer restarts." It doesn't. A running session gets it at the developer's next prompt.

Questions

How do I make every developer's coding agent follow our instruction?

Ask IT to install company-wide settings for Claude Code or Codex on every developer's computer. Give them the instruction's address and which version to follow. Their steps are on Managed agents.

Can a developer turn it off?

No. Settings the company installs sit above a developer's own, and developers can't change them. See What developers can and can't turn off.

How do I know every computer has the new version?

Open the instruction's Agents card. It lists each signed-in computer with the version it has, and counts them by app. A computer marked Behind hasn't started a session or sent a prompt since the version it follows changed.

Does it work with tools other than Claude Code and Codex?

Not company-wide. For other coding agents, a developer adds the follow file to each project. See Make your team's coding agents follow an instruction.

For developers and IT: the settings files, where each tool reads them, and how to require signatures are in Managed agents.

Last checked against the product:

Was this page helpful? Report a problem