CODEX_HOME environment variable unset in automation session
Source type:
obs· Harvested: 2026-05-03 · Original date: 2026-05-03T01:02:20.962Z Metadata:{"project":"Desktop","type":"discovery","obs_id":64915}
obs/64915 · discovery · 2026-05-03T01:02:20.962Z
CODEX_HOME environment variable unset in automation session
During initialization of the daily disk monitoring automation, the system attempted to read previous memory from $CODEX_HOME/automations/automation/memory.md to enable trend comparison. The CODEX_HOME environment variable was unset (empty), causing the mkdir command to attempt creating /automations in the root filesystem, which failed due to read-only permissions. This prevents the automation from accessing historical data for trend analysis, which is a core requirement (comparing directory sizes, identifying new items, tracking risk progression over time).
Concepts: [“gotcha”,“problem-solution”,“how-it-works”]
Facts: [“CODEX_HOME environment variable returned empty string in current session”,“Attempt to create /automations directory failed with “Read-only file system” error”,“Automation memory path $CODEX_HOME/automations/automation/memory.md could not be accessed”,“Session working directory is /Users/lunhsiangyuan/Desktop”]
[← 回 Alfred Brain Hub]