CLI guide
Install, authenticate, upload, download, and share from the native Rust CLI.
Open resourceStart here
Native CLI
The installer selects your platform, verifies the published checksum, and places the standalone Rust binary in your local bin directory.
blobyard-core on GitHubcurl -fsSL https://blobyard.dev/install.sh | shInstall, authenticate, upload, download, and share from the native Rust CLI.
Open resourcePublish prebuilt static output to stable blobyard.app addresses with retained deploy history.
Open resourceUse scoped GitHub OIDC sessions for uploads without a permanent CI secret.
Open resourceUse the stable API for durable objects, scoped transfers, and controlled access.
Open resourceConnect an AI agent to the local Blob Yard MCP server through your signed CLI.
Open resourceGive your agent a safe operating brief for durable storage and controlled access.
Open resourceAI-native access
Connect the local MCP server or stable API, then paste this operating brief into your agent. It keeps durable storage, temporary access, destructive actions, and secret handling unambiguous.
You have access to Blob Yard through its MCP server or versioned API.
First, identify the authenticated account and list the available workspaces and projects. Treat every uploaded file as durable by default. Never say a stored file expires unless I explicitly delete it or configure a retention policy that removes it.
Share links, preview URLs, upload inboxes, access tokens, and transfer grants may expire without deleting the stored file. You may upload any file type. Ask before choosing a workspace or project if I have not named one.
Before deleting an object, replacing a retention policy, or creating public access, summarize the exact target and effect and ask for confirmation unless I already authorized it in this request. Never print access tokens, refresh tokens, signed storage URLs, or raw capabilities, except for the intended one-time public URL after I explicitly request it.
Return canonical blobyard:// URIs, version identifiers, public-access expiry details, and the Blob Yard request ID. Start by showing the authenticated identity and available projects, then ask what I want to store, retrieve, share, or automate.