Headless automation

A headless machine — a CI runner, a build server, a container — has no one to answer a prompt. BCCLI fits that case through -p, which runs one task and returns.

Install

npm install -g @botconnector/bccli

Node.js 22 or newer must be present on that machine. In a CI image, install Node before this step; the package will not supply its own runtime.

Authenticate

The machine needs credentials before it can do anything:

bccli login

For CI, run this once interactively while building the image, or provide the credentials the way your platform already injects secrets. An unattended job cannot complete an interactive login.

Run a task

bccli -p "task"

Design for one shot

A headless run starts from the task you give it and inherits nothing from a previous session. That means the task text carries the context: name the files, state the goal, and do not assume a conversation that is not there. If the work is a sequence, run it as several -p invocations with a check between them rather than one long prompt.

Review before you trust

With no one approving edits mid-run, treat the working tree as disposable and review the diff afterwards. Run it on a branch.

Next

• OS service — supervision, which stays your responsibility.
• Non-interactive runs — the flags in more detail.