Start here

Installation and authentication

Install the native binary and approve browser, terminal, and automation access.

Before you start

Use macOS or Linux on a supported release architecture.
Have a browser session that can sign in to blobyard.com.

Install the CLI

installation command

curl -fsSL https://blobyard.dev/install.sh | sh

The installer selects the matching release archive and verifies its published SHA-256 checksum before placing the standalone Rust binary in your local bin directory.

verify installation

blobyard --version

Approve the device

browser-approved login

blobyard login --name "Development machine"
blobyard whoami

Login opens the Blob Yard activation page. The CLI stores a rotating refresh token in the operating-system credential manager where available. It never stores storage credentials.

Manage session boundaries

revoke current session

blobyard logout

Browser sessions use secure first-party cookies. CLI sessions use separate short-lived access tokens and rotating refresh tokens. Revoking a CLI session does not sign the browser out.

Reference and troubleshooting

Syntax and behavior

Reusable syntax

blobyard login [--name <device-name>] [--no-open]

Concrete example

named device login

blobyard login --name "Development machine"
blobyard whoami

Values used

--name: Optional label used to recognize this CLI session in Settings.
Development machine: Neutral device label. It is not a workspace or project name.
--no-open: Prints the activation URL instead of opening a local browser.

Expected result

Browser approval completes and whoami prints the authenticated identity and default workspace scope.

If it fails

If the code expires, rerun login to issue a new code.
If the browser cannot open locally, rerun with --no-open and use the printed URL on a trusted device.

Security and lifecycle

Only a rotating refresh token is persisted. Storage credentials and browser cookies never enter the CLI token store.