bitfab-cli

Install and configure the Bitfab plugin in Claude Code, Codex, Cursor, or Amp.

Usage

npx bitfab-cli init                       # Detect editors, prompt if multiple
npx bitfab-cli init --editor claude       # Install for Claude Code
npx bitfab-cli init --editor codex        # Install for Codex
npx bitfab-cli init --editor cursor       # Install for Cursor
npx bitfab-cli init --editor amp          # Install for Amp
npx bitfab-cli init --prompt "instrument the chat workflow"
npx bitfab-cli init --v2                    # Login + setup entirely in this terminal
npx bitfab-cli setup --v2 instrument        # Run one setup mode in this terminal
npx bitfab-cli setup --v2 --diagram         # Print the declarative Mermaid state diagram
npx bitfab-cli setup --prompt "modify the billing trace"
npx bitfab-cli session-logs enable        # Enable session log collection
npx bitfab-cli session-logs disable       # Disable session log collection
npx bitfab-cli session-logs status        # Show the saved session log setting
npx bitfab-cli analyze-repo --help        # Show help for analyze-repo
npx bitfab-cli help setup                 # Show help for setup

Terminal-native setup

init --v2 and setup --v2 run a declarative setup flow in the terminal through Claude Agent SDK. Setup reads the selected workflow and writes instrumentation and its replay registry directly. Login can open a browser. Template editing stays in the terminal. The agent asks for missing choices or required refactors and follows the terminal's tool permissions.

Set ANTHROPIC_API_KEY, or configure one of the Agent SDK's supported cloud providers, before using --v2. Bitfab authentication is separate: init --v2 opens the browser for login when needed, then returns to the terminal.

setup --v2 accepts wizard, explain, login, session-logs, instrument, modify, inspect, switch-org, view, replay, db-snapshot, templates, or analyze-repo. Add --diagram with any mode to inspect the exact state graph without authenticating or starting an agent.

Amp

--editor amp clones the Bitfab Amp plugin into ~/.config/amp/plugins/bitfab, confirms Amp loaded it with amp plugins list, then starts Amp and prints the skill to invoke (bitfab:setup, bitfab:assistant, bitfab:update sdk), since Amp takes no initial message on launch. analyze-repo --editor amp runs headless through amp -x. --skip-permissions has no Amp launch flag; the CLI points at the amp.dangerouslyAllowAll setting instead.