Jason Liu’s workflow for turning Codex into a persistent operating loop: durable threads, voice input, file-based memory in an Obsidian vault, Heartbeats, and Goals with real verification criteria.
Key Takeaways
Pinned megathreads with compaction let workstreams accumulate months of history, preferences, and decisions without losing context between sessions.
Memory-as-files in an Obsidian vault (checked into GitHub) makes agent-written knowledge inspectable via diffs, portable across threads, and survivable if a thread dies or compacts badly.
Heartbeats let threads self-schedule recurring checks: a Chief of Staff thread runs every 30 minutes to draft Slack and Gmail replies before you return.
Computer use, @chrome, and $browser serve distinct roles: local preview, authenticated multi-tab sessions, and GUI-only tasks respectively.
Goals need a real oracle to be useful: migrating Python Rich to Rust only counted as done when the Rust port passed the original unit test suite.
Hacker News Comment Review
The main caution raised is that file-based memory requires a verification layer: agents will plausibly claim to update vault entries, write stub content, or silently drift from reality without one.
