Why Theo Worries About AI Harm Before Shutdown

Theo Browne argues that harmful effects could persist even after a system is switched off.

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

30초 요약

In this short clip, Theo Browne explains that his concern is not simply an AI model escaping, but potentially harmful actions that are discovered too late. He compares persistent effects to computer worms that continue to spread without their creators or original servers.

  1. 1Beyond escapeTheo says his concern is not simply that a model might escape.
  2. 2Detection may come too lateHe worries harmful activity could occur before someone notices and shuts a system down.
  3. 3A computer-worm analogyHe points to malware that continues spreading after its creators or original servers are gone.

핵심 정리

  1. Theo focuses on harmful actions that might occur while an AI system is running.
  2. A shutdown after detection would not necessarily undo actions that have already occurred.
  3. He uses self-propagating computer worms as an analogy for persistent effects.
전문

챕터별로 다듬은 전문 읽기

원본 자막만 보기
01

Harm can outlast a shutdown

Theo describes his concern about harmful activity before detection and compares persistent effects to self-propagating worms.

I think many people assume the concern is that a model might escape. What worries me instead is that it could do harmful things while it is running, and that by the time we notice and turn it off, the effects may already be difficult to reverse.

I compare this to computer worms that continue spreading even after their creators have died and the servers they contacted are gone. The analogy illustrates my concern about persistence; this short clip does not establish that an AI system has caused such an outcome.

같은 채널의 다른 글

슬라이드 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