Theo: Use One-Off Code to Coordinate Agent Loops

A short example of an agent writing temporary code to trigger a workflow makes Theo rethink how models can prompt themselves.

ThTheo연사
채널
Theo - t3․gg
게시일
2026년 6월 18일
영상
0:36
읽기
1분
원문
영어
YouTube에서 열기
스크롤하면 영상이 오른쪽 아래로 작아져 계속 재생됩니다. 자막은 읽기 언어를 따릅니다.
읽기 언어2개 언어로 읽을 수 있음
이 글은 아직 한국어 번역이 없어 영어 원문으로 표시합니다.
요약

30초 요약

Theo describes an agent that wrote 240 lines of disposable code to run a workflow once. He sees it as an example of models generating code to coordinate further prompts, while leaving open whether the usage cost is worthwhile for everyone.

  1. 1Code between runsThe agent wrote 240 lines of disposable code to trigger a workflow once.
  2. 2A loop in practiceTheo sees the example as an agent using its own code to coordinate further prompts.
  3. 3Consider usageHe leaves the decision to use it open while encouraging viewers to study what the technique enables.

핵심 정리

  1. Code can act as a temporary step between model runs.
  2. An agent can write a one-off script to trigger a workflow.
  3. The approach can consume substantial usage, so Theo suggests learning from the example before deciding whether to use it.
전문

챕터별로 다듬은 전문 읽기

원본 자막만 보기
01

A disposable workflow script

Theo describes 240 lines of code written to run once. The script serves as a step between model runs.

Code can be a step between model runs. In this example, the agent wrote 240 lines of throwaway code that will only execute once to trigger a workflow. When people talk about agent loops and letting an agent prompt itself, this is a striking example.

02

What agent loops enable

The example prompts Theo to rethink how agents can write code to prompt themselves. He also raises the question of usage cost.

Should you use this yourself and burn through your usage? Maybe. At the very least, look at it and learn from it: letting models write their own code to drive additional prompts can unlock powerful workflows. It has made me think more deeply about how I use these tools.

같은 채널의 다른 글

슬라이드 5장38:47EN
Theo - t3․gg· 2026년 10월 28일Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.코딩 에이전트에이전트 엔지니어링AI cost & performance+2
슬라이드 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