FAQ
Questions, answered straight
Every answer covers what PilotPods does today. Anything not built yet is marked Coming soon.
At a glance
The three questions people ask first
- 23
- questions answered
- 6
- topic groups
- 4
- engines supported
- 0
- telemetry calls
Does my data leave the Mac?
Only what you send to the engines you choose. PilotPods itself has no telemetry, and verify-isolation proves it.
Which engines work?
Claude (including Amazon Bedrock), Codex, Antigravity and Gemini. Grok is monitor only.
How do I stop it all?
Press STOP ALL in the console or run pilotpods stop --all.
All questions
Find your answer
Six groups, 23 questions. Open any one.
Install
Getting from a clone to a running demo.
A Mac with python3 and git. The installer checks for both, creates a ~/.pilotpods data folder and installs a launchd agent template without loading it. It is safe to run again.
$ git clone <this-repo-url>$ cd pilotpods$ ./install.shEngines
The agent tools that do the actual work.
Data and privacy
Where everything lives and what leaves.
Costs
What it costs and how spend is capped.
Stopping
Pause, stop and kill switch.
Instances
Several isolated setups on one Mac.
Still stuck?
Every command explains itself
Each subcommand has its own help, and it is the source of truth when anything here drifts.
$ ./pilotpods --help$ ./pilotpods <command> --helpNot covered here? Send us an email and we will point you to the right command or doc.
Run your first pod in minutes
Install on a Mac, create an instance, and open the console. Everything stays on your machine.
- MIT licence
- No telemetry
- CLI and console
$ ./install.sh$ ./pilotpods init --instance default$ ./pilotpods ui --open