Codex

Message yourself from Codex and answer back into the session.

Plugin route

1. Put sock and sock-mcp on PATH.

2. Sign in, then pick the puppet Codex sends as:

   sock login
   sock puppets use <puppet id>
   

   This writes a puppet token to ~/.config/sock/config.toml (mode 0600), where the plugin's sock-mcp reads it. A plugin's server never sees your shell's SOCK_TOKEN.

3. Add the plugin:

   codex plugin marketplace add aeryx-ai/sock-integrations
   codex plugin add sock@sock-integrations
   

4. Run /hooks in Codex and trust both hooks.

With a machine key in the config file (sock machine-key use) the plugin sends as each project's own puppet, named <repo> on <host>, and your replies come back into the session that asked.

What it does

Outbound only. Hooks message you when Codex needs permission and, at the end of a turn, with the trailing question or decision. The model can also call sock_send.

Hooks send from the TUI or the Codex app, at most once an hour per project. codex exec and subagents never message you, and a sock_send reply is never held back.