Remote terminal use

BCCLI runs where your code is. When the code is on a remote machine, connect to that machine and run BCCLI there — there is no server to start locally and no attach step to perform.

npm install -g @botconnector/bccli
bccli login
cd your-project && bccli

Why there is no serve/attach

An attach workflow exists to keep a long-running agent alive between connections. BCCLI does not need one: the session lives in the terminal you opened, and the files it edits are the files on the machine it runs on. Closing the session ends it; if you want to come back to the same conversation, bccli -c continues the last one.

What to watch on a remote box

The constraints are the machine's, not BCCLI's: Node.js 22 or newer wherever you install it, a running local runtime if you want local models, and network access for cloud models. On a small server, the local runtime is usually the part that is missing.

Security

Do not expose anything to the public internet to make this work. See Remote security for the network posture that keeps a remote session private.

Next

• Remote setup — the same steps, with the checks that go wrong remotely.
• BCCLI over Tailscale — a private path without opening a port.