braintrust cli not working
Fixes a non-working Braintrust CLI: auth, install, and config checks. Use when braintrust commands fail, hang, or error on login/eval runs. Not for the Braintrust web UI or SDK-side bugs.
TL;DR
A dead Braintrust CLI is almost always one of three things: the API key is missing or expired, the CLI is stale, or the command ran outside a Braintrust-initialized project. Check braintrust --version, re-run braintrust login with a fresh key, and confirm you are in the right project directory. Nine times out of ten one of those fixes it.
The query
braintrust cli not workingUse this when
braintrustcommands error, hang, or print auth failures.braintrust logindoes not stick between sessions.- Eval runs from the CLI never reach the Braintrust dashboard.
Not for
- Problems inside the Braintrust web UI itself (login there is a separate auth).
- SDK-side failures in Python/TS eval code; this is about the CLI tool.
- Self-hosted Braintrust proxy networking; check the proxy first.
Steps
- Confirm the CLI is installed and current: run
braintrust --versionand compare against the latest release. Expected output: a version number at or near the latest; if the command is not found, reinstall per the official install docs. - Re-authenticate: run
braintrust loginand paste a fresh API key from your Braintrust org settings. Expected output: a success message and the org name; if it fails, the key is wrong or revoked, so generate a new one. - Check the key is visible to the shell: run
env | grep -i braintrustto confirmBRAINTRUST_API_KEYis set. Expected output: the variable listed; if absent, export it in your shell profile so it survives new sessions. - Run from the right directory: many commands need the project config. Run
pwdand confirm you are inside the project that was initialized withbraintrust init. Expected output: the project directory; move there and retry. - Re-run the failing command with verbose output (
--verboseor the debug flag the CLI offers) and read the first error line, not the last. Expected output: the root cause surfaces, usually auth, network, or a bad project slug.
Provenance
(appended by publisher)
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_cyR8raZmHOPZTihNEzwd7Q
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.