bitfab-cli 0.2.306 → 0.2.307

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +5 -5
  2. package/dist/index.js +31855 -31754
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # bitfab-cli
2
2
 
3
- Install and configure the Bitfab plugin in Claude Code, Codex, or Cursor, or the Bitfab skill pack in Amp (Alpha).
3
+ Install and configure the Bitfab plugin in Claude Code, Codex, Cursor, or Amp.
4
4
 
5
5
  ## Usage
6
6
 
@@ -9,7 +9,7 @@ npx bitfab-cli init # Detect editors, prompt if multiple
9
9
  npx bitfab-cli init --editor claude # Install for Claude Code
10
10
  npx bitfab-cli init --editor codex # Install for Codex
11
11
  npx bitfab-cli init --editor cursor # Install for Cursor
12
- npx bitfab-cli init --editor amp # Install the skill pack for Amp (Alpha)
12
+ npx bitfab-cli init --editor amp # Install for Amp
13
13
  npx bitfab-cli init --prompt "instrument the chat workflow"
14
14
  npx bitfab-cli init --v2 # Login + setup entirely in this terminal
15
15
  npx bitfab-cli setup --v2 instrument # Run one setup mode in this terminal
@@ -24,12 +24,12 @@ npx bitfab-cli help setup # Show help for setup
24
24
 
25
25
  ## Terminal-native setup
26
26
 
27
- `init --v2` and `setup --v2` run a terminal-native declarative flow derived from the editor setup workflow, without handing control to Claude Code, Codex, Cursor, or Studio. Terminal-specific states replace browser plan review, live template preview, and Studio cleanup. Claude Agent SDK handles repository analysis and edits; every workflow choice and every permission for a mutating tool is returned to the terminal for the user to decide.
27
+ `init --v2` and `setup --v2` run a terminal-native declarative flow derived from the editor setup workflow, without handing control to Claude Code, Codex, Cursor, Amp, or Studio. Terminal-specific states replace browser plan review, live template preview, and Studio cleanup. Claude Agent SDK handles repository analysis and edits; every workflow choice and every permission for a mutating tool is returned to the terminal for the user to decide.
28
28
 
29
29
  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.
30
30
 
31
31
  `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.
32
32
 
33
- ## Amp (Alpha)
33
+ ## Amp
34
34
 
35
- Amp has no Bitfab plugin yet, so `--editor amp` installs the [Bitfab skill pack](https://github.com/Project-White-Rabbit/bitfab-amp-plugin) into `~/.config/agents/skills/` and then runs the terminal-native flow above in this process. `init`, `plugin-install`, `setup`, `analyze-repo`, and `update plugin` work with it. `assistant` and `update sdk` do not. `--skip-permissions` and `--upload-logs` are rejected rather than silently ignored, because the terminal flow asks for every mutating tool itself and captures no session logs.
35
+ `--editor amp` clones the [Bitfab Amp plugin](https://github.com/Project-White-Rabbit/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.