@build-it-now/binctl

CLI for managing build-it-now platform resources (projects, branches, sessions, orchestration).

Installation

npm install -g @build-it-now/binctl

Login

binctl auth login

This starts a device-style flow and opens:

• https://build-it.now/binctl/login/<requestId>

Credentials are stored in:

• ~/.config/build-it-now/binctl/config.json

Global Flags

• --base-url <url>
• --json
• --config <path>
• --token <token>
• --api-key <key>
• -p, --project <slug|id>
• -b, --branch <branch>
• -s, --session <sessionId>

Common Commands

binctl auth status
binctl auth logout
binctl auth api-key create --name "ci" --save
binctl auth api-key list
binctl auth api-key revoke <key-id>

binctl get projects
binctl create project --name "Demo Project"
binctl describe project <project-ref>
binctl update project <project-ref> --name "Renamed Project" --mode prod
binctl delete project <project-ref>

binctl -p <project> get branches
binctl -p <project> describe branch <branch>
binctl -p <project> get sessions --branch <branch>
binctl -p <project> create session -b <branch> --name "Spec session"
binctl describe session <session-id>
binctl -s <session-id> update session --name "Renamed session"
binctl -s <session-id> delete session

binctl -s <session-id> conversation   # session summary + conversation + pending questions/envs
binctl -s <session-id> prompt --mode plan --model max "..."
binctl -s <session-id> answer-questions -a1 "Recipe Collection" -a2 "Both Manual & AI"
binctl -s <session-id> apply-required-envs -e backend/KEY=value -e frontend/KEY=value

binctl -p <project> -b <branch> orchestrate --model max

Project mode is derived from the persisted backwardsCompatible project setting:

• greenfield: agent can make breaking/reset-style changes
• prod: agent should keep changes backwards compatible