Hwip Docs
Agents

Agents

Which coding agents Hwip works with, and what reaches your phone for each.

Hwip works with five agents that have their own page here. Each one gets the same list in the app and the same buttons.

AgentQuestionsApproval prompts on the phoneLive timeline
Claude Codehwip_ask toolBash command, file edit, new fileYes
Codex CLIhwip_ask toolNot read yetYes
Gemini CLIhwip_ask toolTool approvalsYes
pihwip ask commandExtensions that ask through ctx.ui.selectYes
OpenCodehwip_ask toolPermission requestsOpenCode 2.x
The Hwip app's session list: sessions grouped by project, one marked Needs you.

Beyond these five

  • Setup (hwip install) also covers Cursor, Windsurf, Copilot CLI, Cline and Aider: ten agents in total.
  • Remote input works with 16 agent CLIs: the wrappers (hwip cc, hwip codex, hwip pi, and so on) start any of them in a tmux session your phone can type into.

How every page is wired

  1. hwip install writes the agent's own configuration: rules, hooks, an MCP server or a plugin, depending on what the agent supports. Your own entries in shared settings files are kept.
  2. hwip <agent> starts the agent in a tmux session named hwip-<project>. That is what lets the phone type into it.
  3. A question carries the session's git diff against HEAD and its last 60 terminal lines, sealed on your machine before it is sent. See What the server sees.

tmux is required. On Windows, that means WSL. Setup is covered in Get started and remote control in Remote control.

On this page