Skip to content

JackBhanded/Claude-Parachute

Repository files navigation

Claude Parachute

Claude Parachute

An undo button for the things Claude Code can't undo.

Build Windows app License: MIT


The problem, in one breath

Claude Code can edit your files for you. It also runs commands for you — and some of those commands delete things, overwrite things, or reset your project.

Claude Code's built-in undo (/rewind) only remembers the file edits. It does not remember the commands. So when a command wipes something out, /rewind can't bring it back. It's just gone.

Claude Parachute is the missing safety net. It quietly saves a copy of your whole project every time Claude does anything — including those commands — so you can always go back. One click and you're rescued.

Think of it like autosave in a video game. Parachute keeps dropping checkpoints as you go, so a bad move is never the end of the world — you just reload the last good one.

What you can do with it

  • Go back in time. Restore your project to any earlier checkpoint with one click. We call it pulling the cord.
  • Never lose work by accident. Every checkpoint is saved automatically in the background while you and Claude work.
  • Undo the undo. Even restoring is reversible — Parachute saves where you were first, so you can't make things worse by pressing the button.
  • Stay calm. A tidy timeline shows every checkpoint, so you always know you have a way back.

It can't lose your work, and it can't make a mess of your project — by design (more on that below).

Get started in 2 minutes

The easy way — no typing. Download Claude Parachute.exe from the latest release and double-click it. You'll get a simple window with your list of checkpoints and a big Pull the cord button. It tucks into your system tray and looks after you from there.

The first time you open it, Windows may show a blue "Windows protected your PC" box. That's normal for small free apps like this one — click More info → Run anyway.

That's it. Open your project, click Snapshot now once to switch it on, and Parachute takes it from there.

The one button that matters: Pull the cord

When something goes wrong, you don't need to understand anything technical. You just:

  1. Open Claude Parachute.
  2. Click the checkpoint you want to go back to.
  3. Press Pull the cord.

Your project snaps back to exactly how it was at that moment. And because Parachute saves your current state first, you can always change your mind and come back. There's no way to make it worse — that's the whole promise.

Prefer typing? There's a command for everything

If you live in a terminal, install it once (no admin needed):

powershell -ExecutionPolicy Bypass -File .\install.ps1

Then, inside any project folder:

Command What it does
parachute init Switch Parachute on for this project.
parachute install-hooks Save a checkpoint automatically after everything Claude does.
parachute snapshot -m "note" Save a checkpoint right now, with a note.
parachute list Show your recent checkpoints (newest first).
parachute restore 3 Pull the cord — go back to checkpoint #3.
parachute undo Quick one-step-back: go to the checkpoint before your last change.
parachute status A quick "is everything switched on?" check.
parachute dashboard Open a nice status page in your browser.
parachute doctor Health check, if something feels off.

To go back, you only ever need two: parachute list to see the numbers, then parachute restore <number> to pull the cord. Both the restore and the quick undo are always reversible.

Is it safe? Yes — that's the point

Parachute is built to be impossible to regret:

  • It can't lose your work. Going back always saves where you are first, so you can undo the undo. And it only brings old files back — it never deletes the new ones you've made since.
  • It keeps to itself. Parachute saves its checkpoints in their own private folder. It doesn't interfere with your project's own version history, and it skips anything your project already tells git to ignore.
  • It can't get in Claude's way. If Parachute ever hiccups, it steps aside silently — it will never interrupt or break what Claude is doing.

What you'll need

  • Windows 10 or 11 for the double-click app.
  • Git installed on your computer — Parachute uses it under the hood to do the saving. If you don't have it, grab it (free) from git-scm.com/download/win and install with all the default options.
  • (For the typed commands only: Python 3.9 or newer.)

How it differs from the alternatives

The starting point is real, not invented: Claude Code's own docs say its /rewind tracks only the files Claude edits with its Write/Edit tools — not the things a command changes — and even suggest you "use git for destructive operations." That's the exact gap Parachute fills. Here's how it compares to the other safety nets out there:

  • Other editors' built-in checkpointsCursor and Windsurf snapshot before each AI edit, but (like /rewind) they don't capture what a terminal command does. If you work in those editors, their built-ins are lovely for undoing edits — just not command side-effects.
  • Cline is the closest cousin: it keeps a separate "shadow" history (not your real git) and saves after each step, commands included. The catch is it's tied to VS Code. Parachute brings that same idea to Claude Code, as a standalone app.
  • Aider auto-commits every change and has /undo — but it commits into your real git history, which not everyone wants. Parachute keeps its checkpoints in their own private spot and never touches your project's git.
  • ccundo is the nearest Claude Code tool, with nice granular, preview-first undo; it aims to cover bash commands too. If you want fine-grained "undo just this one step," it's well worth a look — it's a different flavour from Parachute's whole-project checkpoints.
  • Auto-commit hooks / gitwatch can catch everything (bash included), but they usually commit into your real repo and clutter its history. Parachute deliberately stays out of your git.

The combination Parachute is built around — a private shadow history, made for Claude Code, saving after every step including commands, never touching your real git, and always undoable — is the spot none of the others quite fill. If one of the above fits your setup better, genuinely use it; Parachute is here for the Claude Code user who wants the command side-effects covered too.

Part of the fleet

A little set of friendly tools for people who build with Claude:

  • Claude Meter — see your Claude usage on your taskbar.
  • Claude Lifeboat — back up and restore your Claude data.
  • Claude Lifejacket — keep every chat aware of your projects.
  • Claude Compass — keep every chat tuned to how you like to work.
  • Claude Parachute — you are here. The undo button for what Claude Code can't undo.

About the author

Jack Bhanded

Built by Jack Bhanded, Lead developer and architect at SawYouAtSinai. Devotee of innovative technologies and gadgets. Built this because Claude Code's /rewind kept missing the changes that worried him most — the ones made through the Bash tool — and he wanted a safety net he could trust.

License

MIT — see LICENSE. Free to use, share, and build on.

About

The safety net for when /rewind can't save you. Shadow-git snapshots that catch even the Bash changes Claude Code's rewind misses — with a one-pull, always-undoable restore.

Topics

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Contributors