Phantom by AshlrAI

One place for your engineering agents.

Work alongside your agents, or give the fleet an outcome to work toward. Bring your signed-in coding tools, separately billed APIs and local models into one workbench for chats, projects, traces and review.

The workbench is distributed as @ashlr/phantom@3.29.15 with the phm CLI. Published release · npm package.The ashlr alias remains compatible; @ashlr/hub is the legacy package. Your installed tools, account setup and permissions determine what can run.

npm install -g @ashlr/phantom@3.29.15

  • SubscriptionsThrough signed-in CLIs
  • API creditsSeparately metered usage
  • Local modelsYour configured runtime
ImagePhantomCoordinate the work

Work with me

Converse, guide and inspect a session.

Work for me

Steer outcomes and follow fleet progress.

Plan Build Verify Review

MCP and CLI tools require configuration.

Your resources.
One extraordinary team.

Bring your subscriptions, API credits and local models into one engineering workbench. Give your agents the tools to turn an idea into a result.

Interactive demo · no agents are running

The illustrative team moves through the task and brings you the result.

ImageAnthropicClaude Code
ImageOpenAICodex
ImagexAIGrok
ImageDevinCloud & CLI
ImageOn your machineLocal models
ImageVercelDeployment tools
ImageSupabaseDatabase tools

Connect your supported CLI accounts. Each account keeps its own subscription window and usage reading.

Illustrated handoffs · one shared task

Delegated workflow · a retry fix

Find the cause before changing the code

Scout follows a reported retry failure to a small, reproducible case. The task and its context stay visible while the rest of the team gets ready.

Selected agent
Scout
Task
Investigate the retry failure
Context
Report and reproduction
What you would inspectA reproducible case and a short explanation of the suspected cause.

1 of 5 · Investigate · Ready

Provider logos identify resources. MCP servers and ecosystem tools need configuration.

Your engineering tools, in the same conversation.

Bring configured MCP servers and CLIs for source control, deployment, databases, design and observability. The workbench coordinates tool access; each server, account and permission determines the actions available.

  • Vercel
  • Cloudflare
  • Supabase
  • Stripe
  • Slack
  • Discord
  • PostHog
  • Sentry
  • GitHub
  • Docker
  • Notion
  • Linear
  • Figma

Logos identify products, not endorsement or automatic connection. Subscription CLI sessions, API credentials, MCP tools and local-model runtimes remain separate resources.

Explore the engineering toolkit

Phantom Secrets. A boundary for your credentials.

The local-first Secrets CLI and MCP server keep real API keys out of supported agent paths. See its installation, client setup and reviewed release evidence on the dedicated product page.

Explore Phantom Secrets →

Looking for an existing Secrets section?