Opus 4.5, Amp's latest model, has a context window of 200k tokens, which some users view as limiting. However, Lewis Metcalf argues that this amount is sufficient for effective coding, especially when working with short threads. He emphasizes that shorter threads enhance focus and efficiency, making them easier to manage and keeping tasks well-defined. Metcalf provides insights from his recent work, highlighting a feature he developed with 13 interconnected threads, demonstrating how multiple short threads can collectively handle complex tasks without overwhelming the system. Long threads can lead to increased costs and poorer performance. Metcalf points out that every token in these threads incurs expenses, and models like Anthropic charge more for longer contexts. Additionally, long threads often lead to idle periods that can waste resources. He advocates for breaking down tasks into smaller, manageable threads, which aligns with traditional project management principles. Each thread serves a specific purpose, allowing for clearer organization and faster execution, much like how small tasks simplify workflow. Metcalf explains his process for creating and referencing threads within the Amp CLI. He starts with a basic implementation thread, then branches out into new threads for tweaks, refactoring, and validation. This method not only streamlines the coding process but also makes it easier to track progress and maintain clarity. The ability to reference previous threads, use commands for handoffs, and keep tasks distinct fosters a more efficient coding environment. Ultimately, he believes that 200k tokens are ample if utilized effectively through a structured approach to threading.