A separate check-in thread
Technique
Run your main agent on a long goal, and keep a second chat that reads its history. You use that second chat to ask for status and what is slowing the work, which surfaces the real blockers.
Theo's current stance
Theo used this when progress slowed. It showed that too many jobs crashed the machine, so the agent built a queue, and then that it needed more computers.
Try it
- Keep a second chat that reads the main agent's history.
- Ask it what is currently bottlenecking the work and what the biggest problems are.
- Fix the top blocker, then ask again.
First seen
32:22
update on what's going on. Eventually I noticed that progress was slowing. So I asked the second thread, "Hey, what is currently bottlenecking the work being done? What are the biggest problems?" To
Every mention
32:22
update on what's going on. Eventually I noticed that progress was slowing. So I asked the second thread, "Hey, what is currently bottlenecking the work being done? What are the biggest problems?" To
Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.