Automations seem unable to access their memory
Open 💬 1 comment Opened Mar 15, 2026 by virgildotcodes
What version of the Codex App are you using (From “About Codex” dialog)?
26.311.21342 (993)
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
I've recently begun experimenting with automations, and each automation run tries to access its memory and states it cannot.
Codex diagnosis:
Because the automation is looking in the wrong place.
In this environment:
CODEX_HOME is empty
but the memory file does exist at memory.md
So when it runs:
if [ -f "$CODEX_HOME/automations/summarize-trello-activity-on-jeweldesignai/memory.md" ]; then ...
that path becomes:
/automations/summarize-trello-activity-on-jeweldesignai/memory.md
not your real memory file. Since the if [ -f ... ] check simply fails, the command prints nothing and still exits successfully, so the agent concludes “no prior run memory.”
So the root cause is not that memory is missing. It’s that $CODEX_HOME is unset in the automation shell, and the command silently falls through.
The practical implication is:
every run that reads memory via $CODEX_HOME/... will keep thinking memory is empty
the automation needs to read the absolute path instead, or the runtime needs to export CODEX_HOME
What steps can reproduce the bug?
Create an automation, run it, see if it can access its own memory.
What is the expected behavior?
It should be able to access its memory.
Additional information
Feedback id - 019cf10f-5235-7961-a784-a64a032b0906
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