Skip to content

Diorama · the command line

The whole platform, from a terminal.

Everything the console does, the CLI does: publish a piece, install it into a space, read the listings, open the docs. One surface, two clothes — and it is built to a strict bar: an agent with no prior context can drive the platform with the CLI and the docs alone.

$ diorama test ./invoicing

validate, then a real install walk, in a throwaway local cell

$ diorama publish

sign and ship a version to the package registry

$ diorama install invoicing --space acme

put it in a space — the same install production runs

$ diorama list instances --space acme

the listings, straight from the record

$ diorama docs services/queue

the documentation, in the terminal it is needed in

Install

Two ways in, one command name.

  • bunx diorama

    Zero-install: the latest release, from anywhere — a fresh machine, a CI job, an agent’s sandbox.

  • diorama

    A single-file binary per platform, on your PATH. No runtime to bring.

Plainly marked: both paths arrive with the public registry. Today the CLI ships with the platform source — if you are working with us, it is already on your PATH.

Documentation