eagle-mem 4.6.2 → 4.7.1

package/scripts/update.sh

@@ -13,8 +13,11 @@ LIB_DIR="$SCRIPTS_DIR/../lib"
 . "$LIB_DIR/common.sh"
 . "$LIB_DIR/db.sh"
 . "$LIB_DIR/hooks.sh"
+. "$LIB_DIR/codex-hooks.sh"
 
 SETTINGS="$EAGLE_SETTINGS"
+claude_found=false
+codex_found=false
 
 eagle_header "Update"
 
@@ -30,6 +33,11 @@ if [ ! -f "$EAGLE_MEM_DIR/memory.db" ]; then
     eagle_warn "Database not found — will be created"
 fi
 
+[ -d "$HOME/.claude" ] && claude_found=true
+if [ -d "$EAGLE_CODEX_DIR" ] || command -v codex &>/dev/null; then
+    codex_found=true
+fi
+
 # ─── Update files ──────────────────────────────────────────
 
 mkdir -p "$EAGLE_MEM_DIR"/{hooks,lib,db,scripts}
@@ -63,7 +71,7 @@ fi
 
 # ─── Re-register hooks (idempotent) ───────────────────────
 
-if [ -f "$SETTINGS" ] && command -v jq &>/dev/null; then
+if [ "$claude_found" = true ] && [ -f "$SETTINGS" ] && command -v jq &>/dev/null; then
     # Update PostToolUse matcher if it has the old value (pre-v1.3.0)
     if jq -e '.hooks.PostToolUse[]? | select(.matcher == "Read|Write|Edit|Bash")' "$SETTINGS" &>/dev/null; then
         _tmp=$(mktemp)
@@ -85,9 +93,16 @@ if [ -f "$SETTINGS" ] && command -v jq &>/dev/null; then
     eagle_ok "Hooks registered"
 fi
 
+if [ "$codex_found" = true ] && command -v jq &>/dev/null; then
+    eagle_register_codex_hooks
+    eagle_ok "Codex hooks registered"
+elif [ "$codex_found" = false ]; then
+    eagle_info "Codex hooks skipped ${DIM}(Codex not detected)${RESET}"
+fi
+
 # ─── Update skill symlinks ────────────────────────────────
 
-if [ -d "$PACKAGE_DIR/skills" ]; then
+if [ "$claude_found" = true ] && [ -d "$PACKAGE_DIR/skills" ]; then
     mkdir -p "$EAGLE_SKILLS_DIR"
     # Remove stale symlinks for deleted skills (find catches broken symlinks; glob doesn't)
     find "$EAGLE_SKILLS_DIR" -maxdepth 1 -name "eagle-mem-*" -type l 2>/dev/null | while read -r existing; do
@@ -104,7 +119,26 @@ if [ -d "$PACKAGE_DIR/skills" ]; then
         [ -L "$dst" ] && rm "$dst"
         ln -sf "$skill_dir" "$dst"
     done
