Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(plugins): record the Codex Windows hook limitation

AkitaOnRails02a1c726dd6b
diff --git a/crates/ai-memory-cli/templates/plugin/codex-README.md b/crates/ai-memory-cli/templates/plugin/codex-README.md
index ec5afba9..12748662 100644
--- a/crates/ai-memory-cli/templates/plugin/codex-README.md
+++ b/crates/ai-memory-cli/templates/plugin/codex-README.md
@@ -39,7 +39,8 @@ command says so in its changelog, and you trust the new command once.
shell script, which hands the event to the installed binary
(`ai-memory hook`). The binary applies your capture exclusions, spools the
event, and delivers it only to your ai-memory server. On Windows the hooks
- call `ai-memory hook` directly, so `ai-memory` must be on `PATH`.
+ call `ai-memory hook` directly, so `ai-memory` must be on `PATH`; without
+ it Codex reports a failed hook, and folderless sessions are captured.
- MCP: the ai-memory memory tools, through `ai-memory mcp-bridge
--no-session-id`.
- Skills: the ai-memory routing skills and a `status` skill.
diff --git a/docs/install.md b/docs/install.md
index d59f0818..0fe12b7b 100644
--- a/docs/install.md
+++ b/docs/install.md
@@ -265,7 +265,12 @@ changelog. `ai-memory doctor` and the `status` skill report hooks Codex
skips. The Codex plugin has no options: the server URL and credentials come
from your ai-memory config, and the MCP entry runs `ai-memory mcp-bridge
--no-session-id` from `PATH`. On Windows the hooks call `ai-memory hook`
-directly (`commandWindows`), so `ai-memory` must be on `PATH`.
+directly (`commandWindows`), so `ai-memory` must be on `PATH`. That direct
+call is a known limitation: it skips the launcher, so a Windows event is not
+marked as plugin-launched (folderless sessions are captured, as with a
+settings hook), and without the binary Codex reports a failed hook instead
+of the launcher's silent no-op. Changing it would also change the command
+Codex keys hook trust on.
Codex runs plugin hooks and `~/.codex/hooks.json` hooks side by side, and an
untrusted settings hook is skipped silently, so the plugin cannot safely drop
diff --git a/plugins/codex/README.md b/plugins/codex/README.md
index ec5afba9..12748662 100644
--- a/plugins/codex/README.md
+++ b/plugins/codex/README.md
@@ -39,7 +39,8 @@ command says so in its changelog, and you trust the new command once.
shell script, which hands the event to the installed binary
(`ai-memory hook`). The binary applies your capture exclusions, spools the
event, and delivers it only to your ai-memory server. On Windows the hooks
- call `ai-memory hook` directly, so `ai-memory` must be on `PATH`.
+ call `ai-memory hook` directly, so `ai-memory` must be on `PATH`; without
+ it Codex reports a failed hook, and folderless sessions are captured.
- MCP: the ai-memory memory tools, through `ai-memory mcp-bridge
--no-session-id`.
- Skills: the ai-memory routing skills and a `status` skill.