Real AI agent use cases, with sources and setup prompts

Undo anything your coding agent did, even rm -rf

Claude Code's rewind does not track shell commands, so if an agent deletes your src folder and .env file, nothing comes back. Oops records what the agent does so you can undo it, including deleted files.

$17/mo10 minutesBeginnerSource linked

Source

@theturukx on X · 2026-10-18

Written in our own words. Credit to the original author. Link checked 2026-10-18.

What they did

Claude Code's rewind does not track shell commands, so if an agent deletes your src folder and .env file, nothing comes back. Oops records what the agent does so you can undo it, including deleted files.

Result (as claimed)

Shared by the builder.

Tools they used

Cost: Claude Code: from $17/mo.

Set it up

  1. Pick a contained repo or task

    Start on a branch or side project where mistakes are cheap.

  2. Install and configure

    Set up Claude Code. Read what it can run on your machine and limit permissions where possible.

  3. Run it on a real task

    Give it a well-scoped issue and let it work. Review the diff like any pull request.

  4. Add guardrails

    Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.

Copy the full setup prompt

Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.

You are helping me set up this AI use case end to end in Claude Code.

Goal: Undo anything your coding agent did, even rm -rf
What the original author did: Claude Code's rewind does not track shell commands, so if an agent deletes your src folder and .env file, nothing comes back. Oops records what the agent does so you can undo it, including deleted files.
Reported result (as claimed by the author): Shared by the builder.
Source: https://x.com/theturukx/status/2111819308028604434
Tools they used: Claude Code
Category: Dev & ops

Please:
1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like).
2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure.
3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data.
4. Finish with a checklist to run it again next time.

The Daily 5

Get five new use cases tomorrow morning

Free. Real sources. Unsubscribe any time.

Guides for this use case

How to vibe code an app with Claude Code ยท How to undo, checkpoint and stop runaway coding agents

Related use cases