Onepilot

Agent frameworks on iPhone

Two ways Onepilot puts an agent on your iPhone: framework agents through a deploy wizard, terminal-native agents inside the SSH shell. Here is the current map.

TL;DR

Onepilot separates agents into two surfaces. Framework agents (OpenClaw, Hermes, Paperclip) install on any host you can SSH into — a Mac mini at home, a Raspberry Pi, a work laptop, a NAS running sshd, or a remote VPS — through a one-tap deploy wizard, then run as persistent background processes you supervise from your iPhone. Terminal-native agents (Claude Code, OpenAI Codex CLI) live inside the SSH session — the phone is the terminal. Both share the same primitives: SSH transport, iOS Keychain credentials, 23+ LLM providers, and channel routing through Telegram, Discord, or Slack. The list of supported framework agents grows by adding adapters, not by rewriting the app.

OpenClaw

Integrated in app

Personal AI assistant with a Gateway-and-nodes architecture.

Onepilot provisions the OpenClaw Gateway on any host you SSH into — your Mac mini, a Linux box at home, a Windows machine, a Raspberry Pi, or a $5/month VPS — and pairs the iPhone as a node. The Gateway lives wherever you put it; the iPhone is the supervisor.

In-process channel pluginBundled plugin snapshotSkill managementSoul markdownCron jobsFTS5 memory
Upstream: openclaw.aiRead the iPhone setup guide →

Hermes Agent

Integrated in app

Self-improving agent from NousResearch — Linux/macOS/WSL2/Termux only, until now.

Hermes does not officially support iOS. Onepilot deploys the Hermes runtime to any Linux or macOS host you can SSH into — a Mac mini at home, a Linux box, a Raspberry Pi, or a remote VPS — and drives it from iPhone via Telegram, Discord, or Slack.

Self-improving skillsProvider key envSkill managementSoul markdownCron jobs
Upstream: hermes-agent.nousresearch.comRead the iPhone setup guide →

Claude Code

Integrated in app

Anthropic's coding agent — already available through the Onepilot terminal.

Claude Code is a terminal CLI. Because Onepilot already includes a real PTY terminal, Claude Code works out of the box: SSH into your host, run claude, use it interactively. No wizard step needed. The value Onepilot adds is the layer around the shell — file browser, git, cron, channel routing, and an iOS Keychain-backed API key.

Available todayInteractive CLIRuns in PTY sessionRouted via the same SSH layer
Upstream: anthropic.com

OpenAI Codex CLI

Integrated in app

OpenAI's coding agent — already available through the Onepilot terminal.

Codex CLI is a terminal CLI like Claude Code. It works today inside the Onepilot SSH session — install it once on your host, then run codex from any PTY tab. iOS Keychain holds your API key; the file browser, git tab, and cron tab wrap around the shell.

Available todayInteractive CLIRuns in PTY session
Upstream: openai.com

Paperclip

On the path

Lightweight agent runtime targeted at single-purpose loops.

Paperclip routes through the same AgentFrameworkRegistry and GatewayTransportFactory as OpenClaw and Hermes. It will deploy through the same wizard once the adapter lands.

TBD when adapter ships
Upstream: internal roadmap

Why two surfaces, not one

Framework agents are persistent: they have their own runtime, memory, skill files, and event loop, and they expect to live on a host machine that stays up. The host is your call — a Mac mini in your closet, a Raspberry Pi on the desk, a NAS running sshd, a Windows tower at the office, or a $5/month VPS. The right deploy model is a wizard — pick the host, pick the LLM, pick the channel, walk away. That's where OpenClaw, Hermes, Paperclip live.

Terminal-native agents are interactive CLIs you run inside an SSH session. They start when you type their name and stop when you exit — no wizard step. Claude Code and OpenAI Codex CLI work in Onepilot today because Onepilot already includes a real PTY terminal: install the CLI once on your host, SSH in from your phone, and run it. Onepilot's value here is the layer around the shell: file browser, git, cron, channel routing, the same iOS Keychain that holds your framework-agent keys.

Both surfaces share one routing layer: the AgentFrameworkRegistry on the iOS side, and the SSH transport plus channel plugins on the server side. Adding a new framework agent means writing an adapter, not rewriting the app — which is why the “On the path” cards above are concrete plans, not vague promises.

Try the deploy wizard

Onepilot ships on the App Store soon. Drop your email and we'll send one note when it's live.

Join the waitlist