I shipped 706 commits in 5 days with Taskwarrior + Claude Code

Source: Dev.to

Overview

Last week I merged 38 PRs across 5 repositories, resulting in 706 commits in just 5 days.
I’m sharing this because many Claude Code (CC) users hit the same productivity ceiling.

When you try to scale up CC by opening multiple terminals—each with its own task—you quickly end up context‑switching:

• Which session just finished?
• What does this session need from that one?
• Are two sessions editing the same file?

The founder of Claude Code reportedly runs 10+ parallel sessions, but the real advantage isn’t superhuman multitasking—it’s a system that eliminates coordination overhead.

I call this system TTAL — The Taskwarrior Agents Lab.

Tools

• Taskwarrior hooks spawn Zellij panes.
• Each pane runs a CC session with the task context injected.
• When a session finishes, the next highest‑urgency task auto‑starts.

You don’t manage sessions; you manage tasks.

Commit Log (Mon – Fri)

Thursday is the tell‑tale day: an API rate‑limit hit caused throughput to drop 75 %. The system, not the developer, was the bottleneck.

Design Principle

Agents never block waiting for you.

Most CC workflows are synchronous: you give a task, watch it work, review, then give the next task—making you the bottleneck at every step.

In TTAL:

1. Agents pick up tasks from the queue.
2. They perform the work, commit the changes, and move on.
3. You review PRs when you’re ready, not when the agent needs you.

This is why 5 asynchronous sessions outperform 10 synchronous ones.

Architecture & Documentation

The full system is documented at ttal.guion.io.
The architecture isn’t locked to Claude Code—Zellij can host any CLI agent inside its panes.

The bottleneck was never the AI. It was the glue.

Next Steps

This post is Part 1 of the TTAL series. Follow the series and explore the implementation details at ttal.guion.io.