OpenCode

When OpenCode 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 ~/.config/opencode/AGENTS.md has OpenCode ask through the hwip_ask tool: up to four buttons and a text field.
• Permission requests. When OpenCode asks for permission, the phone shows what it wants to do and its buttons. If you answer at the keyboard first, the phone's answer is refused.
• A finished turn. A "Task done" push with the project and branch.
• The live timeline. Prompts, tool calls and replies, read from OpenCode's own session store.
• 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 ~/.config/opencode/opencode.json, adds an idle-notify plugin, and writes the rule to ~/.config/opencode/AGENTS.md. If OpenCode is already running, run opencode reload so it loads the plugin. Start OpenCode through Hwip:

hwip opencode

It runs in a normal tmux session named hwip-<project>.

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

• The live timeline needs OpenCode 2.x. It reads the session store that 2.x keeps.
• tmux is required. On Windows, that means WSL.

See also Remote control and the MCP tools.