Somewhere in the last two years the job quietly changed. The bottleneck stopped being "how fast can I write this" and became "how many well-specified tasks can I keep in flight, and how fast can I judge the results." The engineers getting outsized leverage from agents aren't typing faster — they're running a different loop.
The loop
It has four beats, and each one has a failure mode the tooling has to solve:
-
Dispatch. Turn an intention into a well-scoped brief and hand it to
an agent — the right agent, with the right model, permissions, and isolation.
Failure mode: dispatch friction. If starting an agent takes a minute of
setup, you'll batch tasks in your head instead, and the parallelism never happens.
In hang4r, New Agent is one dialog: backend
(Claude, Codex, or Cursor), model, permission mode, worktree toggle, go. Defaults
come from your
settings.json, per workspace. - Glance. Know, at any moment, which of your sessions needs you. Failure mode: polling. If you have to read each session to know its state, five agents cost more attention than they save. The tiled workspace answers it ambiently: status LEDs per tile, action-required badges that hit the dock, queued messages so your next thought doesn't wait for the agent's current turn.
- Review. Judge the diff, not the conversation. Failure mode: trust by exhaustion. The 400-line diff at the end of a long session gets skimmed, not reviewed. Per-turn checkpoints keep diffs turn-sized, and inline comments go back to the agent as the next prompt — so review effort turns into revision, not into chat archaeology.
- Merge. Land it and move on. Failure mode: the integration pile. Ten finished branches you haven't merged are ten open loops. Because every session lives on its own worktree branch, merge is a button on the diff panel — commit, merge, or open the PR — and the session archives with its transcript.
What changes in your day
Run this loop with decent tooling and the texture of the day changes. Mornings start by dispatching three or four briefs, not by opening an editor. The "focus block" becomes a review block. You develop a new instinct for which tasks parallelize (bug fixes, tests, migrations, refactors with crisp boundaries) and which deserve a single long-running session with your full attention.
You also hit the new constraint fast: your plan's rate limits are the new CI queue. This is why hang4r keeps your Claude 5-hour and weekly gauges on screen — dispatching is a spending decision now, and you should make it with the meter visible.
Conductor is not a metaphor for "manager"
The conductor doesn't write the music and doesn't play the instruments — but nothing coherent happens without them. The skill is still deeply technical: writing briefs that are really specifications, smelling a wrong approach in a diff at a glance, knowing when to rewind a session instead of arguing with it. Agents didn't remove the engineering. They moved it up one level of abstraction.
The tools are catching up to that job description. That's the window we're building.