01
Identitybeam auth
Own the central Beam session used by every service command.
loginlogoutwhoamiBeam CLI / One command surface
[CLI] Command line
Build.
Publish.
Connect.
Beam brings identity, local action development, Registry packages, and network operations into one coherent CLI — with predictable output for people, scripts, and agents.
One Install, Two Binaries
beam and beam-agentd ship and update together.
Human or Machine Output
Readable text, structured JSON, stable exit codes.
Every Namespace, One Session
Authenticate once and reuse it across all commands.
beam / terminalv0.1.0-test
$ beam auth whoami
signed in · team@beam.network
$ beam registry inspect ./redact-action
valid package · 3 inputs · node runtime
$ beam action run ./redact-action
completed · mock runtime · 184 ms
$ beam tunnel status
ready · local API v4 · 2 endpoints
Auth · Actions · Registry · TunnelsReady
[01]
From zero to Beam in one command
The installer detects your platform, downloads matching beam and beam-agentd binaries, verifies SHA-256, and replaces both together.
Terminal
$
curl -fsSL https://cdn.b3m.dev/cli/install.sh | shInstalls the matching beam and beam-agentd bundle with SHA-256 verification.
[02]
Four namespaces. One Beam workflow.
Each namespace owns one clear responsibility, while global configuration, authentication, output, and errors remain consistent.
02
Local runtimebeam action
Build and execute action packages against local fixtures.
run03
Package lifecyclebeam registry
Take an action from validation to a versioned Registry release.
inspectpackpublishversionsresolve04
Connectivitybeam tunnel
Operate endpoints, transfers, bridges, identities, and durable work.
startexposeuploaddownloadoperations[03]
From source code to a live route
Use the same CLI as an action moves from local development to the Registry, then put the network underneath it.
01Authenticate once
$ beam auth login02Validate the package
$ beam registry inspect ./redact-action03Run it locally
$ beam action run ./redact-action --runtime mock04Create the archive
$ beam registry pack ./redact-action --out redact.tgz05Publish a version
$ beam registry publish ./redact-action --tag v1.0.006Bring up connectivity
$ beam tunnel start[04]
Simple at the prompt. Serious underneath.
Every namespace shares the same expectations for configuration, output, help, automation, and safety.
01
Central identity
Log in once, inspect the active identity, and let every Beam service consume the same local authentication.
02
Action development
Build and run Node action packages locally with explicit config, inputs, secrets, logs, and runtime mode.
03
Registry lifecycle
Validate, pack, publish, list, and resolve deterministic action packages from the same command surface.
04
Network operations
Create endpoints, move data, inspect durable work, and manage the companion daemon without a second CLI.
05
Human or machine
Choose readable output, structured JSON, or quiet mode with stable exit codes and structured failures.
06
Native completion
Generate completion for bash, zsh, or fish and keep the full Beam command map close at hand.
[05]
One interface. The right runtime for every job.
beam owns the user experience and delegates each operation without pulling service engines into the CLI binary.
Public surface
beam
Parsing, validation, identity, configuration, presentation, completions, and exit codes stay in one place.
AUTH
Beam Auth
Central session and identity
ACTION
Local Node runtime
Build and execute packages
REGISTRY
Registry HTTPS API
Resolve and publish versions
TUNNEL
beam-agentd API v4
Endpoints and durable transfers
+
+
[06]
One install.
The whole Beam workflow.
Authenticate, build locally, publish packages, and operate the network from the same command surface.