A phone remote for a browser agent, and the limits we put on it
Aside Pocket lets you watch and steer Aside Browser agent sessions from an iPhone. Notes on the architecture and on the permission rules a remote control for an agent needs.

I run a lot of browser work through Aside, an AI browser whose agents act inside my logged-in accounts. The agents run on my Mac, and checking on them meant going back to the desk. Aside Pocket is the small phone remote I built for that. It’s open source under MIT: github.com/khmuhtadin/aside-pocket.

Architecture
iPhone PWA --HTTPS over Tailscale--> bridge on 127.0.0.1 (Node) --> Aside CLI --> Aside
- A Node bridge on the Mac wraps the official Aside CLI and serves a web app. It listens on
127.0.0.1only. tailscale serveexposes it over HTTPS inside the owner’s tailnet. No port is opened to the internet and Tailscale Funnel is not used.- The phone side is a PWA installed from Safari, so there is no App Store build.
- Aside has no event stream, so the bridge polls the CLI: every 2 seconds while a session runs, every 15 seconds when idle.
What the phone can do
See every session in one inbox, read a session’s thread, start a task with a model and effort level, steer, queue, stop or archive a session, view routines and their last run, search memory read-only, and get a push notification when a session finishes, fails or waits for the owner.
The limits
A remote control inherits everything the agent can reach, so the bridge is narrower than the CLI it wraps.
- Two checks on every API call. The request must come from a Tailscale login on the allow-list and carry a bearer token.
- Short-lived pairing. A pairing code is 6 digits, works once, expires after 5 minutes and is dropped after 5 wrong attempts. Only its hash is stored.
- No permission escalation. Tasks started from the phone always run with Aside’s Guard permission. The bridge never passes full access.
- Routine retry off by default. A routine’s run session keeps the routine’s permission mode, which can be full access, so retrying it from the phone needs an explicit config flag.
- A list of calls the bridge never makes. It cannot delete sessions, change Aside settings, create or edit routines, or show the owner’s own tabs. The list is written down in the repo.
- Secrets stay local. The token, push keys and config live in
~/.aside-pocketwith directory mode 0700 and file mode 0600.
Known limits
It relies on CLI behaviour Aside does not document, so an Aside update can break it. It is tested with Aside 1.26.x on macOS and iPhone. Replies to a pending approval are sent with session resume and have not been verified against a live approval. Aside Pocket is not affiliated with Aside.
Repo and install instructions: github.com/khmuhtadin/aside-pocket