@bunshin-cc/bunshin 0.6.2 → 0.6.3
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 +6 -0
- package/dist/bin.js +430 -299
- package/dist/claude-code-ui/hooks/bunshin-ui.mjs +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -33,6 +33,12 @@ bunshin recall "changing a state transition other teams depend on" --hypothetica
|
|
|
33
33
|
|
|
34
34
|
`bunshin index` shows how the repo’s docs split into sections and which paths push each one. Learned knowledge arrives after real sessions: when a session was worth it, a reflection runs at its end (for Claude Code, as a fork of the session, so it reuses the prompt cache). Suggestions that were not applied automatically wait in `bunshin review`.
|
|
35
35
|
|
|
36
|
+
## Staying current
|
|
37
|
+
|
|
38
|
+
The hooks run whichever `bunshin` is installed; nothing updates it for you. At most once a day, session start checks npm for a newer version and, when there is one, tells you once that day (`npm i -g @bunshin-cc/bunshin@latest`). Set `BUNSHIN_NO_UPDATE_CHECK=1` to turn the check off.
|
|
39
|
+
|
|
40
|
+
Sessions uploaded by a CLI before 0.6.2 carry a clipped trace (at most 60,000 characters). After updating, `bunshin sync --retrace` re-sends those from the last 30 days (`--days N`) with their whole trace, as long as the session's transcript file is still on the machine.
|
|
41
|
+
|
|
36
42
|
`bunshin demo` runs an offline example using temporary synthetic data. It does not verify your workspace connection or automatic learning.
|
|
37
43
|
|
|
38
44
|
## Scope and removal
|