OnepilotJoin
Onepilot mascot

Onepilot vs Clawket

Both put your agent on your phone — but they connect to it differently. Clawket is a companion client for an agent you've already set up. Onepilot deploys the agent for you and gives you the whole host over SSH. Here's the honest, useful difference.

TL;DR

Clawketis a polished open-source mobile companion (iOS + Android) for OpenClaw and Hermes — chat with the agent, manage skills, cron, and tools, with a fun pixel-art view. It connects to an agent you've already deployed. Onepilot deploys the agent for you and connects over a real SSH tunnel, adding a true terminal, a file browser for skill files, git diffs, and cron — plus Claude Code and Codex in the same app. Want a focused chat-and-ops companion? Clawket is great. Want deploy + full shell-level control across frameworks? That's Onepilot.

Deploy and fully control Hermes from your iPhone — one email when Onepilot ships.

At a glance

ClawketOnepilot
OpenClaw & HermesYesYes
Claude Code / CodexYes (in terminal)
Deploys the agent for youBring your ownYes (SSH wizard)
Chat & manage skills/cronYesYes
Real interactive terminalYes
File browser + git diffsYes
ConnectionGateway / APISSH tunnel
PlatformsiOS + AndroidiOS (iPhone + iPad)

Based on each project's public description as of May 2026. Clawket is open source on the App Store and GitHub.

Where Clawket shines

If you've already got an agent running and you want a focused, friendly app to talk to it and tweak its skills, cron, and tools, Clawket is a genuinely nice piece of work. It is open source, it is on both iOS and Android, and the pixel-art agent view gives it personality most utilities lack. For chat-plus-operations on an existing agent, it does the job well.

Where Onepilot goes further

It deploys the agent. Onepilot SSHes into a host you own and installs the agent under nvm with no sudo, wires the provider and channel, and starts it — so you don't have to hand-install before you can use a mobile client.

It gives you the host, not just the agent.Over its SSH tunnel you get a real terminal, a file browser to read the skill files Hermes writes, a git tab with real diffs, and cron. That's the gap between operating the agent and operating the machine it runs on.

It spans more frameworks. OpenClaw and Hermes through the wizard, plus Claude Code and Codex in the terminal — one app for every agent on the box.

FAQ

What is Clawket?

Clawket is an open-source mobile companion app for AI agents, available on iOS and Android, that supports OpenClaw and Hermes. It lets you chat with your agent, see its responses, and manage skills, cron jobs, and tool settings, with a playful pixel-art view of your agent. It's a well-made client for talking to and operating an agent you've already set up.

How is Onepilot different from Clawket?

The biggest difference is the connection model. Clawket is a companion client that connects to an agent you've already deployed and talks to it through its gateway/API. Onepilot opens a real SSH tunnel to the host: it deploys the agent for you through a wizard, then gives you the host itself — a real interactive terminal, a syntax-highlighted file browser, a git tab with real diffs, and cron. So Clawket is excellent for chatting with and operating an existing agent, while Onepilot also handles setup and gives you full shell-level control of the machine the agent runs on.

Do both support OpenClaw and Hermes?

Yes — both are multi-framework on that front. Clawket supports OpenClaw and Hermes. Onepilot deploys OpenClaw and Hermes through its wizard and, because it includes a real terminal, also runs Claude Code and Codex CLI once they're installed on the host. If running coding agents like Claude Code or Codex alongside Hermes matters to you, that's a point of difference.

Does Clawket set up the agent for me?

Clawket is primarily a client for an agent you've already installed and configured on a host — you bring the running agent, it gives you a mobile interface to chat and manage it. Onepilot includes the deploy step: it SSHes into a host you own, installs the agent under nvm with no sudo, wires the LLM provider and the messaging channel, and starts it as a background process. If you'd rather not hand-install the agent first, that deploy flow is the difference.

Why would I want a terminal and file browser instead of just chat?

Chat is great for directing the agent, but some things need the host. Reading the actual skill files a self-improving agent like Hermes writes, inspecting a git diff to verify exactly what changed, tailing a log when the gateway won't start, or running an arbitrary command to fix something — those need shell access, not a chat box. Onepilot's SSH tunnel gives you that. It's the difference between operating the agent and operating the whole machine it lives on.

Are they mutually exclusive?

No. They connect to the agent differently, so you could use either or both — the agent is the same process on the same host. Many people will prefer one app for everything; Onepilot aims to be that one app by covering deploy, chat-channel routing, and full SSH control across multiple frameworks. Clawket is a strong choice if a focused, playful chat-and-ops companion is what you want.

Deploy and fully control your agent

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

See also: The Hermes app, Hermes WebUI vs native app, or Run Hermes on iPhone.