Give Codex a memory.
It keeps what you decided and why, and brings it back in later sessions, citing where it came from. Personal memory is free, and you sign in as part of the install. There's no key to copy.
- Free for personal memory
- Sign in during install
- Plugin source on GitHub
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.
What happens next
- 1
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.
- 2
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.
- 3
It comes back when it matters
In a later session, when something you already settled comes up, Codex uses it and says where it came from.
How you'll know it worked
- studio.assertion-ai.com/plugin lists this computer under Codex, with its version and when it last captured.
- After some real work, studio.assertion-ai.com/memory shows what it kept.
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.
Using something else?
It's one memory. Whatever you keep here is there in the other tools too.