feat: sync Node Kimi hook integration

This commit is contained in:
ZacharyZhang-NY committed 2026-07-19 06:22:18 -04:00
1 parent aeedbebd02
commit cb9f33c255
9 files changed
+976 -4

No files matched your search

+3
View File
@@ -54,6 +54,8 @@ npx elydora install \
Codex performs a one-time trust review for user hooks. Run `/hooks` in Codex after installation and trust the Elydora `PreToolUse` and `PostToolUse` definitions.
Kimi installation writes the strict hook contract to each detected runtime: Kimi Code's `$KIMI_CODE_HOME/config.toml` (default `~/.kimi-code/config.toml`) and the migrating Python CLI's `~/.kimi/config.toml`. A fresh installation targets current Kimi Code, avoiding cross-runtime migration markers. Both runtimes load the hooks globally; run `/hooks` to inspect them.
Kiro CLI installation covers both runtime contracts. Kiro CLI v2 uses the generated custom agent through `kiro-cli --agent elydora-audit`. Kiro CLI v3 loads the global standalone hooks when started with `kiro-cli --v3`.
### Commands
@@ -71,6 +73,7 @@ Kiro CLI installation covers both runtime contracts. Kiro CLI v2 uses the genera
|-------|-----|
| Claude Code | `claudecode` |
| OpenAI Codex | `codex` |
| Kimi Code | `kimi` |
| Cursor | `cursor` |
| Gemini CLI | `gemini` |
| Kiro CLI | `kirocli` |