Attention and execution

  • Theo treats threads as to-dos. "Settle" removes completed work from the sidebar; the target is to finish the day with threads either gone or still working. This helps select what needs attention but does not eliminate context-switching cost. 39:44 40:16 40:39
  • Choose a remote execution machine before starting a thread so closing the laptop does not stop work. T3 Code groups repository copies by Git origin; he generally chooses Linux and uses Macs when mobile or computer-use work needs them. 41:49 42:17
  • Command-Enter sends a new thread in the background while leaving the user in place to submit another task. He checks threads when they show done or input, rather than watching generation. 44:02 44:25
  • Automatic load balancing distributes new tasks across connected servers. His operating assumption is that agents can run concurrently while human attention remains the bottleneck. 44:50 45:19

Ask for a complete return package

  • For connected-device settings, he supplies a screenshot and identifies ambiguous disconnect behavior and missing remove actions. He authorizes direct implementation if the approach is clear, otherwise asks for several HTML mockups to choose between. 42:51 43:10 43:35 44:02
  • For paragraph-based streaming, he first asks whether the change is difficult because he only wants it if friction is low. He dismisses the agent's "half a day" estimate as unreliable. 45:43 46:04
  • Then he requests implementation, a PR, and a Tailscale-accessible test environment, adding PR monitoring afterward. Including all deliverables upfront avoids several unnecessary attention cycles. 46:21 46:41 47:02
  • He says merging a linked PR removes its thread. With explicit merge conditions, the agent can finish without another user visit; he estimates about half his threads disappear before he reads their final message. 47:28
  • New threads use separate Git worktrees by default. He describes same-branch checkout conflicts during independent review and expects agents to solve them with another branch or clone. 47:54 48:22
  • He reports auto-settlement after three inactive days by default, changed to seven in his setup. Snoozing defers a task; dimmed working threads emphasize completed work and requests for input. 48:46 49:05 49:31