agnostic-ai

Type to search the docs and updates.

Browse documentation
DocsDocumentation

Compare targets

Pick two coding tools, or add a third in Target C, to compare generated files by spec kind. Share the URL to keep your selection.

For example, with Claude Code and Codex, a shared rule becomes a Claude rule file and a Codex AGENTS.md section.

This page shows sample output paths. Before switching tools in an existing project, run agnostic-ai compare to check the fields in your own specs.

Claude Code and Codex: 2 of 10 spec kinds differ in support, 4 in file format.

This is the default comparison. Turn on JavaScript to pick other targets, or read the capability matrix.

Native
Dedicated target format.
Mapped
Another native format preserves the content.
Opt-in
Written after you enable an output setting.
Source only
Kept in .agnostic-ai, not written by default.
No output
No direct or safe mapped output.
Support state, file format, and native paths per spec kind. Rows marked Differs have a different state per target. Rows marked Format differs share a state but write different file formats.
Spec kindClaude CodeclaudeCodexcodex
AgentsFormat differs
NativeMarkdown
  • .claude/agents/test-writer.md
NativeTOML
  • .codex/agents/test-writer.toml
Skills
NativeMarkdown
  • .claude/skills/release/SKILL.md
NativeMarkdown
  • .agents/skills/release/SKILL.md
Rules
NativeMarkdown
  • .claude/rules/testing.md
NativeMarkdown
  • AGENTS.md
Hooks
NativeJSON
  • .claude/settings.json
NativeJSON
  • .codex/hooks.json
MCPFormat differs
NativeJSON
  • .mcp.json
NativeTOML
  • .codex/config.toml
CommandsDiffers
NativeMarkdown
  • .claude/commands/deploy.md
MappedMarkdownYAML
  • .agents/skills/deploy/SKILL.md
  • .agents/skills/deploy/agents/openai.yaml
SettingsFormat differs
NativeJSON
  • .claude/.agnostic-ai-permissions.json
  • .claude/settings.json
NativeTOMLJSONsh
  • .codex/config.toml
  • .codex/hooks.json
  • .codex/hooks/agnostic-ai-protect.sh
Code reviewTool-specificDiffers
No output
NativeMarkdown
  • AGENTS.md
Dev setupTool-specificFormat differs
NativeJSON
  • .claude/launch.json
NativeTOML
  • .codex/environments/environment.toml
Ignored files
No output
No output

Read the paths with care

Paths come from syncing one sample spec per kind. Files that hold several kinds, such as .claude/settings.json, appear under each. Check whether the tool loads each optional output. Codex, for example, can receive legacy project command files but does not load them. Check each target page for field limits and optional outputs.