Coding agents keep working on a server long after you close your laptop. Warpeer recognises them inside your remote sessions and tells you which ones need you, without opening every pane.
Supported agents
Warpeer recognises Claude Code, Codex, OpenCode, Gemini, Amp, Auggie, Copilot CLI, Cursor CLI, Droid, Goose, Pi, DSH and Command Code. Agents run as usual in tmux, Herdr or a plain shell. You do not need to change how you start them.
Agent states
Each session shows the state of the agent running in it:
| State | Meaning |
|---|---|
| Working | The agent is busy on a task. |
| Waiting | The agent finished its turn and is waiting for your next message. |
| Needs input | The agent is blocked on a question or a permission request. |
| Completed | The task finished. |
| Failed | The agent stopped with an error. |
| Detected | The agent is running, but its state could not be read. |
The state appears on the session card in the Sessions tab, in the session list when you connect, and on the terminal tab.
Session probe
Tap the chart button on a session card to open its probe. It shows the agent and model, token use (input, output and total), the working folder, the git branch and worktree, the list of changed files, and system details such as the distribution, kernel and architecture of the host.
How it works
The remote helper reads process and session information on the server and returns it to your iPhone over the same SSH connection. Nothing is sent to Warpeer, and nothing is typed into your terminal.