@cybedefend/vibedefend 1.4.7 → 1.5.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 +10 -0
- package/dist/hook-runner.js +319 -114
- package/dist/hooks/runtime/emit.js +40 -0
- package/dist/hooks/runtime/emit.js.map +1 -1
- package/dist/hooks/runtime/fetch-rules.js +6 -1
- package/dist/hooks/runtime/fetch-rules.js.map +1 -1
- package/dist/hooks/runtime/pre-compact.js +9 -0
- package/dist/hooks/runtime/pre-compact.js.map +1 -1
- package/dist/hooks/runtime/resolve.js +18 -9
- package/dist/hooks/runtime/resolve.js.map +1 -1
- package/dist/hooks/runtime/session-activation.js +222 -0
- package/dist/hooks/runtime/session-activation.js.map +1 -0
- package/dist/hooks/runtime/session-review.js +13 -3
- package/dist/hooks/runtime/session-review.js.map +1 -1
- package/dist/hooks/runtime/session-start.js +33 -3
- package/dist/hooks/runtime/session-start.js.map +1 -1
- package/dist/hooks/runtime/user-prompt-submit.js +6 -1
- package/dist/hooks/runtime/user-prompt-submit.js.map +1 -1
- package/dist/login.js +22 -3
- package/dist/login.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -141,6 +141,16 @@ That file is now **optional** for GitHub/GitLab-linked projects, but it
|
|
|
141
141
|
remains a supported override everywhere — when present, it always wins over
|
|
142
142
|
git-origin auto-resolution (as does the `CYBEDEFEND_PROJECT_ID` env var).
|
|
143
143
|
|
|
144
|
+
**Folders that are not CybeDefend projects.** The hooks are installed for
|
|
145
|
+
every folder your agent opens. When a session starts in a folder with no
|
|
146
|
+
`.cybedefend/config.json` and no project linked to its GitHub/GitLab `origin`
|
|
147
|
+
(notes, documents, unrelated repos), VibeDefend shows one line saying
|
|
148
|
+
CybeDefend is off for this session and why. All other hooks then stay off for
|
|
149
|
+
the rest of that session. Running `vibedefend link` in the folder turns
|
|
150
|
+
them back on, even mid-session. Claude Code and Codex show that line
|
|
151
|
+
themselves; Cursor's agent relays it in its first reply; Windsurf does not
|
|
152
|
+
display hook output, but its hooks stay off all the same.
|
|
153
|
+
|
|
144
154
|
`.cybedefend/config.json` also accepts an optional `apiBase`. Because the file
|
|
145
155
|
is committed — and therefore comes from whoever published the repository you
|
|
146
156
|
just cloned — that key is only honoured when it points at an origin **you**
|