BCCLI interactive session
bccliRun it inside the project directory. The session keeps the conversation, the files it has touched, and the model it is using; you steer it with plain language and with slash commands.
Steering a session
Type / to see the commands this version has. The ones you will reach for first:
| Command | What it does |
|---|---|
/help | prints the slash-command surface of this release |
/model, /provider | switch the pair behind the session |
/diff | review what has changed so far |
/undo | step back from the last change |
/resume, /doctor | reopen an earlier session, or check the current one |
/diff is the one to build a habit around: an agent that edits files is only useful if you can see what it edited before you commit.
Permissions
BCCLI reads code, edits files, and runs commands with your permission. Shift+Tab cycles the permission mode. The permissive mode is what lets a session make many changes without stopping to ask — use it on a branch you can throw away, and review the diff when the session ends.
Leaving and coming back
End the session as you would any terminal program. Afterwards:
bccli -ccontinues the last session, and bccli -r lets you pick one from a list.
One task instead
If the work is a single request rather than a conversation, skip the interface:
bccli -p "task"That run starts from the task you give it, so keep the task self-contained.
Next
- Use a model — pinning a provider and model.
- Non-interactive runs —
-pin scripts and CI.