In 30 Sekunden
Theo says an AI-assisted audit of recently updated T3 Code pull requests produced useful insight for 12 cents. He proposes running a bot every three hours to flag PRs it considers ready to merge. The spoken token totals differ from the figures visible in the on-screen snapshot, so they should not be assumed to describe the same measurement.
- 1A low-cost auditTheo describes getting useful insight for 12 cents from a recent PR audit.
- 2Scope and usageThe request covered recently updated T3 Code PRs. The spoken token counts and the displayed usage snapshot do not match.
- 3A proposed recurring botHe plans a bot that checks periodically and alerts him to PRs it considers ready to merge.
Das Wichtigste
- Theo asked an agent to audit T3 Code pull requests updated in the previous five days.
- He describes the audit as costing 12 cents and proposes repeating it every three hours.
- The spoken token figures differ from the visible snapshot, and the clip does not explain the discrepancy.
Den bearbeiteten Text nach Kapiteln lesen
Auditing PRs and planning a recurring check
Theo describes a low-cost audit of recently updated pull requests. He proposes automating a readiness check every three hours.


I got a useful insight for 12 cents. I did not just ask the agent to audit my own pull requests: I asked it to examine the open T3 Code PRs updated in the last five days.
I say the audit used six billion input tokens, mostly cached, and 300,000 output tokens. The usage snapshot shown in the clip instead displays about 6.23 million input tokens and 30,642 output tokens, with a pricing calculation being revised; the clip does not explain whether these are the same measurement.
I plan to set up a bot to repeat this every three hours and notify me when it thinks a pull request is ready to merge. I expect that to help us ship faster.
Mehr aus diesem Kanal
36:07EN
30:37EN
0:43EN
29:22EN
31:13EN
31:47EN