-    eagle_ok "Skills updated"
+    eagle_ok "Claude skills updated"
+fi
+
+if [ "$codex_found" = true ] && [ -d "$PACKAGE_DIR/skills" ]; then
+    mkdir -p "$EAGLE_CODEX_SKILLS_DIR"
+    find "$EAGLE_CODEX_SKILLS_DIR" -maxdepth 1 -name "eagle-mem-*" -type l 2>/dev/null | while read -r existing; do
+        skill_name=$(basename "$existing")
+        if [ ! -d "$PACKAGE_DIR/skills/$skill_name" ]; then
+            rm "$existing"
+            eagle_ok "Removed stale Codex skill: $skill_name"
+        fi
+    done
+    for skill_dir in "$PACKAGE_DIR"/skills/*/; do
+        [ ! -d "$skill_dir" ] && continue
+        skill_name=$(basename "$skill_dir")
+        dst="$EAGLE_CODEX_SKILLS_DIR/$skill_name"
+        [ -L "$dst" ] && rm "$dst"
+        ln -sf "$skill_dir" "$dst"
+    done
+    eagle_ok "Codex skills updated"
 fi
 
 # ─── Backfill project names ───────────────────────────────
@@ -118,10 +152,20 @@ fi
 
 # ─── Patch CLAUDE.md with Eagle Mem instructions ─────────
 
-if eagle_patch_claude_md; then
-    eagle_ok "CLAUDE.md updated ${DIM}(eagle-summary instructions added)${RESET}"
-else
-    eagle_ok "CLAUDE.md up to date"
+if [ "$claude_found" = true ]; then
+    if eagle_patch_claude_md; then
+        eagle_ok "CLAUDE.md updated ${DIM}(eagle-summary instructions added)${RESET}"
+    else
+        eagle_ok "CLAUDE.md up to date"
+    fi
+fi
+
+if [ "$codex_found" = true ]; then
+    if eagle_patch_codex_agents_md; then
+        eagle_ok "AGENTS.md updated ${DIM}(Codex eagle-summary instructions added)${RESET}"
+    else
+        eagle_ok "AGENTS.md up to date"
+    fi
 fi
 
 # ─── Save installed version ───────────────────────────────

package/skills/eagle-mem-memories/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: eagle-mem-memories
 description: >
-  View and sync Claude Code auto-memories, plans, and tasks mirrored in Eagle Mem. Use when:
-  'eagle memories', 'show memories', 'sync memories', 'what does claude remember',
+  View and sync Claude Code and Codex memories, plans, and tasks mirrored in Eagle Mem. Use when:
+  'eagle memories', 'show memories', 'sync memories', 'what does the agent remember',
   'show plans', 'show tasks', 'mirror memories', 'onboard project',
   'what did past sessions learn'. Uses the eagle-mem CLI.
 ---
@@ -11,9 +11,9 @@ description: >
 
 ## Purpose
 
-**For the user:** Claude Code remembers across sessions. Decisions, preferences, project context, and architectural plans survive session boundaries. The user never has to re-explain "we chose Postgres because..." or "don't use semicolons in this project."
+**For the user:** Claude Code and Codex remember across sessions. Decisions, preferences, project context, and architectural plans survive session boundaries. The user never has to re-explain "we chose Postgres because..." or "don't use semicolons in this project."
 
-**For you (Claude Code):** Access to what past Claude sessions learned about this project. Memories tell you *why* decisions were made. Plans tell you *what's coming*. Tasks tell you *what's in flight*. Together they're the knowledge bridge that makes you effective from message one.
+**For you:** Access to what past Claude Code and Codex sessions learned about this project. Memories tell you *why* decisions were made. Plans tell you *what's coming*. Tasks tell you *what's in flight*. Together they're the knowledge bridge that makes you effective from message one.
 
 ## Judgment
 
@@ -21,7 +21,7 @@ description: >
 - The user references a past decision ("remember when we decided to...", "what's our convention for...")
 - You're about to make an architectural or style choice -- memories may record the user's preference
 - You need project context that isn't in CLAUDE.md or README (relationships between services, deployment quirks, naming conventions)
-- The user asks "what does Claude remember about X?"
+- The user asks "what does Claude/Codex/Eagle Mem remember about X?"
 
 **Check plans when:**
 - The user asks about upcoming work or roadmap
@@ -43,21 +43,21 @@ description: >
 
 ### 1. Know the three data types
 
-**Memories** -- Claude Code's auto-memory files (`~/.claude/projects/*/memory/*.md`). These contain user preferences, project conventions, and feedback. Each has a name, type (user/feedback/project/reference), and description.
+**Memories** -- Claude Code auto-memory files (`~/.claude/projects/*/memory/*.md`) plus top-level Codex memory files (`~/.codex/memories/MEMORY.md`, `memory_summary.md`). These contain user preferences, project conventions, and feedback. Each mirrored row is source-attributed.
 ```bash
 eagle-mem memories list                    # all memories
 eagle-mem memories search "typescript"     # FTS5 search
 eagle-mem memories show <file_path>        # full content
 ```
 
-**Plans** -- Claude Code's plan files (`~/.claude/plans/*.md`). Multi-step strategies for complex work. Each has a title, optional project tag, and markdown content.
+**Plans** -- Claude Code plan files (`~/.claude/plans/*.md`) and future agent plan files as support is added. Multi-step strategies for complex work. Each has a title, optional project tag, and markdown content.
 ```bash
 eagle-mem memories plans                   # all plans
 eagle-mem memories plans search "migration"
 eagle-mem memories plans show <file_path>
 ```
 
-**Tasks** -- Claude Code's task JSON (`~/.claude/tasks/<session>/*.json`). Individual units of work with status tracking (pending/in_progress/completed).
+**Tasks** -- Claude Code task JSON (`~/.claude/tasks/<session>/*.json`) and Eagle Mem task records created directly by agents such as Codex. Individual units of work with status tracking (pending/in_progress/completed).
 ```bash
 eagle-mem memories tasks                   # all tasks
 eagle-mem memories tasks search "refactor"
@@ -68,13 +68,13 @@ eagle-mem memories tasks show <file_path>
 
 Two paths feed the mirror:
 
-**Real-time (PostToolUse hook).** Every time Claude Code writes or edits a memory file, plan file, or creates/updates a task, the hook intercepts it and mirrors it into Eagle Mem's SQLite with FTS5 indexing. This happens automatically -- no user action needed.
+**Real-time hooks.** Claude Code memory/plan/task files are mirrored when written. Codex sessions are captured through SessionStart/UserPromptSubmit/PostToolUse/Stop hooks, and important durable facts should be placed in `<eagle-summary>` so they become shared recall.
 
-**Backfill (sync command).** For memories, plans, and tasks that existed before Eagle Mem was installed, or that were written outside a Claude Code session:
+**Backfill (sync command).** For memories, plans, and tasks that existed before Eagle Mem was installed, or that were written outside a hooked session:
 ```bash
 eagle-mem memories sync
 ```
-This scans all three directories, hashes each file, skips unchanged ones, and mirrors anything new or modified. It also backfills project names from Claude Code transcripts. Safe to run repeatedly -- content-hash dedup prevents double-insertion.
+This scans known Claude Code and Codex memory/task locations, hashes each file, skips unchanged ones, and mirrors anything new or modified. It also backfills project names from transcripts. Safe to run repeatedly -- content-hash dedup prevents double-insertion.
 
 ### 3. Search effectively
 
@@ -104,7 +104,7 @@ This asymmetry is intentional but easy to forget. If you're getting too many irr
 
 ### 5. Onboard an existing project
 
-When Eagle Mem is installed on a project that already has Claude Code history:
+When Eagle Mem is installed on a project that already has Claude Code or Codex history:
 ```bash
 eagle-mem memories sync
 ```
@@ -117,7 +117,7 @@ After sync or after expecting the hook to fire:
 eagle-mem memories list          # should show recent memories
 eagle-mem search --stats         # check counts are non-zero
 ```
-If memories list is empty after sync, check that `~/.claude/projects/` contains memory files for this project. If the hook isn't capturing new writes, check that PostToolUse hook is registered in settings.json.
+If memories list is empty after sync, check that `~/.claude/projects/` or `~/.codex/memories/` contains memory files. If the hook isn't capturing new writes, check Claude Code `settings.json` or Codex `hooks.json`.
 
 ## What makes a good memory lookup
 

package/skills/eagle-mem-tasks/SKILL.md

@@ -10,9 +10,9 @@ description: >
 
 ## Purpose
 
-**For the user:** Multi-step work doesn't get lost when Claude Code compacts. A 6-task implementation plan survives intact across compactions — no re-explaining what was decided, no drift from the original direction.
+**For the user:** Multi-step work doesn't get lost when Claude Code or Codex compacts. A 6-task implementation plan survives intact across compactions — no re-explaining what was decided, no drift from the original direction.
 
-**For you (Claude Code):** Each task description is a message to a future context window with ZERO memory of what happened before. After compaction, SessionStart re-injects pending/in-progress tasks from Eagle Mem's `claude_tasks` table. That re-injected text is all the next context window gets. If the description says "implement auth middleware," the next window has nothing to work with. If it says "implement auth middleware — JWT with RS256, sessions in Redis, errors use RFC 7807 format (decided in task 1)," the next window can execute immediately.
+**For you:** Each task description is a message to a future context window with ZERO memory of what happened before. After compaction, SessionStart re-injects pending/in-progress tasks from Eagle Mem's `agent_tasks` table. That re-injected text is all the next context window gets. If the description says "implement auth middleware," the next window has nothing to work with. If it says "implement auth middleware — JWT with RS256, sessions in Redis, errors use RFC 7807 format (decided in task 1)," the next window can execute immediately.
 
 ## Judgment
 
@@ -42,12 +42,12 @@ Break the request into tasks that are each completable in one context window. Th
 
 ### 2. Create — write self-contained descriptions
 
-Use `TaskCreate` for each task. The description is the most important field — it must carry forward every decision from the planning conversation.
+Use the agent-native task mechanism when available. In Claude Code, use `TaskCreate`. In Codex, use `update_plan` for the live UI and `eagle-mem tasks add --agent codex` for durable cross-session task records. The description is the most important field — it must carry forward every decision from the planning conversation.
 
 **Context transfer pattern:** For each task, ask: "If I read only this description with zero prior context, can I execute it?" If not, add what's missing.
 
 ```
-TaskCreate:
+TaskCreate / eagle-mem tasks add:
   subject: "Add JWT auth middleware"
   description: "Add Express middleware that validates JWT tokens on protected
     routes. Decisions: RS256 algorithm, public key from env JWT_PUBLIC_KEY,
@@ -60,15 +60,15 @@ TaskCreate:
 
 ### 3. Execute — one task at a time
 
-`TaskUpdate(in_progress)` on the current task. Do the work. Stay focused on that task — don't drift into adjacent tasks.
+Mark the current task in progress (`TaskUpdate(in_progress)` in Claude Code, or `eagle-mem tasks start <id> --agent codex` in Codex). Do the work. Stay focused on that task — don't drift into adjacent tasks.
 
 ### 4. Complete — record what happened
 
-`TaskUpdate(completed)`. Emit `<eagle-summary>` so Eagle Mem captures what was accomplished.
+Mark the task completed (`TaskUpdate(completed)` in Claude Code, or `eagle-mem tasks complete <id> --agent codex` in Codex). Emit `<eagle-summary>` so Eagle Mem captures what was accomplished.
 
 If the task produced decisions that downstream tasks need, update those task descriptions now:
 ```
-TaskUpdate:
+TaskUpdate / update durable task description:
   taskId: "3"
   description: "...original description... Note from task 2: the user table
     uses UUID primary keys, not auto-increment. Auth tokens table FKs to
@@ -90,7 +90,7 @@ After compaction, SessionStart re-injects all pending/in-progress tasks. Pick th
 **A task fails or produces unexpected results:** Update the task description with what was learned and what went wrong. Don't just retry blindly — the description should carry the failure context so the next attempt (or the next context window) doesn't repeat the same mistake.
 
 ```
-TaskUpdate:
+TaskUpdate / task record update:
   taskId: "4"
   description: "...original description... FAILED ATTEMPT: Prisma migrate
     errored because the users table already has a conflicting unique
@@ -102,11 +102,11 @@ TaskUpdate:
 
 ## The compact cycle — how task state survives
 
-1. You call `TaskCreate`/`TaskUpdate` (Claude Code's native task tools)
-2. Claude Code writes task JSON to `~/.claude/tasks/$session_id/*.json`
-3. Eagle Mem's PostToolUse hook fires, mirrors the task into the `claude_tasks` FTS5 table
-4. SessionEnd hook does a final sweep to catch any status changes missed by hooks
-5. On compaction (or new session), SessionStart queries `claude_tasks` for pending/in-progress tasks from the last 7 days and injects them into context
+1. Claude Code path: you call `TaskCreate`/`TaskUpdate`; Claude Code writes task JSON to `~/.claude/tasks/$session_id/*.json`; Eagle Mem mirrors it.
+2. Codex path: you call `update_plan` for live progress and `eagle-mem tasks add/start/complete --agent codex` for durable records.
+3. Eagle Mem stores both paths in the shared `agent_tasks` FTS5 table with `origin_agent`.
+4. SessionEnd does a final Claude Code task sweep where native task files exist.
+5. On compaction (or new session), SessionStart queries `agent_tasks` for pending/in-progress tasks from the last 7 days and injects them into context.
 
 The task descriptions you write ARE the context that survives. Everything else — your reasoning, the conversation, the files you read — gets compacted away.
 
@@ -126,14 +126,20 @@ The bad version forces the next context window to re-discover every decision. Th
 ## Reference
 
 ```bash
-# Viewing tasks (read-only — Eagle Mem mirrors, doesn't manage)
+# Viewing tasks
 eagle-mem tasks                # pending/in-progress for current project
 eagle-mem tasks list           # all tasks (including completed)
 eagle-mem tasks completed      # completed tasks only
 eagle-mem tasks search <q>     # FTS5 search across task history
 eagle-mem tasks --json         # JSON output for scripting
 
-# Claude Code task tools (these are what you actually use)
+# Codex durable task records
+eagle-mem tasks add "Implement auth middleware" --agent codex --desc "Use RS256, Redis sessions, RFC 7807 errors"
+eagle-mem tasks update <id> --agent codex --desc "New context or failure details"
+eagle-mem tasks start <id> --agent codex
+eagle-mem tasks complete <id> --agent codex
+
+# Claude Code task tools
 TaskCreate                     # create a new task
 TaskUpdate                     # update status, description, dependencies
 ```