Find your agent limit
Build-along · ~15 min at your own keyboard
At some number of simultaneous agents, YOU become the bottleneck: sessions sit waiting on your input, you switch badly, forgotten tabs rot. Many people report hitting that around 3 or 4, but there's no fixed number — it depends on the work and on you. Find yours by measuring: if sessions often sit idle waiting for you, you have too many, not too few. This lesson is 15 minutes of setup, then two ordinary work blocks this week where you observe.
The long version: How many agents at once ↗
Mac: Mac: turn on the terminal bell, or run afplay /System/Library/Sounds/Glass.aiff from a hook, so a finished agent makes a sound.
Windows: Windows: turn on the terminal bell, or run [console]::beep() in PowerShell from a hook, so a finished agent makes a sound.
Do this
0/4Checkpoints
- ▸You should now see notes on idle time and stress from the 2-session hour.
- ▸You should now see the same notes from the 4-session hour.
- ▸You should now see a chime or notification firing when an agent finishes.
- ▸You should now see your personal cap written as a number.
The three ways this goes wrong
- You forget which tab is which. — Name each session when you start it, in the first line you send.
- You never hear the agent finish. — Test the notification once on purpose before the hour starts.
- Your cap is a feeling ('not too many'). — Write a number and the one exception you allow.
Share what happened
Paste your 2-vs-4 observations and your written cap rule.
Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].
🔒 Don't paste confidential, personal-health, or payment info.