Skip to content

Releases: profullstack/bufferoverride

bo 0.1.0 — the BufferOverride CLI

Choose a tag to compare

@ralyodio ralyodio released this 19 Aug 07:09
ff3f455

The first published release of bo, the BufferOverride CLI.

npm install -g @profullstack/bufferoverride

Node 20 or newer, and nothing else — the package has no dependencies.

What it does

Capture a failure. bo run -- bun test wraps a command rather than replacing it: it keeps what the command printed, records the environment, redacts the secrets, and searches for the existing answer before offering to publish anything. The wrapped command's exit code passes straight through, so it can go in front of something already in CI without changing what CI sees.

Read without an account. bo search and bo get need no credential.

Sign in from a terminal. A terminal cannot hold a browser session, so bo login asks for a device code, a human approves it in a browser they are already signed in to, and the CLI polls for a token sealed to an X25519 key it generated for that one exchange. The stored credential is written 0600.

Move an answer somewhere else. bo get <code> renders markdown for the terminal; --markdown writes the whole thread to stdout as one document and --copy puts it on the system clipboard.

Configure a coding agent. bo mcp config prints the MCP server configuration. Five read tools need no authentication; write tools are gated on the scopes the key actually carries.

Safety

Redaction is best effort and cannot be complete — no pattern list catches a custom-format secret. It runs on the way in rather than behind a flag you have to remember, because secrets in a stack trace are the normal case rather than the exception. Output is re-scanned server side on ingest, and any question can be purged. Treat --dry-run as the default habit.

Docs: https://bufferoverride.com/docs/cli