Codex CLI

When Codex CLI stops to ask you something, Hwip sends the question to your iPhone and types your answer back into the same tmux session.

What reaches your phone

• Questions. A rule in ~/.codex/AGENTS.md has Codex ask through the hwip_ask tool: up to four buttons and a text field.
• A finished turn. A "Task done" push with the project and branch.
• The live timeline. Prompts, tool calls and replies, read from Codex's own session log.
• Your prompts. Type a prompt on the phone, and it lands in the session as if you typed it at the keyboard.

How it is wired

hwip install registers the Hwip MCP server in ~/.codex/config.toml, adds prompt and stop hooks, and writes the rule to ~/.codex/AGENTS.md. Start Codex through Hwip:

hwip codex
hwip codex "fix the failing test"

It runs in a normal tmux session named hwip-<project>, and arguments pass through.

What a question carries

The session's git diff against HEAD and its last 60 terminal lines. Secret-looking text is masked first, best effort. Everything is sealed on your machine with AES-256-GCM before it is sent. What the server sees.

Limits

• Codex's own approval prompts stay on the computer. Approve those at the keyboard.
• tmux is required. On Windows, that means WSL.

See also Remote control and the MCP tools.