Set up Codex for a repository

Connect ToDoddle through the generated MCP configuration, then keep repository-specific operating rules in AGENTS.md. Codex reads these files when a run starts and combines global guidance with repository and nested-directory guidance. Files closer to the working directory take precedence. See the official OpenAI AGENTS.md guide.

Useful repository guidance includes:

• where code lives and which package manager to use;
• required type, test, documentation, and quality commands;
• safe handling rules for databases, credentials, and production systems;
• the ToDoddle project ID and expectation that tracked work stays current;
• when time should or should not be recorded;
• whether commits or pushes require confirmation.

Keep product intent in the ToDoddle project brief and specifications rather than duplicating it in every repository. Keep AGENTS.md concise and operational. Use nested instructions only when a directory genuinely needs different commands or review rules.

A custom role such as reviewer, release agent, or frontend implementer is behavioral guidance—not authorization. Use the Agent Connection label to identify it in ToDoddle, then enforce actual access with scopes and project grants.

After changing MCP configuration or instruction discovery settings, restart Codex or open a new task. Ask it to identify its loaded instructions, discover ToDoddle tools, and read one known project before allowing mutations.

The same ToDoddle workflow remains portable to other MCP-compatible agents: retain vendor-neutral project Context, task evidence, connection labels, scopes, and grants.