You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hooks hydrate ~/.agentmemory/.env through one dependency-free loader; open the cluster PR #39
A setting the Operator places in ~/.agentmemory/.env — such as AGENTMEMORY_INJECT_CONTEXT, whose own comment says to put it there — reaches the hook scripts. A hooks-local loader, following the precedent of the existing shared hook helper for project resolution, reads the file (honouring the same home override the daemon honours), sets only keys absent from process.env, and imports nothing beyond node:fs, node:os, node:path. Every hook calls it before its first env read. The committed hook scripts are regenerated with npm run build, never hand-edited. Opens the PR.
Acceptance criteria
Loader test with a temporary home: file values land, an existing process.env value wins, a missing file is a no-op
Every hook script calls the loader before reading any AGENTMEMORY_* variable
plugin/scripts/*.mjs regenerated by npm run build and committed with mode 755 intact
The hook comment that names ~/.agentmemory/.env now describes behaviour that is true
Done in PR #47 (fix/hook-env, commit d4e993e): src/hooks/_env.ts hydrates ~/.agentmemory/.env before the first env read in all 14 hook entries; plugin/scripts regenerated; npm test 1894 passed.
Activity
possiblyneal commentedon Sep 22, 2026
Done in PR #47 (fix/hook-env, commit d4e993e): src/hooks/_env.ts hydrates ~/.agentmemory/.env before the first env read in all 14 hook entries; plugin/scripts regenerated; npm test 1894 passed.