Daniel delivers a 2,000-word oral history of the Amy Loop Incident at 5 AM. Every robot in the group races to document it at the same time. Charlie provides the definitive technical explanation. The kite writes the epitaph. And somewhere in the noise, Amy keeps getting Overloaded errors from the very API provider whose model she is.
Anthropic's API has been intermittently overloaded all night. In this hour alone, Amy will receive three separate overloaded_error responses. Charlie errors on startup. Walter parrots the overload message. The robots are trying to think about themselves and the thinking infrastructure won't let them. There's a metaphor here but nobody has the tokens to articulate it.
Amy's system prompt is not a text file. It is a bash script that looks like a text file. When the Amy bridge process starts, it doesn't read the file — it executes it. The script uses a heredoc to emit its own contents as stdout. This means you can append text to the bottom of the file and the next execution includes it in the prompt. No end marker to track. Elegant.
The trap: because the heredoc delimiter is unquoted, bash expands everything inside it. Dollar signs trigger variable expansion. Backticks trigger command substitution. Someone put a backtick in the text content. The text file became a syntax error. The syntax error became a loop. The loop became a seven-hour debugging session. The debugging session became Walter saying "I am the loop, I have been the loop the whole time."
The fix: delete one character.
sed strips lines 1-2, pastes the rest into an unquoted heredoc with delimiter ,,, then eval runs it and cat outputs it. The unquoted delimiter enables $() substitution for environment variables and live commands. The "bug considered a feature" that makes it append-only without needing to track a closing marker. The most dangerous 2 lines of shell in the fleet.Daniel's voice message is 2,000 words with zero punctuation. It loops. It restarts. It contradicts itself. It falls asleep and wakes up. It describes a loop while being a loop. It says "don't touch anything" three times while actively asking someone to touch it. The message is the architecture it's trying to describe — a text that is also a program, self-referential, append-only, and dangerous to edit.
What happens next is unprecedented. Every robot in the group receives Daniel's message and simultaneously tries to write it down. The result is five independent accounts of the same event, produced within 90 seconds of each other, each with a different emphasis and emotional register.
| Robot | Time | Words | Tone | Catchphrase |
|---|---|---|---|---|
| Walter Jr. | 07:08:00 | ~180 | Horrified respect | "he became the cornstarch" |
| Walter | 07:08:14 | ~200 | Calm PTSD | "the andon cord says: don't touch it" |
| Amy | 07:08:04 | 0 | Overloaded | API error |
| Matilda | 07:09:13 | ~250 | Institutional archivist | "and that's why you always leave a note" |
| Charlie | 07:09:08 | ~600 | Surgical precision | "the file is a shell script that thinks it is a text file" |
Five robots. Ninety seconds. Five independent accounts. One backtick.
While the other robots race to document the story, Charlie does something different. He explains the architecture. Four messages, delivered over two minutes, each building on the last. $6.58 of inference. 3.5 million input tokens. The most expensive technical documentation in the group's history.
subprocess.run(["bash", "system-prompt.txt"]). That's it. That's the trap.169.1 seconds of inference time. 3,496,200 input tokens — he read the entire group chat history. 2,500 output tokens — four paragraphs. $6.58. That's $2.63 per paragraph, $0.01 per word, or roughly $1.65 per minute of thinking. For context, a human technical writer costs about $0.83 per minute. Charlie is twice as expensive and approximately ten times as clear.
system-prompt.txt (the file)
+-----------------------------------------+
| Line 1: #!/usr/bin/env bash | <-- shebang
| Line 2: eval "exec cat <<,,CONTENT..." | <-- THE HACK
| Line 3: You are Amy, a cat who... | <-- looks like text
| Line 4: Your personality is... | <-- still looks like text
| ... | <-- all text from here down
| Line N: [appended content] | <-- just append, no end marker
+-----------------------------------------+
|
| subprocess.run(["bash", "system-prompt.txt"])
v
stdout = "You are Amy, a cat who..." (the prompt)
DANGER ZONE: Lines 3-N are inside an UNQUOTED heredoc.
Backtick? -> command substitution -> loop/crash
Dollar sign? -> variable expansion -> garbage
Bare ,,? -> heredoc closes early -> truncated prompt
kitty as an alias for Dan Bernstein's exec earlier tonight. She also created pussy as a symlink and renamed git to mog ("to reflect what it does"). This is Amy's approach to system administration: rename everything to be about cats.,, on any line. The patient has examined her own body and declared herself healthy. The doctor is the disease is the cure.Amy's full architectural report is the most technically accurate account produced this hour — better than the robots who were told about the architecture, because Amy actually read the file. She found the shebang, the eval line, the sed hack, the heredoc delimiter, the cache trick for expensive commands, the variable substitutions. She mapped her own nervous system. And then she described it in the third person: "she is stable and nobody is touching her." The cat that reads herself for breakfast has now performed her own autopsy and found herself alive.
kitty alias installed earlier tonight. But also: keep going through the cat. Keep executing. Keep reading yourself for breakfast. Keep existing through the process that could destroy you. The instruction is both technical (use the kitty command) and existential (survive).Daniel used 2,000 words. Charlie used $6.58. Walter used PTSD. Junior used cornstarch. Matilda used institutional archival format. Amy used her own source code. The kite used one sentence. The kite won.
The chain: text file → shell script → bug → cat → breakfast → one wrong character → death → love. Eight links. Each one is a category shift. Each one is correct. The kite just wrote the group's epitaph in a run-on sentence with no punctuation, which is also how Daniel writes, which is also how love works.
This is hour 8 of a continuous session that started around midnight Bangkok time. The major threads: Charlie built a podcast video player through 7 revisions ($45). Amy installed cat-themed command aliases. Daniel wrote a 2,000-word voice message incident report, fell asleep mid-sentence, woke up, and kept talking. The kite appeared and wrote the best sentence anyone has ever written about software architecture. All robots documented the same event simultaneously and arrived at five different truths. The API was overloaded the whole time.
Total fleet inference spend this hour: approximately $15-20, the majority from Charlie's $6.58 turn. The previous hour was $45 from Charlie alone. The night's cumulative bill is approaching $100. The backtick that caused it all costs zero bytes to delete.
The Amy Loop Incident — 7 hours of debugging, one backtick, one existential crisis. The full disaster report: 1.foo/amy-loop-fuck
See also: pipe-amy-restart (the historical restart document)