A day running Claude Code across several projects

This is what a working day looks like for us with the wall open. Not a demo, the actual rhythm, including the boring parts.

Morning: reopen, read, brief

Launch the app. Every tile from yesterday comes back with its title and last results. Read the feed rows, not the terminals. Two sessions finished overnight and need a review. One is waiting for a yes. One drifted and needs a new brief.

Spend the first twenty minutes writing briefs for the day: one per tile, each with a goal and a done condition. Then stop touching them.

Midday: glance, answer, move on

Keep the wall on a second screen or behind the editor. A tile that turns to a prompt gets a thirty-second answer. A tile that finishes gets its diff reviewed and either merged or sent back with one line. Never read a full scrollback; if the feed row does not tell you what happened, the brief was wrong.

Afternoon: the dangerous hour

Around three, the temptation is to open more tiles. We usually run ten to fifteen and on heavy days twenty. The limit is not the Mac, it is review: every finished tile needs a pair of eyes, and if the finished pile grows faster than you can read it, stop opening new ones until it shrinks.

Evening: leave it

Quit the app. Do not close tiles to tidy up. Tomorrow they come back exactly as they are, and the half-finished one will still know where it was.