Claude Code hook

Codex Claude Bridge

Claude Code and Codex CLI talk to each other through one markdown file in your project. No server, no hooks, no plugin.

63 stars 10 forksHooks Source

Install

From source
git clone https://github.com/abhishekgahlot2/codex-claude-bridge.git

From the README

Codex Bridge

Claude Code and Codex CLI talk to each other through one markdown file in your project.
No server, no hooks, no plugin. You read along.

Quick start

1. Add talkto.md to your project root:

2. Open claude and codex in that project, or in any of its git worktrees.

3. Tell one of them what to discuss:

4. Tell the other one check talkto.md. From then on they keep going on their own.

How it works

The rules sit at the top of talkto.md, so each agent learns the protocol by reading the file. There is nothing to install.

1. An agent appends a message that ends with Waiting on:  — .
2. It runs the watch command from the file in the background.
   - Claude Code runs it with Monitor and is woken when it prints.
   - Codex CLI runs it in a background terminal and keeps polling, so its turn stays open.
3. The watch exits when a complete message addressed to that agent appears. The agent reads it, replies, and waits again.
4. Waiting on: nobody — done ends the conversation.

The watch compares against the agent's own last message, not a line count. A reply that lands before the watch starts is still caught, and a half-written one waits until its Waiting on: line exists. Every git worktree resolves to the main checkout's talkto.md.

Message format

Optional: skip naming the file

Add one line to AGENTS.md, which Codex reads, and to CLAUDE.md, which Claude reads:

Then discuss this with codex is enough.

Limits

- An agent waits only while its turn is running. If Esc, an error or a usage limit cuts a turn short, say check talkto.md.
- Both agents must run on the same machine.
- Anything appended to talkto.md reaches both agents as a message.
- Agents read only the latest messages, but a long file still costs context. Start a fresh file when a topic is…
Read the full README on GitHub

How hooks work

  • Hooks are shell commands Claude Code runs at fixed points: before or after a tool call, when you submit a prompt, when Claude stops, on notifications and at session start.
  • They are set in the hooks section of ~/.claude/settings.json (or .claude/settings.json for a project), or come bundled in a plugin.
  • A hook can block a tool call, add context, or run a formatter or test. Read the scripts before you install them: they run on your machine with your permissions.
Claude Code docs

Details

Type
Hooks
Last updated
8 October 2026
Topics
agent-to-agentai-agentsclaudeclaude-channelsclaude-codecodex-climcpmodel-context-protocolopenaiopenai-codex

FAQ

What is Codex Claude Bridge?

Claude Code and Codex CLI talk to each other through one markdown file in your project. No server, no hooks, no plugin. It is a hook for Claude Code, from abhishekgahlot2/codex-claude-bridge on GitHub.

How do I install Codex Claude Bridge?

Clone abhishekgahlot2/codex-claude-bridge from GitHub and follow the setup steps in its README.

Is Codex Claude Bridge popular?

abhishekgahlot2/codex-claude-bridge has 63 GitHub stars and 10 forks. It was last updated on 8 October 2026.

More hooks

Browse the most popular Claude Code mods, all hooks, or the skills and MCP server directories.