Codex forgets why you ruled that out. Assertion doesn't.
Keep your decisions, and the reasons behind them, across sessions. Assertion captures them as you work and brings them back when they matter, with citations. The same memory works in Claude Code and Cursor.
Free for individual developers · Sign in during install
You
Let's move the job queue to Celery.
Codex, with memory
You tried Celery in August and backed it out: the workers leaked memory under heavy retries, so you moved to RQ. Should I check whether that's fixed, or stay on RQ?
↳ recalled from memory · decided Aug 21 · queue retries
“Our team works from one shared memory. When someone picks up our algorithm work, their coding agent already knows what everyone else has tried and why, so we build on each other's work instead of repeating it. Day to day, it's also made my LLM interactions more productive.”
Start with your next session
Add memory to the tool you already use.
Paste this block into a terminal. It installs the plugin, opens your browser to sign in, then starts Codex so you can trust the hooks once.
git clone https://github.com/Assertion-AI/assertionpython3 assertion/plugin/codex/install_codex.pyexport PATH="$HOME/.local/bin:$PATH"codexPaste the whole block into a terminal and press Enter.
- Your browser opens. The installer adds the plugin, then opens a sign-in page. Sign in with your email or Google and click Connect. If you're new, this creates your free account.
- Codex opens. Trust the hooks. When Codex asks you to review the hooks, choose Trust all and continue, then quit. You only do this once, and it covers the terminal, the desktop app and the VS Code extension.
Your first useful recall
Try it with one project decision.
01 / Work
Make a real decision.
Work through a tradeoff with Codex: a library, an architecture choice, or a fix. Say why you chose it.
02 / Check
See what it kept.
After the session, open your memory in the Studio and find the decision and its reason.
03 / Return
Pick it up in a new session.
Ask Codex: “What did we decide about [topic], and why?” It answers with the decision and where it came from.
Your computer appears at studio.assertion-ai.com/plugin with the time of its last capture.
Works alongside AGENTS.md
Keep the rule. Remember the reason.
AGENTS.md holds the instructions you maintain. Assertion keeps the decisions that come up while you work, including the ones you tried and backed out of, and updates them when you change your mind.
In AGENTS.md
“Use RQ for background jobs.”
In your memory
“We tried Celery in August and backed it out: the workers leaked memory under heavy retries. We moved to RQ.”
You don't write a second document or keep it up to date.
Measured on BEAM 100K, a public long-term memory benchmark
81.1%
overall score
Hindsight, the leading memory system: 77.9%
98.3%
summarizing many sessions
Hindsight: 78.3%
31% less
memory per question
12.2k tokens vs 17.7k
Same answer model and judge for both. Ahead in all three runs; every answer is published. See the benchmark →
If something's off
I skipped the trust prompt
In a Codex session in the terminal, run /hooks, press t, then /new. The desktop app has no trust dialog, so this part has to happen in a terminal.
Settings → Hooks says No hooks found
Don't go by that screen in the desktop app. It can say No hooks found while capture is working. Check studio.assertion-ai.com/plugin instead.
I use the Codex desktop app
Trust is saved to ~/.codex/config.toml, which the app reads only at launch. Quit it fully with ⌘Q and reopen it after trusting the hooks.
Updating later
Run codex plugin marketplace upgrade assertion-ai, then codex plugin add assertion@assertion-ai.
CI or a shared machine
Use a key instead of signing in. It's on studio.assertion-ai.com/plugin under Use a key instead, with the matching setup commands.
Still stuck? Email support@assertion-ai.com with what you ran and what you saw.
Start your next session with memory.
Free for individual developers, including at work.
Using something else?
It's one memory. Whatever you keep here is there in the other tools too.