AgentHost Client
Connect to your AHP servers, follow sessions live, and take control from wherever you are.
Get it on the app stores:
iOS and Android
A phone interface for whatever your host advertises. The app adapts to the capabilities on offer instead of assuming how your agent works.
Start sessions, follow each step, and step into the conversation the moment an agent needs a decision.
Connect AHP machines and servers. See where your agents are available, and move between them without losing the thread.
Create and follow automations on your own hosts. See when the next one runs, how the last one ended, and what wants attention.
Walk the resources a host exposes, read documentation, and check what changed without switching apps.
Open a terminal session on the host from your phone. Investigate, confirm and run without leaving the flow.
Manage connections, appearance, language, text size and security. On a phone, tokens live in the system keystore.
On an iPad or a desktop the app opens into a shell: the destinations and the session list on the left, the session beside it, and a context pane for what changed, the skills and the MCP servers. One client, at three widths.
Your agents already run on a machine you own, so keep them there. Start a host in the editor you have open, or run the reference host on a laptop, a VM or a container: the app is the window onto it, and nothing of ours sits in between.
Any server that speaks AHP will do, and these two are the easiest place to start. Whichever you pick, it is yours, and only you run it.
Nothing to create, no account, no cloud in between. Give the app the address of the server you just started.
An address and a port. ws:// is assumed if you leave the scheme out.
Your host writes a connection token when it starts. Paste it here. A wrong token is refused at the WebSocket handshake, so it appears as a failed connection rather than a protocol error.
Open a workspace and start a session, or schedule an automation to run on its own. Everything the host publishes arrives in the inbox, ordered by which one needs you.
The token is not an account and it is not ours. It is the secret your own server generated, and it stays on your device.
For iOS and Android, through the App Store and Google Play. The store handles the payment and the updates.
Beyond your own network: put it on a mesh VPN first, then a TLS tunnel. Never forward a bare port. Whatever is behind that port can read and write your filesystem as your user.
US$ 9.87 a month, billed by the App Store or Google Play. Cancel from your store account at any time, and you keep access until the end of the period you already paid for.
No. It is a client, so it needs a host to connect to, the way a browser needs a site. Setting one up is a single command on the machine that runs your agents.
No account, no login, no cloud. You enter your own host address and token, and both stay on your device.
Only to the host you configured, over the connection you configured. There is no backend of ours in the path and the app has no analytics.
Any server that speaks the Agent Host Protocol, including the reference host and the VS Code agent host. The app reads what a host advertises at the handshake rather than assuming a version.
AgentHost Client
Leave the desk. Stay in control.
