Extend delegation beyond coding

  • Theo describes asking an agent to collect and organize MRI PDFs from doctors' portals, a task for which he might otherwise have considered writing a dedicated program. 21:38
  • His explanation is that prompting makes worthwhile tasks possible that he would never have bothered building software for. Those experiments then reveal which tools and connections are worth engineering. 22:26 22:50

Email example and reported outcome

  • Theo has five inboxes and actively monitors four. Frustration with email clients had repeatedly pushed him toward building his own email application. 23:18
  • After a hand injury, he connected multiple email accounts to ChatGPT. He says he went from checking email about 10 times a day to roughly once a day, relying on agents for more of the work. This is his personal account. 23:49

Proposed workflow across systems

  1. Ask an agent to watch for particular emails, such as an expected large AWS bill. 23:49 24:10
  2. Use the bill as the starting point for a request to investigate the AWS dashboard and find ways to reduce costs. This is an illustrative request; the video gives no resulting savings figure. 24:10
  3. Through the T3 Code MCP connection, Codex or Dot can start Claude threads in T3 Code. Theo describes connecting these systems so an email can lead to engineering work across agents and applications. 24:10 24:37

Design lesson

  • Connecting the relevant data and actions lets a single request cross application boundaries. Theo's engineering emphasis is on those connections and data access, which expand what later prompts can accomplish. 22:50 24:37