Setting Yourself Up for Success — Jason Liu’s Codex Workshop
Jason Liu on persistent project threads, recurring wake-ups, goal verification, and coordinated workstreams
Jason Liu presents a personal operating model for long-running agent work: named project threads, reviewable context, reusable skills, scheduled wake-ups, observable goal checks, and monitor threads that coordinate downstream work. He also discusses the limits of broad computer access, live-connector evaluation, token-intensive workflows, and cross-project memory.
Jason Liu, who says he works at OpenAI, presents a personal operating model for moving agent work beyond disposable sessions. The workshop connects persistent project context, named threads, reusable skills, recurring wake-ups, observable goals, and thread-to-thread coordination. It is a practitioner account, not a controlled reliability study.
Key Points Covered
- Long-lived threads preserve a workstream: Liu argues that improved compaction makes named, pinned project threads practical for ongoing work and lets each thread delegate narrower tasks to subagents 03:02–07:11(opens in a new tab).
- Context should be both recoverable and reviewable: He combines voice input, skills, plugins, memory, and project files, and keeps his agent-maintained notes in Git so he can inspect changes with
git diff08:04–17:05(opens in a new tab), 21:51–22:41(opens in a new tab). - Personal skills improve through correction: Liu builds personal workflows quickly, corrects mistakes as they appear, and waits for repeated use before sharing a skill with a team. He also notes that workflows spanning live connectors such as Slack are difficult to snapshot and evaluate reproducibly 23:42–24:44(opens in a new tab).
- Heartbeats wake an existing thread: Instead of creating a new session for every scheduled run, a heartbeat sends a message back into the same thread so it can resume with its accumulated context 34:49–40:06(opens in a new tab).
- Goals need observable checks: Liu describes goals as verification steps that let an agent continue until a condition is met. For longer runs, he also uses editable goal, plan, state, and work-log files 40:06–41:08(opens in a new tab). Editorial caveat: A passing check proves only the property it measures, not that the whole result is correct.
- Monitor threads can coordinate visible workstreams: His monitor pattern creates downstream threads for issues, updates them when new evidence appears, and leaves those threads visible for human inspection rather than hiding every task as a background subagent 55:53–58:43(opens in a new tab).
- Recurring work needs cadence and stopping criteria: Liu recommends matching reasoning effort to the task, controlling how often a heartbeat runs, keeping no-change replies minimal, and defining when the loop should stop 1:11:47–1:13:46(opens in a new tab).
Limits and Risks
- Liu's personal setup benefits from unusually generous token access, so its cost and latency do not generalize directly to constrained teams 23:42–26:53(opens in a new tab).
- Broad computer access can let a determined model route around connector restrictions through the graphical interface. Permission settings and project instructions help guide behavior, but they are not complete security boundaries 29:54–33:52(opens in a new tab), 52:40–54:49(opens in a new tab).
- Liu reports good results from memory and compaction but does not establish how cross-project memory leakage should be measured or prevented 1:01:36–1:04:29(opens in a new tab).
Full video: https://www.youtube.com/watch?v=il1c1a2FufU(opens in a new tab)