hermes - 💡(How to fix) Fix fix(memory): publish verified Hindsight openai-codex durable patch

Summary

The Hindsight openai-codex durable patch is local-ready and independently verified, but publication from the current runner is blocked by missing maintainer GitHub write credentials.

Source

• Base branch: main
• Target branch: fix/hindsight-codex-durable-patch-main
• Local commit: 3210046fef9c6e2e838b4854b488a9908f56a711 (fix(memory): make Hindsight Codex provider durable)
• Patch SHA256: 659c76655bbbd5f2bd5a0552b5af12f218a2491c459ede3a78a586866ce62732

Files changed

• plugins/memory/hindsight/__init__.py — durable embedded Hindsight openai-codex config/provider wiring.
• plugins/memory/hindsight/codex_llm.py — Hermes/Codex OAuth-backed Hindsight LLM provider shim.
• tests/plugins/memory/test_hindsight_provider.py — regression coverage for schema, provider patching, env/profile behavior.

Verification

• python -m pytest tests/plugins/memory/test_hindsight_provider.py tests/test_empty_model_fallback.py -q -o 'addopts=' → PASS, 111 passed.
• git diff --check origin/main..HEAD → PASS.
• Targeted py_compile → PASS.
• Patch applies cleanly on isolated origin/main worktree.
• Runtime smoke: Hindsight daemon health/version/retain/recall(include_chunks=false)/reflect/watchdog → PASS.
• Secret scan on handoff + patch: no OpenAI/GitHub/JWT/private-key/raw-token patterns detected.

Maintainer commands

cd /path/to/hermes-agent
git fetch origin main
git switch -c fix/hindsight-codex-durable-patch-main origin/main
git am /path/to/hindsight-codex-durable.patch
python -m pytest tests/plugins/memory/test_hindsight_provider.py tests/test_empty_model_fallback.py -q -o 'addopts='
git diff --check origin/main..HEAD
git push -u origin fix/hindsight-codex-durable-patch-main

gh pr create \
  --repo NousResearch/hermes-agent \
  --base main \
  --head fix/hindsight-codex-durable-patch-main \
  --title "fix(memory): make Hindsight Codex provider durable"

Security

No secrets, tokens, account IDs, or raw logs are included. No raw OpenAI key is required; the runtime uses existing Codex/Hermes OAuth auth.

Note

A direct branch creation attempt from the current automation returned GitHub Not Found, consistent with missing write access. This issue is the upstream maintainer handoff until a maintainer pushes the verified patch and opens the PR.