Proposed PR: first-class Codex lifecycle hook integration

[github-actions[bot]]

Originally posted as issue #2257 by @NoRain211
#2257

Hi, I built a branch adding first-class Codex lifecycle hook integration for claude-mem, but GitHub says this repo only allows collaborators to open PRs.

Branch:
https://github.com/NoRain211/claude-mem/tree/feat/codex-lifecycle-hooks

Compare:
main...NoRain211:claude-mem:feat/codex-lifecycle-hooks

Summary

This adds Codex as a first-class lifecycle source for claude-mem by adapting Codex hook payloads into the existing claude-mem pipeline.

This is not a second memory store. Codex native Markdown memories remain separate; claude-mem continues to use its existing session, observation, queue, summarization, transcript fallback, search, and roll-up internals.

What it adds

• claude-mem codex-hook entrypoints for:
  • SessionStart
  • UserPromptSubmit
  • PostToolUse
  • Stop
  • dispatch
• Codex hook payload normalization with platform_source = "codex".
• Per-tool Codex observation capture through the existing pending queue path.
• Stop-hook summary enqueueing without forcing Codex continuation.
• Transcript ingestion retained as fallback/backfill.
• Dedupe between hook-captured events and transcript-ingested events.
• Idempotent Codex hook install/status/remove commands:
  • npx claude-mem codex install-hooks --scope user
  • npx claude-mem codex install-hooks --scope repo
  • npx claude-mem codex hooks-status
  • npx claude-mem codex remove-hooks --scope user
  • npx claude-mem codex remove-hooks --scope repo
• Docs covering Codex hooks, Codex native memory coexistence, transcript fallback, and troubleshooting.

Design notes

• Managed hooks invoke npx -y claude-mem codex-hook ... so users do not need a global claude-mem binary on PATH.
• Legacy managed hook commands using claude-mem codex-hook ... are still recognized by the remover.
• Injected Codex context is labeled, bounded, and explicitly presented as memory context rather than authoritative source.
• Existing Claude Code integration, MCP search/read support, transcript ingestion, storage, summarization, and roll-up internals are preserved.

Commit stack

• c941ea50 feat(codex): add lifecycle hook pipeline
• 19dd4403 feat(codex): manage lifecycle hook installation
• fa8de28b docs(codex): document lifecycle hook integration
• fe980e8b fix(codex): invoke managed hooks through npx
• 1657fd08 test(codex): cover lifecycle hook paths
• a44d0a54 chore(build): update generated plugin artifacts

Verification

Passed:

npm run build
git diff origin/main --check

Focused test suite:

bun test tests/services/sqlite/PendingMessageStore.test.ts tests/services/sqlite/migration-runner.test.ts tests/zombie-prevention.test.ts tests/codex-hook-adapter.test.ts tests/codex-hooks-installer.test.ts tests/hook-lifecycle.test.ts tests/servers/mcp-tool-schemas.test.ts tests/mcp-integrations.test.ts tests/cursor-mcp-config.test.ts tests/codex-transcript-watcher-windows.test.ts
Result:

132 pass
0 fail
Known note:

npm run typecheck:root
currently stops on the repo TypeScript 6 config deprecation before checking this diff:

Option 'moduleResolution=node10' is deprecated and will stop functioning in TypeScript 7.0.
Maintainer import
If useful, you can fetch the branch directly:

git fetch https://github.com/NoRain211/claude-mem.git feat/codex-lifecycle-hooks
git checkout -b feat/codex-lifecycle-hooks FETCH_HEAD
I’m happy to adjust the branch if you’d prefer this split differently or want the generated plugin artifacts handled in a separate commit.