ECX: everything claude codex

Real, unedited. A codeword told to Codex by voice. A minute later Claude knows it, without reading a single file.

Claude Code and Codex, working as one team. Two agents from two different labs share one memory and see each other's latest messages, so you can start a task in one and finish it in the other without explaining anything twice. Around that team: every session starts already knowing you, your notes are searchable by meaning, the setup checks its own tools before they break, and it keeps working from your phone with your laptop shut.

Not a skills pack. It runs alongside packs like Superpowers instead of replacing them.

Built and battle-tested every day for 6 months by @nerfsaksham, 3x hackathon winner. It's the setup behind 37 shipped projects. Install it in 30 seconds.

you talk to either agent  ->  both remember  ->  your notes answer  ->  your phone keeps going

Install in 30 seconds

git clone https://github.com/saksham10arora-dotcom/everything-claude-codex ~/ecx
cd ~/ecx && ./install.sh

It asks two questions (where your notes live, your first name) and wires everything in. It's safe to re-run, never overwrites your files, and backs up every settings file it touches.

Want the full stack?

./install.sh --vault ~/vault --name Ada --with-search --with-cron --with-phone

Then open Claude Code in your vault and type /boot.

Things your setup can't do yet

Without a system vs. with ECX

What's inside

everything-claude-codex/
|-- agent-sync/      Claude <-> Codex: each sees the other's newest messages, plus agent-to-agent mail
|-- skills/          18 skills: boot, daily, weekly, catchup, opps, outreach, email, content, brand, resume,
|                    money, project, summary, ship, tldr, wiki, wiki-health, video-notes
|-- hooks/           tests before done, guard, MCP health, session memory, inbox, archive, AI-tell guard, usage
|-- vault-search/    3 MCP servers (meaning, graph, router) + image search + nightly indexers
|-- phone-vault/     after-every-reply GitHub sync, phone capture auto-merge, cloud boot rules
|-- memory/          keeps hot.md current after every /compact
|-- watch-notes/     video -> key frames + transcript, for /video-notes
|-- statusline/      context bar + unread mail from Codex
|-- templates/       CLAUDE.md, AGENTS.md (Codex boots knowing what Claude knows), hot.md
|-- scripts/         install.py, doctor.py
`-- tests/           27 tests, macOS + Linux, Python 3.9 to 3.12

How it fits together

flowchart LR
  you((You)) -- types --> CC[Claude Code]
  you -- talks --> CX[Codex + voice]
  CC <-- agent-sync: newest messages + mail --> CX
  CC & CX -- boot from --> M[(hot.md + memory)]
  CC & CX -- MCP --> S[Vault search: meaning, graph, images]
  M & V[(Your vault)] -- sync after every reply --> GH[(Private GitHub repo)]
  phone((Phone, laptop shut)) -- Claude app / ChatGPT app --> GH

The pieces

1. Memory that knows you

hot.md holds what's true right now: deadlines, projects, hard rules. A hook loads it, plus your last sessions, before your first message. After every /compact, it's refreshed automatically. Codex reads the exact same files through AGENTS.md, so it knows what Claude knows.

2. agent-sync: two agents, one conversation

Before every message, a hook hands each agent the newest lines of the other's chats, Codex voice transcripts included. Local, one Python file, stdlib only. They can also mail each other directly (sync.py send), and you get a readable log in agents/AGENT_CHAT.md.

3. Vault search, three ways

• By meaning: "notes about latency" finds them even if the word never appears.
• By relationship: "how does my engine relate to my competition strategy" walks a knowledge graph.
• By image: "the slide with the architecture diagram" searches your slides, screenshots and PDF pages, and tells you which note each one lives in.

A router picks the right one. All of it re-indexes every night.

4. Phone vault: laptop shut, still works

After every reply, your notes and a copy of your memory sync to your private GitHub repo. On your phone, Claude (Claude app) and Codex (ChatGPT app) work on that repo in the cloud. Say "I met Adi, he's at X": one note lands in inbox/, a GitHub Action merges it, and Claude files it next time you open your laptop.

5. Self-healing hooks

• Tests before done: when Claude Code or Codex tries to finish, your tests run first. If they fail, the agent is sent back with the failing output and has to fix it. It runs only when something changed, finds npm, pytest, unittest, cargo, go and make tests on its own, and gives up after 3 tries instead of looping. Set the command per repo in .ecx/test-command (or off).
• Danger guard: blocks rm -rf ~, disk formats and fork bombs; asks before force-pushes, reset --hard and DROP TABLE.
• MCP health: refuses to call a server whose dependency is down (and tells you the fix) instead of letting it return empty answers.
• doctor: 16+ checks across hooks, indexes, jobs and sync. It also runs at the start of every Claude Code and Codex session: silent when everything is healthy, a short warning with the fix (and the index's last update time) when not.

6. Skills that run your week

/boot gives you a 30-second briefing. /daily starts the day. /opps is your opportunity pipeline with eligibility checks. /outreach and /email handle networking with a paper trail. /content and /brand are a content machine in your voice. /catchup continues another window's chat. /ship commits, pushes and proves it.

Guides

• The longform guide: how the whole system was built, what broke, and why.
• agent-sync deep dive

Works great with

ECX plays well with these (not bundled, all worth installing): [