Skip to content
Skip to content
PilotPods

Features

Everything PilotPods does, and what is still to come

One local system on your Mac to plan, run, watch and stop agent work. Each feature says Works today or Coming soon.

1
Pilot COS per instance
5
engine adapters
4
event kinds in the audit log
0
outbound calls from the core

The tour

Four groups, one flight deck

Pick a group. Each card shows its status.

Works today

Pilot COS

One chief of staff per instance. It takes your tasks, plans them and hands the work to pods. You talk to it only.

Works today

Pod COSs

Each pod has a Pod COS that manages a small group of workers, keeps its tickets moving and reports back to the Pilot COS.

Works today

Workers

Hire a worker into a pod with one command, optionally from a job description catalog. Each worker runs on an engine you choose.

Works today

Engines

Claude (including Amazon Bedrock), Codex and Antigravity run work today. Gemini and Grok are covered in the engines table below.

One Mac

no shared state between instances
default
  • own SQLite database
  • own port range
  • own budget cap
project-a
  • own SQLite database
  • own port range
  • own budget cap
project-b
  • own SQLite database
  • own port range
  • own budget cap

Engines

Pick the engine per worker

PilotPods shows which engine did the work. An engine that is not installed shows as not installed.

  • Claude

    Calls the signed in claude CLI in headless mode. Amazon Bedrock is supported.

    Works today

  • Codex

    Calls the Codex CLI with its own auth discovery.

    Works today

  • Antigravity

    Finds the running, signed in language server and reads the real reply.

    Works today

  • Gemini

    Adapter written, honest not installed message. Not yet run end to end.

    Coming soon

  • Grok

    Monitor only, by design. It never runs work.

    Works today
Engines
$ pilotpods engines list$ pilotpods engines detect

Budgets, approvals and STOP ALL

Money and risk stay in your hands

Caps are checked before a call is made. When one is hit, the task waits for you instead of spending on.

  • Caps at instance and pod level: daily, total and per run.
  • Warning at 80 percent, a harder warning at the cap.
  • Approvals for spend, hires, deliverables and actions.
  • STOP ALL ends every session and the daemon in one step.
Caps, audit, STOP ALL
$ pilotpods spend record 1.00 --instance project-a$ pilotpods audit list --kind approval --limit 10$ pilotpods stop --instance project-a --all

Real commands

From nothing to a working pod

Real commands, in order. Each one runs today.

  1. 1

    Create an instance

    Terminal
    $ pilotpods init --instance project-a --mission "Research pod"

    Instances keep data, daemons and caps separate.

  2. 2

    Add a pod and a worker

    Terminal
    $ pilotpods pod create research --instance project-a$ pilotpods hire analyst --pod research --instance project-a

    A Pod COS manages the pod.

  3. 3

    Start it and open the console

    Terminal
    $ pilotpods instances start$ pilotpods ui --open

    The console is served on 127.0.0.1 only.

  4. 4

    Back up, then stop

    Terminal
    $ pilotpods backup --instance project-a$ pilotpods stop --instance project-a --all

    Restore shows a dry run before it applies.

pilotpods
$

Everything runs on your Mac. Copy any command from the steps on the left and run it in a terminal.

At a glance

Works today or Coming soon

  • Pilot COSWorks today

    Takes tasks, hands work to pods

    pilotpods init
  • Pod COSs and workersWorks today

    Manage and run work in a pod

    pilotpods pod, hire
  • EnginesWorks today

    Claude, Codex, Antigravity run work

    pilotpods engines
  • Budgets and capsWorks today

    Check spend before it happens

    pilotpods spend
  • ApprovalsWorks today

    Hold work for your decision

    web console
  • Heartbeats and leasesWorks today

    Detect stale and stuck work

    pilotpods status
  • STOP ALLWorks today

    End every session and daemon

    pilotpods stop --all
  • InstancesWorks today

    Isolated copies on one Mac

    pilotpods instances
  • AuditWorks today

    Append only event log

    pilotpods audit list
  • BackupsWorks today

    Dated archive and restore

    pilotpods backup, restore
  • Gemini tested runComing soon

    Verified against a real install

    pilotpods engines

Questions

Quick answers

The core makes no outbound calls and has no tracking code. You can prove it with pilotpods verify-isolation. Engines you choose to run talk to their own providers.

Run your first pod in minutes

Install on a Mac, create an instance, and open the console. Everything stays on your machine.

Get started Read the docs
  • MIT licence
  • No telemetry
  • CLI and console
Quick start
$ ./install.sh$ ./pilotpods init --instance default$ ./pilotpods ui --open