codex-setup
Skill29 starsChanged 32 days agoApache-2.0View on GitHub
Set up OpenMyMemo in Codex so every new session starts with the user's memory. Use in Codex when the user asks to set up OpenMyMemo, or says Codex doesn't know them at the start of a session.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- WaterTian/cc-hudtheir own version, first seen Nov 8, 2026
- sd0xdev/sd0x-dev-flowtheir own version, first seen Oct 8, 2026
- sd0xdev/sd0x-harnesstheir own version, first seen Oct 6, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- WaterTian/cc-hud★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Don't edit ~/.codex/hooks.json yourself, and don't try to trust the hook for them.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
This is for Codex only. In any other app, tell the user it isn't needed there and stop.
Codex doesn't run hooks that plugins ship, so OpenMyMemo adds a session-start hook to the user's own
~/.codex/hooks.json. Run this in a shell; it finds the newest installed OpenMyMemo plugin and runs its
setup script, which leaves the user's other hooks alone:
sh "$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/openmymemo/openmymemo/*/ | sort -V | tail -n 1)integrations/codex/setup.sh"Tell the user in a line or two what it printed, then give them the last step, which only they can do, once:
trust "Loading your OpenMyMemo memory", either in the ChatGPT desktop app under Settings → Coding → Hooks,
or by opening Codex in a terminal (codex), typing /hooks and selecting SessionStart. The app and the
terminal share these settings, so either place covers both. From the next new session on, their memory
loads automatically.
Don't edit ~/.codex/hooks.json yourself, and don't try to trust the hook for them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.