Reference · Primitive map

Same six pieces, two tools

Reproduced from Addy Osmani's comparison table. The names differ; the capability does not.

Primitive	Job in the loop	Codex app	Claude Code
Automations	discovery + triage on a schedule	Automations tab: project, prompt, cadence, environment. Results land in a Triage inbox. `/goal` for run-until-done	Scheduled tasks and cron, `/loop`, `/goal`, hooks, GitHub Actions
Worktrees	isolate parallel features	Built-in worktree per thread	`git worktree`, `--worktree`, `isolation: worktree` on a subagent
Skills	codify project knowledge	Agent Skills (`SKILL.md`), invoked with `$name` or implicitly	Agent Skills (`SKILL.md`)
Plugins / connectors	connect your tools	Connectors (MCP) plus plugins for distribution	MCP servers plus plugins
Sub-agents	ideate and verify	Subagents defined as TOML in `.codex/agents/`	Task subagents in `.claude/agents/`, agent teams
State	track what's done	Markdown or Linear via a connector	Markdown (`AGENTS.md`, progress files) or Linear via MCP

Why this matters Once you notice the shape is the same, you stop arguing about which tool. You design a loop that still works no matter which one you happen to be sitting in.

Source: Addy Osmani, Loop Engineering. Vendor docs: Codex automations, Codex skills, Codex subagents.