stackbone dev · 7 stages, one command

One command. Your whole stack, booting on your machine.

stackbone dev brings up a local control plane that speaks the exact contract production does — auth, the model gateway, triggers, metrics and dry-run billing — plus a real database, RAG, storage, queues and secrets. Hot-reloads on every save. The emulator runs on localhost:4242; the boot banner deeplinks you straight into Studio.

Read the CLI docs Open Studio

one command
hot reload
same contract as prod

~ <agent> · stackbone dev

$ stackbone dev

 Docker services ready  (postgres + minio ready)

 Platform migrations applied

 Agent migrations applied

 RAG schema ready

 Agent process ready

 Emulator listening  (:4242)

 Tunnel ready

╭─ stackbone studio ───────────────╮
▸ Open Studiohttp://localhost:4200/app/<org>/installations/<id>?stackbone-dev=…

  Tunnel     <slug>.tun.stackbone.ai
  Local      http://localhost:4242

  Agent      <agent name>
  Protocol   v10  ·  9 capabilities
╰──────────────────────────────────╯

stack up · emulator on :4242

01 · Boot sequence

7 stages · one command

The terminal above and this ledger read from one signal — every stage flips here the instant it lands up there.

docker Docker services ready · postgres + minio ready done

platform-migrations Platform migrations applied done

creator-migrations Agent migrations applied done

rag-migrations RAG schema ready done

agent Agent process ready done

emulator Emulator listening · :4242 done

tunnel Tunnel ready done

An absent RAG stage just doesn't fire — the previous step is already done.

02 · The data plane

One docker compose brings up your agent's whole data plane and the emulator injects its addresses — no cloud account, no keys to paste. Here is exactly what lands in the process:

env | grep STACKBONE_

STACKBONE_POSTGRES_URL    postgres://stackbone:stackbone@127.0.0.1:5433/stackbone_devSTACKBONE_S3_ENDPOINT     http://127.0.0.1:9004STACKBONE_S3_BUCKET       stackbone-dev

Credentials are injected by the emulator — your agent never pastes a key, exactly as a provisioned install does.

03 · Same contract, both sides

GET /api/contract → v10 · 9 capabilities

database.postgres_directPostgres 17 @ :5433dedicated Neon

rag.basicpgvector (same Postgres)Neon + pgvector

queues.pgmqpgmq (same Postgres)_queue_jobs (vanilla Postgres)

events.busin-process buscontrol-plane bus

secrets.read_writefile-backedinjected secrets

config.read_writefile-backedcontrol-plane config

approval.fire_and_forgetStudio HITL inboxHITL inbox

storage.s3MinIO @ :9004 (bucket stackbone-dev)R2 bucket

ai.openrouterOpenRouter gatewaymetered OpenRouter sub-key

left: stackbone dev → emulator. right: provisioned install → production. Same nine capability slugs on both sides.

one command boots all nine, here and in production.

04 · The CLI

21 commands · 2 live · 10 more scaffolded

The whole stack is driven from one CLI: 2 live, 10 scaffolded, and 9 real working commands shown without a live/scaffolded badge. What the scaffolded verbs will inspect runs inside stackbone dev and the SDK now.

dev live run the local control-plane emulator; open Studio from the boot banner

serve live run the runtime wrapper that exposes the platform HTTP verbs

db scaffolded scaffolded; what it inspects runs inside stackbone dev and the SDK today

rag scaffolded scaffolded; the retrieval index runs inside stackbone dev and the SDK today

hitl scaffolded scaffolded; human-in-the-loop runs inside stackbone dev and the SDK today

secrets scaffolded scaffolded; secrets are injected by stackbone dev today

storage scaffolded scaffolded; the object store runs inside stackbone dev and the SDK today

queues scaffolded scaffolded; queues run inside stackbone dev and the SDK today

logs scaffolded scaffolded; logs stream from the stackbone dev session today

runs scaffolded scaffolded; runs are inspected inside stackbone dev today

contract scaffolded scaffolded; the contract is read live via GET /api/contract on stackbone dev today

config scaffolded scaffolded; non-secret config is file-backed inside stackbone dev today

loginauthenticate the CLI via the device-code flow (CLI auth; app sign-in uses magic links)

initscaffold a project from a starter + Claude skill

linklink this directory to an organization + agent

listlist organizations the current user owns

currentprint the organization linked to this session

whoamishow the active user and organization

publishpackage the agent and publish it to the control plane

docsprint Stackbone documentation inline

metadataone-shot overview of the workspace state

develop locallystackbone devstackbone evalstackbone publish

Boot the whole stack with one command.

Develop locally. stackbone dev → stackbone eval → stackbone publish.

Read the CLI docs Open Studio