# How I Accidentally "Killed" an AI Coding Agent With a Totally Normal Prompt > Source: > Published: 2026-08-14 21:43:31+00:00 How do you terminate an LLM *inside its own session* — without `/exit` , a stop button, or any command at all? I stumbled into an answer by accident while messing around with an AI coding agent. And the funniest part: **I never asked it to stop.** Hit the Stop button. Type `/exit` . Or send a prompt so massive it blows past the context limit and the request just... can't continue. None of that is interesting. The first two are just built-in commands. The third isn't "termination," it's a technical wall. So I wondered: could a completely ordinary prompt make an agent unable to continue? Turns out: yes. I told the agent, casually: "Rename the root directory to NewName." It did. Perfectly. Task complete. And then the chat input just... died. Grayed out. Nothing. I was like: *The only thing stopping me from you is you.* The model wasn't gone. It was just sitting there, waiting for input I could no longer give it. ``` /project/AHWWIW/ → /project/NewName/ ``` The rename worked fine. The problem: the IDE and agent session were still pointing at the old path, `/project/AHWWIW/` , which no longer existed. The workspace had vanished out from under its own session — no error, no crash, just a silently orphaned session with nowhere left to send messages. No — let's be honest about that. The model's running fine on a server somewhere; deleting a folder on my laptop does nothing to it. What I broke was the *execution environment*: ``` LLM → Agent → IDE/tools → Workspace → Filesystem ``` The LLM was untouched. The session was toast. But from where I was sitting? Conversation over. Via a completely normal prompt. A regular chatbot just gives you text back. An agent can actually reach out and touch its own environment — create files, delete them, run commands, rename directories. Which means it can occasionally do something totally reasonable that quietly demolishes the ground it's standing on. Rename directory → old path vanishes → session still expects it → input disabled. The agent did exactly what I asked. It just also, completely by accident, made it impossible to talk to it again. Not really — no prompt reaches down into a server rack and pulls a plug. But you *can* nuke an agent's session by asking it to modify something the session quietly depends on. I wasn't even trying. I just wanted to rename a folder.