Skip to content

Add Codex persistent memory blog post#812

Merged
benfrank241 merged 9 commits into
mainfrom
blog/adding-memory-to-codex-with-hindsight
Apr 8, 2026
Merged

Add Codex persistent memory blog post#812
benfrank241 merged 9 commits into
mainfrom
blog/adding-memory-to-codex-with-hindsight

Conversation

@benfrank241

Copy link
Copy Markdown
Member

Summary

Notes

  • Cover image /img/blog/adding-memory-to-codex-with-hindsight.png needed before merge

🤖 Generated with Claude Code

@benfrank241
benfrank241 force-pushed the blog/adding-memory-to-codex-with-hindsight branch from 040bc43 to ee69347 Compare March 31, 2026 15:01

**Full-session upsert.** The transcript is stored using the session ID as the document key. If a session is retained multiple times (in chunked mode), the content is upserted rather than duplicated. No accumulation of near-identical entries.

**Zero dependencies.** The plugin is three Python stdlib scripts. No pip install, no virtualenv, no version conflicts.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can't be true


**Recall adds latency.** Every prompt triggers a Hindsight query before Codex sees it. In practice this is 100–300ms with Hindsight Cloud on a fast connection. For interactive sessions it's imperceptible; for automated scripts it may matter. Use `"recallBudget": "low"` or `"autoRecall": false` if you need to skip it.

**Retention is asynchronous.** The `retain.py` hook fires asynchronously so it doesn't block your session from exiting. Facts extracted from a session won't appear in recall until the next session.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fact may not appear until later, not necessarily the next session. It depends on how fast the async processing goes.

@cdbartholomew

Copy link
Copy Markdown
Contributor

Could we add one short troubleshooting note to the post? Something like: “Nothing happening? Check ~/.hindsight/codex/error.log first for hook failures. If you need more detail, enable "debug": true and inspect ~/.hindsight/codex/debug.log.” We’re opening a separate PR that adds this persistent logging behavior to the Codex integration, so this note depends on that change landing.

benfrank241 and others added 7 commits April 8, 2026 10:25
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Clarify "zero dependencies" — hook scripts are stdlib-only but local
  daemon mode requires uvx; Cloud mode has no local prerequisites
- Fix retention timing — facts may appear sooner or later than the next
  session depending on async processing speed

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Documents the persistent log files added by the upcoming Codex
integration PR: error.log for hook failures, debug.log when
debug mode is enabled.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@benfrank241
benfrank241 force-pushed the blog/adding-memory-to-codex-with-hindsight branch from 7aa9d14 to a8aafcc Compare April 8, 2026 14:25
benfrank241 and others added 2 commits April 8, 2026 10:29
- Add Cloud bullet to TL;DR
- Note no daemon required when choosing Cloud during install
- Rename "Connecting to Hindsight Cloud" -> "Hindsight Cloud (Recommended)" with clearer framing
- Note per-project isolation works with Cloud
- Move Cloud CTA to top of Next Steps

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The post doesn't exist in this branch so Docusaurus broken link check fails.
Switching to absolute URL bypasses validation until both PRs are merged.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@benfrank241
benfrank241 merged commit 9e23e83 into main Apr 8, 2026
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants