@sentralbee/cli

The sentralbee command — scaffold a Sentralbee app, then build it against a local dev harness (mock platform) with manifest validation. Requires Bun.

sentralbee create <dir>                      scaffold a new app into <dir>
sentralbee dev [--port 8080] [--api <url>]   run your app against a local mock platform
sentralbee webhook <type> [json]             fire a signed test webhook at your running app
sentralbee token                             print a fresh session token + embed URL
sentralbee manifest                          validate ./sentralbee.app.json

Get started

bunx @sentralbee/cli create my-app
cd my-app
bun install
bun run dev

sentralbee create <dir>

Scaffolds a new app from the starter template into <dir> (refuses a non-empty directory). It sets the new package.json name from <dir> and pins the @sentralbee/* dependencies to this CLI's published version, then restores the .gitignore that npm strips from published packages. The scaffolded app is plain, readable example code you own. Run the other commands from inside your app's directory (where sentralbee.app.json lives).

sentralbee dev

Generates a throwaway Ed25519 dev keypair, starts your app with the matching public key, mock-installs a workspace (delivers a fake api key + webhook secret to /install/provision), and prints an embed URL with a live session token. Everything runs locally — no Sentralbee stack. Session details are written to .sentralbee/dev.json (gitignored) so webhook/token in another terminal reach the same app.

The harness mints the exact same token claims + webhook signatures the real platform does, so your verification paths are exercised for real.