Organisation-wide agent rules
The project note tells the coding agents working in one repository to protect the tools that pay, delete, send messages, run commands, push code or edit secrets or config. The organisation note is the same text for every repository of a company, set once by an administrator in each coding agent's organisation-level instructions.
signafAIde is installed per project, and an organisation rule also reaches repositories that do not have it yet. So the organisation note adds one sentence: in a repository without signafAIde, install it there first. It also names npx signafaide check --ci, the CI check. Nothing in these files installs signafAIde, sends anything or creates an account.
The files are in the open repository, in agents/team/, generated from the same source as the project note, and a test keeps them equal. Take the one for your tool and put it where the table says.
| tool | file | where it goes | vendor documentation |
|---|---|---|---|
| Claude Code | claude-code/CLAUDE.md | The managed policy CLAUDE.md: /Library/Application Support/ClaudeCode/CLAUDE.md on macOS, /etc/claude-code/CLAUDE.md on Linux and WSL, C:\Program Files\ClaudeCode\CLAUDE.md on Windows, placed by MDM, Group Policy, Ansible or similar. It applies to every user on the machine, in any repository, and a developer cannot exclude it. | Deploy organization-wide CLAUDE.md |
| Claude Code, as a setting | claude-code/managed-settings.d/50-signafaide.json | The same text in the claudeMd key, as a drop-in next to managed-settings.json: /Library/Application Support/ClaudeCode/managed-settings.d/ on macOS, /etc/claude-code/managed-settings.d/ on Linux and WSL, C:\Program Files\ClaudeCode\managed-settings.d\ on Windows. Use this or the CLAUDE.md file, not both. Drop-ins merge in alphabetical order, so a later file that also sets claudeMd replaces this text: put the note into that file's claudeMd instead. | The claudeMd key, managed settings and drop-ins |
| Cursor | cursor/team-rule.md | Team Rules in the Cursor dashboard (Team and Enterprise plans). Paste the text as a new rule with no glob, so it applies to every conversation, and turn on enforcement so members cannot switch it off. Team Rules are free text and apply across all repositories of the team. | Rules: Team Rules |
| GitHub Copilot | copilot/organization-instructions.md | The organisation's settings: Copilot, Custom instructions, "Preferences and instructions" (Copilot Business or Enterprise). GitHub applies them on github.com (Copilot Chat, the cloud agent) and in Copilot code review, not in local IDE sessions, and on github.com they rank below personal and repository instructions. In IDEs, the per-project AGENTS.md that protect writes carries the note. | Adding organization custom instructions, About customizing responses |
| Codex | codex/config.toml | developer_instructions is a documented config.toml key ("additional developer instructions injected into the session"). An administrator sets it in the cloud config.toml (Edit as TOML), in config_toml_base64 of the com.openai.codex macOS MDM domain, or in the managed defaults file /etc/codex/managed_config.toml (Unix) or ~/.codex/managed_config.toml (Windows). Merge the key into a file that already exists rather than replacing it. Managed defaults are starting values a user can change. | Config reference, managed configuration, AGENTS.md |
| Windsurf (Devin Desktop) | windsurf/signafaide.md | System-level rules (Enterprise): every .md file in /Library/Application Support/Windsurf/rules/ on macOS, /etc/windsurf/rules/ on Linux and WSL or C:\ProgramData\Windsurf\rules\ on Windows is loaded in every workspace, and end users cannot delete it. The newer Devin Desktop documentation gives /etc/devin/rules/ as the Linux path, with /etc/windsurf/rules/ as the legacy one; check which your installed version reads. | Windsurf memories and rules, Devin Desktop rules |
Not covered #
These tools document no organisation-level instructions, so there is no file for them:
- Gemini CLI. System settings files exist (
/etc/gemini-cli/settings.jsonand others), but the enterprise guide describes no instructions orGEMINI.mdfor all users. The per-user~/.gemini/GEMINI.md, or the project'sGEMINI.mdthatagent setupwrites, carries the note. - **Codex
AGENTS.md.** It exists only per user (~/.codex/AGENTS.md, or underCODEX_HOME) and per project. A company can place the note there for each user with its own tooling, but that is not an organisation setting.
What these rules do not do #
They are guidance the agent reads. They do not make a tool protected, and an agent that ignores them leaves the tool as it was. The check that holds in every repository is npx signafaide check --ci in CI: it fails a pull request that adds a tool that pays, deletes, sends, runs commands, pushes code or edits secrets or config without protecting it. See CI check.