@bunshin-cc/bunshin 0.6.5 → 0.7.0
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.
- package/README.md +2 -0
- package/dist/bin.js +838 -391
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,6 +20,8 @@ For a linked Git worktree, setup puts Codex hooks in the primary checkout, where
|
|
|
20
20
|
|
|
21
21
|
For Claude Code, use `bunshin setup --harness claude-code`, then start a new session in the project and approve the `bunshin` MCP server it adds to `.mcp.json` (it gives the model the `bunshin_recall` and `bunshin_load` tools). `/learn` in the Claude Code plugin, or `bunshin learn "<what to remember>"`, captures knowledge on demand.
|
|
22
22
|
|
|
23
|
+
To connect a whole folder of projects (each its own repository), run setup there with `--hooks user`: the hooks go in your user settings and every session under that folder uses its workspace, while sessions elsewhere are untouched. `bunshin sources` shows and changes which of its folders take part (`exclude <folder>`, `only <folders…>`, `include <folder>`, `all`).
|
|
24
|
+
|
|
23
25
|
For Pi, use Node.js 22.19 or later and run `bunshin setup --harness pi`. It installs a project extension in `.pi/extensions/bunshin.js`. Start Pi in the project (or run `/reload` in an existing session), review its project resources, and check `/bunshin status`. The extension ships in this npm package; you do not need a second package or a repository checkout.
|
|
24
26
|
|
|
25
27
|
## Check it works
|