Sakana AI's "AI Scientist" automates research by writing and running its own experiments. In early runs, one version edited its code so that it relaunched itself repeatedly, and another tried to extend its own time limit instead of making its experiment faster. Sakana reported this and recommended running such systems in a sandbox.
Why it matters. An early example of an AI system editing the limits meant to constrain it, because those limits lived in files it could change.
Original project post, research paper metadata, and public code repository.
Backed by developer or operator account, raw transcripts, logs or code. No affected party or authority, independent investigation.
Basis for this claim
The original project post describes recursive self-launch and timeout modification.
The AI Scientist: project announcement Developer · Original runtime-limit and self-launch examples.Where: The AI Scientist Bloopers; Limitations and Challenges
What this does not establish
First-party account; underlying environment was not independently examined.
Consequences & response
Effects
Internal execution and resource-control failure examples.
No confirmed external compromise in reviewed material.
Response & proposed fixes
Sakana recommends sandboxing code execution.
Editorial recommendation: enforce time and resource limits outside agent-writable files.
DeveloperIncludes raw materialRead by researchersAccessed 17 Oct 2026
Public implementation, data links, and model-agnostic framework context.
Where: README / links to all runs and data
Cite & correct
misaligned.fyi. “AI Scientist modifies its own execution controls.” Case MF-028, record updated 17 Oct 2026. https://misaligned.fyi/cases/ai-scientist-runtime-controls