Phantom documentation
Put your engineering agents to work.
Install Phantom, make your first useful turn, and build a fleet with clear permissions and measurable outcomes. Protect supported credential paths with the separate Phantom Secrets tools.
Workbench 3.29.15; Phantom Secrets v0.7.9. Installation, account readiness and autonomous activation are separate steps.
Explain this guide with AI
Choose your assistant. Only this public guide link and the prompt below are shared when you open it.
The link tries to fill the prompt. Sign-in or provider changes may require you to paste it yourself.
Phantom workbench
From the first local chat to a fleet you can inspect, steer and stop.
Read the overview- Install and open PhantomCLI, local console, first turn and desktop installation.
- Let an agent help you set upDiscovery, machine-readable contracts and operator steps.
- Commission a fleetResources, standing grants, outcomes and improvement evidence.
- Find the right commandInstalled help, JSON discovery and effect boundaries.
- Resolve a blockerInstallation, accounts, quotas and resident service admission.
Phantom Secrets
Protect API keys in supported coding-agent workflows. The Secrets executable is phantom; the workbench is phm.
Connect an agent
Evaluate trust
Adopt and contribute
Machine-readable context
Give agents the same guide you use.
Fetch the workbench manifest and raw Markdown to discover setup, commands and operator-only steps. The Secrets references describe the separate credential boundary. Public docs do not report your local readiness.