Massive files being created in /tmp directory

Status Fixed / completed
Maintainer reply ✓ Yes — wolffiex
Activity 8 comments · opened Feb 27, 2025 · closed Apr 11, 2025
💡 Likely answer: A maintainer (wolffiex, collaborator) responded on this thread — see the highlighted reply below.

I started claude code in a simple hello world zig project, and asked it to extend it into a text adventure game. After creating the game (which it did flawlessly), it tried to play it, and appeared to get stuck in the game loop. This resulted in 68GB claude-af8a-stdout file being created in my /tmp directory.

Apologies if this is a duplicate, and was easily fixed by deleting the file, but felt it was worth a bug report

View original on GitHub ↗

8 Comments

danbri · 1 year ago

FWIW https://x.com/TetraspaceWest/status/1894873248644600153

claude code created a 1.7 TB file in my tmp folder comprising entirely of the stdout of it being unable to play a text based game it made
scbenet · 1 year ago
FWIW https://x.com/TetraspaceWest/status/1894873248644600153 > claude code created a 1.7 TB file in my tmp folder comprising entirely of the stdout of it being unable to play a text based game it made

Interesting, I'm sure the file mine created would've been bigger but 68GB was just all the available disk space on this machine

wolffiex collaborator · 1 year ago

Thanks for this report. We'll cut off commands that generate over 1MB of stdout or stderr. Fix should be in the ext version.

wolffiex collaborator · 1 year ago

Saw this in prod today. If you are still having issues after 0.2.27 please reopen

!Image

mhpenta · 1 year ago

Today experienced a 313GB stdout file. The issue may have been reintroduced.

amaruy · 1 year ago

Same here.
Version: 0.2.66 (Claude Code)
-rw-rw-r-- 1 ubuntu ubuntu 54G Apr 10 08:26 /tmp/claude-bae3-stdout

$tail -f /tmp/claude-bae3-stdout
   |   |

Player 1, enter row (0-2) and column (0-2) to place your symbol >>>
 - |   |
---|---|---
   |   |
---|---|---
   |   |
wolffiex collaborator · 1 year ago

ok this should be fixed in v0.2.69

github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.