Theo’s Low-Cost Experiment Auditing T3 Code Pull Requests

Theo describes using an inexpensive model to review recently updated pull requests and proposes a recurring readiness check.

ThTheo登壇者
チャンネル
Theo - t3․gg
公開日
2026年9月3日
動画
0:24
読了時間
1 分
スライド
2
原文
英語
YouTube で開く
スクロールすると動画は右下に小さくなって再生を続けます。字幕は閲覧言語に合わせて切り替わります。
閲覧言語2 言語で読めます
この記事はまだ日本語に翻訳されていないため、英語の原文を表示しています。
要約

30 秒でわかる

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.

  1. 1A low-cost auditTheo describes getting useful insight for 12 cents from a recent PR audit.
  2. 2Scope and usageThe request covered recently updated T3 Code PRs. The spoken token counts and the displayed usage snapshot do not match.
  3. 3A proposed recurring botHe plans a bot that checks periodically and alerts him to PRs it considers ready to merge.

ポイント

  1. Theo asked an agent to audit T3 Code pull requests updated in the previous five days.
  2. He describes the audit as costing 12 cents and proposes repeating it every three hours.
  3. The spoken token figures differ from the visible snapshot, and the clip does not explain the discrepancy.
全文

チャプターごとに整えた全文を読む

文字起こしのみ
01

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.

The PR audit request
スライド 1 / 2The PR audit requestThe on-screen prompt asks for recently updated open PRs and reports on overlap, issues and merge risk.
Usage snapshot
スライド 2 / 2Usage snapshotThe visible token totals differ from the spoken figures; the screen also shows a request to revise cache pricing.

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.

同じチャンネルの記事

スライド 5 枚36:07EN
Theo - t3․gg· 2026年10月27日Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.AI cost & performanceコーディングエージェントInference+1
スライド 5 枚30:37EN
Theo - t3․gg· 2026年10月26日Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.Agent skillsコーディングエージェントCode review & verification+2
スライド 2 枚0:43EN
Theo - t3․gg· 2026年10月23日Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.CybersecuritySoftware engineering
スライド 6 枚29:22EN
Theo - t3․gg· 2026年10月22日Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.CybersecurityAI securitySoftware engineering+1
スライド 4 枚31:13EN
Theo - t3․gg· 2026年10月20日Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.コーディングエージェントDeveloper productivityHuman-AI Collaboration+1
スライド 4 枚31:47EN
Theo - t3․gg· 2026年10月18日Theo on Asking Agents for Outcomes and Building the Tools They NeedTheo Browne · Ping LabsA tool-call report, a troubleshooting playbook and connected data show how prompting can reshape product engineering.Prompting & in-context learningコーディングエージェントエージェント工学+2