agnostic-ai

Type to search the docs and updates.

Browse documentation
DocsReference

Compare targets

Pick two tools to see what agnostic-ai sync writes for each spec kind, and where. Target C is optional: pick one to compare three. The page URL keeps the choice, so you can share a comparison.

Claude Code and Codex: 2 of 10 spec kinds differ in support, 3 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
Opt-in
SettingsFormat differs
NativeJSON
  • .claude/settings.json
NativeTOML
  • .codex/config.toml
Code reviewTool-specificDiffers
No output
NativeMarkdown
  • AGENTS.md
Dev setupTool-specific
No output
No output
Ignored files
No output
No output

Where the data comes from

Support states come from the capability matrix. Paths come from a real sync of one sample spec per kind, and CI fails when either drifts from the adapters. File formats come from each path's extension. A file that holds more than one kind, such as .claude/settings.json, appears under each kind that writes to it.

This page compares output files, not how each tool behaves once it reads them. Open a target page for field-level caveats and the config keys an Opt-in kind needs.