Remote BCCLI setup

You are already on the remote machine — connected with SSH or Termius — and the project you want to change is on that machine's disk.

1. Check the runtime

node --version

Node.js 22 or newer, on the remote machine. Installing Node on your laptop does not help here.

2. Install

npm install -g @botconnector/bccli

If npm is not found, Node is not installed for this user on this machine; a version manager avoids the permission problems that come with installing it system-wide.

bccli login

Credentials are stored per provider on this machine. A remote box starts with none, so this step is not optional even when your laptop is already signed in.

4. Start inside the project

cd your-project && bccli

The session is scoped to that directory. Verify with bccli models that the provider you just signed in to actually reaches the models you expect.

Automation

For a scheduled job or a CI step on the remote machine, skip the interface:

bccli -p "task"

Common failures

A command not found after install is a PATH problem for the remote user. An empty bccli models is a sign-in problem, not an install one.

Remote security — keeping the path private.
Diagnostics — when one of the checks above fails.