[bldr]docs
CLI toolsbldr

bldr

Builder node gRPC client

Builder node gRPC client

Generated from bldr 0.1.0.

bldr [BLDR FLAGS] <COMMAND>

Commands

Command
bldr blobBlob operations
bldr buildCreate a build and watch it live until it finishes
bldr buildsManage builds — list, inspect, attach, detach, delete, or create a detachable build
bldr cacheFunction-invocation cache operations
bldr clusterDistributed-pinning cluster state (members, pins, refs, GC epoch)
bldr completionsShell completions: print a script, or wire them into your shells
bldr deployRun a deployment: invoke a Deployment block (function + options) by CID and stream its progress tree. See bldr deployments to list runs
bldr deploymentsManage deployment runs — list (optionally live), inspect, abort, delete
bldr fetchRecursively download a DAG from the peer network into the node's local store
bldr fsFilesystem tree operations: import, materialise, and FUSE mount
bldr getFetch a single block from the node (local-first, optional network fallback)
bldr infoShow node identity, addresses, peer count, and bootstrap status
bldr inspectInspect a CID: detect its kind (blob / fs-node / container-image / dag-cbor) and print a typed summary. Child CIDs (directory entries, image layers) are shown so you can drill in with another inspect
bldr invokeInvoke a registered function over the function protocol
bldr loginLog in to bldr-service, the hosted bldr console
bldr logoutLog out of bldr-service: revoke this CLI's login and forget it
bldr logsRead content-addressed log streams by full id &#123;peer&#125;/&#123;tenant&#125;/&#123;uuid&#125;
bldr mapThe persistent key → CID map: TTL'd, pinnable, GC-rooted mappings (sealed log streams live here as log/&#123;stream-id&#125;)
bldr netNetwork and peer management
bldr peersList connected peers (or watch live events with --watch / -w)
bldr podPods: docker/podman-style container sandboxes for testing images (CID in, stdout/stderr + a diff CID out). Not the way to build things
bldr putStore data in the node's local block store
bldr refManage named CID refs on the remote node
bldr runRun an application built by bldr: bldr run &lt;TARGET>:&lt;RUNNABLE> starts a runnable (backed by a build) and streams its progress + pod logs
bldr runsManage runs — list (optionally live), attach, stop
bldr secretManage secrets stored in the node's secret provider
bldr storageThe block store: what holds its bytes, and garbage collection
bldr testBuild a workspace (or a member) and report its test results: every ctx.addTest(name, …) target is built, then the daemon's aggregated per-case verdict is printed. Exits non-zero if any case failed
bldr wait-forBlock until a resource reaches a state, then say what happened and how long it took
bldr whoamiShow who this CLI is logged in to bldr-service as
bldr workspaceManage workspaces — directories containing bldr-workspace.yml

Global flags

Accepted by every command above.

-s, --server <SERVER>

gRPC server address.

Unix: unix:///run/user/&lt;uid>/bldr.sock (default, from $XDG_RUNTIME_DIR) TCP: http://host:port

Defaults to unix://$XDG_RUNTIME_DIR/bldr.sock.

--output-format <FORMAT>

How to render build event streams.

pretty (default): live tree view (Ctrl-C abort, Ctrl-X detach). json: print each raw BuildEvent as a JSON object on its own line. ron: print each raw BuildEvent in Rust Debug format (one per line).

Defaults to pretty.

Value
prettyLive tree view with spinners and progress bars (default)
jsonOne JSON object per line, printed as each event arrives
ronOne Rust Debug ({:#?}) block per line, printed as each event arrives

--tenant-id <ID>

Scope this request to a tenant.

Sends x-bldr-tenant-id: &lt;id> so the daemon addresses content in tenant &lt;id>'s namespace. Omitted ⇒ the default tenant (0).

On this page