v13.10.1
Fixed
- Codex SessionStart hook no longer fails at startup by emitting valid hookSpecificOutput with hookEventName and additionalContext fields when a hook errors before its handler runs
- Codex adapter now preserves explicit empty-string additionalContext in output instead of silently dropping it
Fixes
- Codex SessionStart hook no longer fails at startup. When a hook errored before its handler ran (missing
session_id, invalidcwd, or a missing transcript path), claude-mem fell back to a bare{"continue":true}regardless of which hook fired. Codex's strictSessionStartvalidator rejects that shape as "invalid session start JSON output," breaking context injection at Codex startup. The fallback now emits a validhookSpecificOutput: { hookEventName: "SessionStart", additionalContext: "" }for thecontexthook, matching what Codex expects. - Fixed a related gap where the Codex adapter silently dropped an explicit empty-string
additionalContextfrom its output instead of preserving it, which could leave the SessionStart payload incomplete.
Closes #2947, #2972. Supersedes #2953 and #2948.