BCCLI diagnostics

When a BCCLI run fails, the useful question is which layer broke: the install, the provider, the model, or the session. Three commands answer it in order.

1. Is the install current?

bccli --version

It must report 0.4.0 or newer. An older version is worth updating before debugging anything else — the command surface changes between releases, so a fix you read about may simply not exist in the copy you are running.

2. Can BCCLI see the model?

bccli models

The list comes from the providers this machine is signed in to. If the model you are asking for is missing, the problem is upstream of the request: sign in again with bccli login [provider], or check bccli provider list.

3. What does the session say?

Inside an interactive session:

/doctor

/doctor reports on the running session — its provider, model, and the checks that apply to it. /help prints the slash-command surface of the version you actually have, which is the fastest way to confirm a command exists in this release.

Permission prompts

If BCCLI keeps asking before it edits a file or runs a command, that is the permission mode, not an error. Shift+Tab cycles it. Change it deliberately: the permissive mode is what lets a session make many edits without stopping, so use it on a branch you can discard.

Next

• BCCLI models — providers and provider/model pairs.
• Troubleshooting — when the runtime or the machine is the problem, not the CLI.