ompctl

OMP coding agents, from your phone

Your agents keep running. You stop having to sit there.

Your phone drives the sessions already running on your machine. Read what changed, send the next instruction, and walk away from the desk.

Pair your device Open the web app

Already running OMP? Keep your sessions. Add ompd.

On your phonePaired
Phone session list with live terminals, project filtering, activity and spend.
One list. The work already in flight.

The product, in use

Pick up where you left off.

At a desk, keep the list beside the conversation. On a phone, open one session at a time.

Desktop console with a session list on the left and the selected session with its subagents on the right.
The desktop view. Same application, room for both panes. Open any image at full size.
01Find your session

Live terminals, daemon-owned agents and dormant transcripts in one list. Filter by project; check activity, model and spend before opening one.

Web session list with live and dormant work, project filtering and per-session activity.
Web. The same fleet as the phone above.
02Give the next instruction

Read replies and tool calls, then send a message into the session. A live terminal keeps rendering on its machine.

Phone transcript showing the agent's reasoning, tool results and message composer.
Phone. The conversation and the next instruction.
Web transcript with the selected session, its messages and the composer.
Web. More room for the same conversation.
03Follow the subagents

Open a shared session's subagent band to see the workers underneath it and read their transcripts.

Expanded subagent band on a phone, listing workers and their current states above the transcript.
Phone. Expand the band above the conversation.
Web session with its subagent band expanded, showing the workers attached to that session.
Web. Keep the parent session in view.
04Let a routine start the work

A schedule or webhook starts ordered prompts in fresh agents. Each run keeps the sessions it created, ready to open afterward.

Routines on a phone with a read-only pairing and no routines configured.
Phone. This pairing can read routines.
Routines in the web console, with access limited by the current device's scopes.
Web. Running or changing routines needs manage.
05Switch the machine you drive

Choose a saved connection. Each pairing keeps its own credential and the permissions you gave that device.

Phone connections screen listing saved pairings and identifying the active connection.
Phone. Pick the connection to open.
Saved connections in the web console, each with its own pairing credential.
Web. The same switcher on a wider screen.

Where the work happens

Your machine does the work.

01 / Machine

ompd

The daemon owns the sessions, working directories and credentials. It runs alongside OMP.

02 / Relay

The hub

The daemon dials out to hub.ompctl.ai. Reach it away from your network without forwarding a port.

03 / Device

Your console

A phone or browser, paired with a scoped token. You decide what that device can do.

Get started

Four commands and a code.

Run these on the machine that runs OMP. Keep the machine awake and the daemon running while you're away.

  1. Install the daemon

    ompd self-install

  2. Start it

    ompd start

  3. Invite your device

    ompd invite "my phone" --scopes read,prompt

    Scan the QR code or paste the token into the app. This invite grants reading and prompting; add approve to answer approvals.

  4. Check the connection

    ompd doctor

Pair once, then open your sessions

Phone pairing screen with the hub address, token field and QR code scanning option.
Phone. Scan or paste.
Web pairing screen with the hub already filled in and a field for the device token.
Web. Paste the same kind of token.

The app opens the sessions the daemon already holds. Open the web app or get the native app source.

Granted per device

A device gets exactly what you gave it.

Pairing grants a scoped token. A phone paired for reading and prompting cannot answer approvals or manage your agents.

Four scopes, chosen when you pair.
ScopeWhat it permits
readSee sessions, transcripts, agents and cost.
promptSend messages into a session.
approveAnswer approvals and plan reviews.
manageProvision hosts, change settings and create agents.

ompd devices lists pairings. ompd revoke ends one. ompd rotate re-mints it. ompd audit shows what devices did.

Before you pair

Where it stops today.

Open the app to check in.
Push notifications do not ship yet. Nothing alerts your phone when a decision is waiting.
One operator at a time.
Steering a live terminal works. True co-drive waits on upstream OMP collaboration.
See the model, set it on the machine.
The model is visible in the console. Changing it from your phone does not ship.
Read artifacts as text.
Image, video, diff and HTML viewers have not landed.
Pair your device Read the source