Dev moves nearly all code changes to subthreads, parent thread just orchestrates
zeeg · x · 2026-11-14
The author shares a recent major investment in his AI coding workflow: the project already has several reactive context mechanisms, but now almost all code changes go through a subthread while the parent thread manages the work. The reasons: doing variable work inside subthreads is hard, and the pattern simplifies a lot. As he puts it, organizing work is a pain — which is exactly why he's investing in it.
More from coding & agent
- Yogurt: open-source local-first Granola alternative for private AI meeting notes — supportingthedogs · 2026-11-14
- Anthropic Breaks Down the Five Primitives Behind Always-On AI Agents — dotey · 2026-11-14
- Compacting at 500k tokens costs a third less than 1M: real usage data on context compression — EricBuess · 2026-11-14
- Context Vim idea: diffusion LLMs could edit full code pages with control tokens — ryunuck · 2026-11-14
- Agent drives Unreal Engine via MCP: auto lighting, rendering and self-critique loop — HankYeomans · 2026-11-14
- Running Claude agent sessions visualized as characters in an Oasis game world — LeviTurk · 2026-11-14