# AGENT THREADS. How to SHIP like Boris Cherny. Ralph Wiggnum in Claude Code. Source: https://www.youtube.com/watch?v=-WBHNFAB0OE Recap page: https://rapidrecap.app/video/-WBHNFAB0OE Generated: 2026-01-12T14:34:46.944+00:00 --- ## Quick Overview The four ways to improve agentic engineering, as illustrated by the evolution from beginner to expert workflows, are: running More P-threads (parallel execution paths), running Thicker B-threads (more work per unit time), running Longer L-threads (extended duration without human intervention), and running Fewer checkpoints (reducing human trust points). **Key Points:** - The video presents four concrete ways to improve agentic engineering: More (P-threads), Thicker (B-threads), Longer (L-threads), and Fewer (reducing human checkpoints/increasing trust). - P-threads involve parallel execution paths, exemplified by running multiple threads simultaneously (e.g., 10 threads mentioned in Boris Cherry's setup). - B-threads focus on thicker work, meaning more work per unit time, often involving agents prompting other agents (super meta structure). - L-threads represent long-duration tasks with high autonomy, requiring no human review between steps (e.g., Step 100 shown in the diagram). - F-threads utilize fusion and selection by prompting multiple agents and aggregating the best result (Best of N), which is crucial for rapid prototyping. - C-threads handle phased workloads where human intervention guides each phase, contrasting with the 'Zero Touch, Maximum Trust' Z-Thread. - The ultimate goal is to reach the Z-Thread, characterized by 'Zero Touch, Maximum Trust,' where agents operate autonomously for long durations without manual review. ![Screenshot at 2:04: The base thread structure is introduced as 'A unit of engineering work over time driven by you and your agent\(s\),' showing a linear progression from Prompt \(P\) to Agent Work \(tool calls\) to Review \(R\).](https://ss.rapidrecap.app/screens/-WBHNFAB0OE/00-02-04.jpg) **Context:** The video is a tutorial by IndyDevDan explaining advancements in agentic engineering, framed around the concept of 'threads'—units of engineering work over time driven by an engineer and their agents. The presentation draws heavily on concepts and tweets shared by prominent figures like Andrej Karpathy and Boris Cherry, contrasting simple base threads with more complex P-threads, C-threads, F-threads, B-threads, L-threads, and finally, the highly autonomous Z-Thread. ## Detailed Analysis The video details the evolution of agentic engineering workflows, starting from simple base threads (P -> R) and progressing through several advanced thread types: P-threads, C-threads, F-threads, B-threads, L-threads, and finally, the Z-Thread. P-threads (Parallel Execution) involve running multiple parallel execution paths (e.g., 2-4 threads) to increase throughput. F-threads (Fusion & Selection) use a same-prompt strategy across multiple agents, fusing the results (Best of N) to select the best outcome, ideal for rapid prototyping. C-threads manage phased workloads where human intervention guides each phase in a chained process, suitable for high-risk production work. B-threads introduce a super meta structure where a primary agent prompts sub-agents (Base, P-Thread, C-Thread, F-Thread) to complete tasks concurrently, resulting in thicker, more complex work within a single thread. L-threads focus on high autonomy and long duration, running for hours without human review (e.g., Step 100 shown), which requires high trust in the agent's process. The four ways to improve agentic engineering are summarized as: More (P-threads), Longer (L-threads), Thicker (B-threads), and Fewer (reducing human checkpoints/increasing trust). The ultimate goal presented is the Z-Thread, representing 'Zero Touch, Maximum Trust,' where agents run complex, long-running tasks autonomously without manual intervention, reflecting the future of engineering. ### Introduction and Context Setting - Andrej Karpathy's tweet highlights the profession being dramatically refactored due to agentic tools; Boris Cherry's setup involves running 5-10 Claudes in parallel using system notifications. - The core concept is the Base Thread: a unit of engineering work over time driven by you and your agent(s), consisting of Prompt, Agent Work (tool calls), and Review. ### Thread Types and Evolution - Base Thread (1 step) -> P-Threads (parallel execution paths, 2+ threads) -> F-Threads (fusion/selection of multiple results) -> C-Threads (phased workloads guided by human review) -> B-Threads (super meta structure with nested threads) -> L-Threads (long duration, high autonomy, no human review) -> Z-Thread (Zero Touch, Maximum Trust). ### Four Ways to Improve - More (P-threads: parallel execution paths) - Longer (L-threads: extended duration without intervention) - Thicker (B-threads: more work per unit time, nested threads) - Fewer (reducing human checkpoints, increasing trust). ### Key Concepts Highlighted - Stop Hook (intercepts completion attempts until validation passes) - Ralph Wiggum analogy used to explain the need for deterministic validation over reliance on AI saying 'I'm done'. - Boris Cherry's workflow involves using multiple agents in parallel (5-10 Claudes) and pre-allowing common bash commands via settings. ### Conclusion - The Z-Thread represents the future of engineering where trust is maximized, achieving zero touch, long-duration work. ![Screenshot at 0:00: Overhead shot of the presenter typing on a laptop, setting the scene for a technical discussion.](https://ss.rapidrecap.app/screens/-WBHNFAB0OE/00-00-00.jpg) ![Screenshot at 0:04: On-screen text posing the central question: "How do you know you're improving?"](https://ss.rapidrecap.app/screens/-WBHNFAB0OE/00-00-04.jpg) ![Screenshot at 0:30: A graph illustrating the 'Impact Gap' widening between engineers using agents \(green line\) and those without \(gray line\).](https://ss.rapidrecap.app/screens/-WBHNFAB0OE/00-00-30.jpg) ![Screenshot at 2:01: Slide defining 'The Base Thread' as a unit of engineering work driven by the engineer and agents, showing the P -\> Agent Work -\> R flow.](https://ss.rapidrecap.app/screens/-WBHNFAB0OE/00-02-01.jpg) ![Screenshot at 11:54: Diagram illustrating F-Threads: multiple parallel prompts feeding into a Fusion/Best of N step before the final Review.](https://ss.rapidrecap.app/screens/-WBHNFAB0OE/00-11-54.jpg)