v1.0 · Built on Bun

Whitelabel agent runtime for teams that need control

One governed gateway.
Your brand on the binary.

DPAI is a terminal coding agent that talks only to the Dual Path Intelligence gateway — so model choice, budgets, access policy, and failover live server-side, not hardcoded across your CLI.

$ curl -fsSL https://install.dpai.sh | bash

See how it works →

TypeScript 5.9 Bun runtime OpenTUI React brand.json lock

dpai — session

$ █

GATEWAY

100+ models

BUDGET

$42.18 left

POLICY

locked route

brands/dpai.json

dpai — the resulting CLI

Brand

Built for

MSPs shipping branded agents Platform teams governing model spend Regulated orgs with locked data paths Senior living & care deployments

models behind one gateway endpoint

hour catalog cache TTL

built-in sub-agents

brand.json to ship your CLI

PRODUCT

Three things that make DPAI different.

Not another multi-vendor CLI. A single runtime you can brand, govern, and lock down.

01 — GATEWAY

One path for every model

All traffic hits Dual Path Intelligence. Budgets, allow-lists, and failover are configured once server-side — not copy-pasted into agent code.

100+ models spend caps failover

02 — WHITELABEL

brand.json in, your CLI out

Product name, binary, config dir, env prefix, colours, and locked gateway URL are data. Scaffold, validate, build, ship — no fork required.

own npm name gateway.locked theme.accent

03 — CONTROL

Posture you can explain

Capabilities stripped at build time, storage minimized, operator attribution on every action, and a compliance report your auditors can read.

build-time cuts retention attribution

CAPABILITIES

Everything the agent loop needed. Nothing it didn’t.

Bash-first tools, real sub-agent delegation, and a verify pipeline that boots your app.

One gateway, every vendor

Every request goes to Dual Path Intelligence — a single endpoint fronting 100+ models. Budgets, access policy, and failover stay server-side, not hardcoded per-vendor in the CLI.

POST /v1/chat/completions

Sub-agent delegation

Foreground task — explore, general, verify, computer, or custom agents — plus background delegate for read-only deep dives.

Sandboxed verify

/verify builds, boots, and smoke-tests your app in a Shuru microVM — with screenshots and video evidence.

Computer-use

Host desktop automation via agent-desktop: semantic accessibility snapshots, stable refs, and screenshots on macOS.

Scheduling & daemon

Natural-language recurring or one-shot headless runs. A daemon keeps cron-style schedules alive under /schedule.

Telegram remote

Pair a bot, approve once, keep chatting from your phone — including voice notes via gateway STT.

Hooks & lifecycle

Shell out on PreToolUse, PostToolUse, SessionStart, and more — enforce policy, run linters, log activity.

Skills & MCP

Drop Agent Skills into .agents/skills/ or wire MCP servers from the TUI. Extend without touching source.

Sandbox mode

Shell inside a Shuru microVM so the agent can’t touch host FS or network. Network off by default.

FOR MSPs

Your brand. Your gateway lock.
One JSON file.

Every product-identifying string, path, colour, and endpoint is data, not source.

acme.brand.json

{
  "id": "acme-msp",
  "productName": "Acme",
  "binName": "acme",
  "configDirName": ".acme",
  "envPrefix": "ACME",
  "gateway": {
    "baseUrl": "https://gateway.acme.com/v1",
    "locked": true
  },
  "models": { "allow": ["claude-sonnet-5"] },
  "theme": { "accent": "#ff5500" }
}

Scaffold

dpai brand init acme-msp --out acme.brand.json

Validate

dpai brand validate acme.brand.json

Build

bun run whitelabel acme.brand.json --out ../acme-cli --install-script

Ship it

Own npm name, binary, config dir, env prefix, README, colours — nothing for the client to configure. gateway.locked guarantees traffic transits your audited gateway.

REGULATED ENVIRONMENTS

Built for senior living, medical, and SOX-relevant deployments.

DPAI ships a compliance posture system: capabilities removed at build time, a gateway lock that pins where data goes, storage minimization with enforced retention, and operator attribution baked in.

$dpai compliance → posture of this build, and its limits

No software makes you HIPAA or SOX compliant on its own. A BAA is required and unverified here, and the CLI performs no PHI detection. Read the Compliance Guide before deploying into a regulated environment.

Data destination Gateway lock pins all model traffic to your endpoint Requires locked brand build

Capability surface Features stripped at compile time, not runtime flags Choose posture before ship

Storage Minimized local state + enforced retention windows Host logs still your job

Attribution Operator identity attached to tool use and sessions IdP integration optional

Sector packs Ready senior-living brand + posture defaults Not a compliance certificate

GET STARTED

Running in under a minute.

Install the CLI, set your gateway key, and you’re in the agent loop.