AGENTS.md for Codex? #1341
-
|
Hi Folks! Does anyone have a good AGENTS.md file when working with Codex? The current one which loads upon init, when selecting Codex, uses pretty heavy Claude Code verbiage and doesn't really address the nuances of Codex. Anecdotally it seems like Codex and/or Opencode have a strict adherence to agents.md and because the default file speaks so heavily towards Claude...it gets confused and the MCP encounters errors. Example: MCP IntegrationTask Master provides an MCP server that Claude Code can connect to. Configure in {
"mcpServers": {
"task-master-ai": {
"command": "npx",
"args": ["-y", "task-master-ai"],
"env": {
"ANTHROPIC_API_KEY": "your_key_here",
"PERPLEXITY_API_KEY": "your_key_here",
"OPENAI_API_KEY": "OPENAI_API_KEY_HERE",
"GOOGLE_API_KEY": "GOOGLE_API_KEY_HERE",
"XAI_API_KEY": "XAI_API_KEY_HERE",
"OPENROUTER_API_KEY": "OPENROUTER_API_KEY_HERE",
"MISTRAL_API_KEY": "MISTRAL_API_KEY_HERE",
"AZURE_OPENAI_API_KEY": "AZURE_OPENAI_API_KEY_HERE",
"OLLAMA_API_KEY": "OLLAMA_API_KEY_HERE"
}
}
}
}Codex uses config.toml as far as I understand. Another example would be: Tool Allowlist RecommendationsAdd to {
"allowedTools": [
"Edit",
"Bash(task-master *)",
"Bash(git commit:*)",
"Bash(git add:*)",
"Bash(npm run *)",
"mcp__task_master_ai__*"
]
}I'm not 100% certain on how to adjust these bits which directly leverage model-specific tooling, but I have at least tidy'd things up in the attached version. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Theres this PR that kind of fixes that: Wonder if that solves things for you ? |
Beta Was this translation helpful? Give feedback.
Theres this PR that kind of fixes that:
#1326
Wonder if that solves things for you ?