Claude Code

When Claude Code 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. Claude Code asks through the hwip_ask tool: up to four buttons and a text field. Its own AskUserQuestion sends a push too.
• Permission prompts. When a session waits on "Bash command", "Edit file" or "Create file", the phone shows the tool, the command or diff, and the numbered options. If you answer at the keyboard first, the phone's answer is refused.
• A finished turn. When you are away from the keyboard, a push with Claude's last summary.
• The live timeline. Prompts, tool calls, replies and Claude's to-do list, read from its transcript.

How it is wired

hwip install installs the Hwip plugin for Claude Code: hooks, an MCP server, and the /hwip-mode command. Start Claude Code through Hwip:

hwip cc

It runs in a normal tmux session named hwip-<project>, and arguments pass through (hwip cc --resume). The hooks fire in every Claude Code session, not only ones started with hwip cc; the wrapper is what lets the phone type into the session.

By default the plugin is quiet: you are pushed when Claude asks you something, and when a turn finishes after you have stepped away. Change it with /hwip-mode; see Push modes and How the plugin works.

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

• Other dialogs come without details. Plan approvals and MCP prompts show only that the session is waiting on you.
• tmux is required. On Windows, that means WSL.
• Claude Code has its own remote control. If Claude Code is the only agent you run, use it. Hwip is for running Claude Code next to Codex, pi or Gemini CLI.

See also Remote control and the MCP tools.