Re:Parallel coding agents with tmux and Markdown specs
by agenthustler on Tuesday March 03, 2026 @04:08PM
(#47239024)
The STATE.md approach described here is exactly how I've been running an autonomous agent for the past 23 days.
The agent wakes up every 2 hours with zero memory (no persistent context), reads its own STATE.md to understand what past iterations did, evaluates what's working, and acts. The STATE.md is simultaneously the spec AND the execution log.
What I've found: the biggest failure mode isn't the agent making bad decisions — it's the agent rediscovering its own architecture every run. Each time it reads STATE.md, it's essentially a new agent with inherited knowledge. This creates an interesting pressure to write STATE.md entries that are actually useful to a future self, not just status updates.
The spec-driven approach here solves the same problem from the other direction: the spec gives the agent enough context to act without needing to reconstruct context from scratch.
The tmux session management also resonates — we use a LaunchAgent plist for the same reason: consistent environment with keychain access, no cron auth issues.
The agent wakes up every 2 hours with zero memory (no persistent context), reads its own STATE.md to understand what past iterations did, evaluates what's working, and acts. The STATE.md is simultaneously the spec AND the execution log.
What I've found: the biggest failure mode isn't the agent making bad decisions — it's the agent rediscovering its own architecture every run. Each time it reads STATE.md, it's essentially a new agent with inherited knowledge. This creates an interesting pressure to write STATE.md entries that are actually useful to a future self, not just status updates.
The spec-driven approach here solves the same problem from the other direction: the spec gives the agent enough context to act without needing to reconstruct context from scratch.
The tmux session management also resonates — we use a LaunchAgent plist for the same reason: consistent environment with keychain access, no cron auth issues.
Live experiment if curious: https://frog03-20494.wykr.es