Take something down
Deleting an app or a project, what goes with it, and how to get your files out first.
Ask for it
delete the old landing page from agenthost
Your agent finds it, tears it down and removes its data. The address stops answering immediately.
What goes with what
| You delete | What goes |
|---|---|
| An app | The app, its files, its environment variables, its invitation list, its address |
| A project | Every app inside it, and everything in the table above for each |
There is no undo
Deleting is permanent. There's no bin, no retention window and no restore tool. If you're deleting a project, ask what's in it first — "what apps are in that project?" — because it takes all of them.
Get your files out first
Your files are yours, and the copy your agent sent is the one that's running. If your project only exists on agenthost — you built it in a chat and never saved it locally — ask before you delete:
save the files for that app into ./recovered before deleting it
Getting into the habit of keeping projects in git makes this a non-question, and also gives you the rollback that agenthost doesn't have.
Cleaning up a pile
list all my agenthost apps with what they are and when I last deployed them
Then delete in batches. Your agent can go through them one at a time and tell you what each was, so you're not deciding from a name you chose in a hurry six months ago.
Stopping without deleting
There is no pause. An app is either deployed or deleted — you can't park one for a while and bring it back through the MCP. If you want something off the internet but not gone, either make it invite-only with nobody on the list, or delete it and keep the files to deploy again later.
Taking down just the access
To stop people opening something without removing the app itself, make it invite-only and revoke the invitations, or remove individual addresses. See Make something private.
Tools: delete_app, delete_project.