For hosts that speak AHP
Connect to your AHP servers, follow sessions live, and take control from wherever you are.
iOS and Android.
1 waiting on you
Hosts
Connect AHP machines and servers. See where your agents are available, and move between them without losing the thread.
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.
The whole app, with you
Your agents keep working while you’re away. Follow their progress, answer questions, approve actions, and pick up where you left off. All from your phone.
When an agent asks before it runs a command or edits a file, the request reaches your phone. Read what it wants to do, then decide.
02 Approvals
03 Changes
See exactly what your agent did, and what it cost.
01 Sessions
Start sessions, follow each step, and step into the conversation the moment an agent needs a decision.
06 Automations
Create and follow automations on your own hosts. See when the next one runs, how the last one ended, and what wants attention.
04 Resources
Walk the resources a host exposes, read documentation, and check what changed without switching apps.
05 Terminal
Open a shell on any connected host, or follow the one a session is running. The keys a phone keyboard lacks sit above it.
Before you start
Step one · your server
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.
VS Code ships an Agent Host, and it runs standalone as well as inside the editor. If VS Code is already where you work, you are a step away from a host.
code.visualstudio.comThe host this app is built and tested against. Free, open source, and happy on Node, Bun or Deno: your workstation, a server, a VM or a container.
github.com/softov/ahpdAny 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.
Step two · the app
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.
No small print
Nothing, during early access. Paid plans may come later. If they do, they are announced here and in the app first, and nothing is charged unless you choose to buy it.
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.
Leave the desk. Stay in control.
