Keeping versions of a Claude Code project, without learning git

Claude Code is excellent at building and surprisingly casual about keeping. Here's what's actually protected today, and how to close the gap in two minutes.

What Claude Code saves on its own

• Session checkpoints. Claude Code snapshots your files as it works, and you can rewind within a session when an edit goes wrong. Fast, and the first thing to reach for.
• The conversation. Your chat history survives and can be resumed, which sometimes contains earlier versions of files inside Claude's responses.

What it doesn't

• A permanent, browsable history of the whole project. Checkpoints are a working convenience, not an archive.
• Anything off your machine. A dead laptop, a deleted folder, or an overenthusiastic cleanup takes the project and its history together.
• A version another person (or another tool) can see, compare, or restore.

The two-minute fix

Give the project a home that Claude Code itself maintains. Plyo speaks your agent's language directly, so the setup is one command and one sentence:

1. Create a free Plyo account, then copy an AI key (Settings → AI keys).
2. Run this in your terminal:

3. Then tell Claude Code:

From then on every piece of finished work becomes a checkpoint on a timeline (with a plain-English note about what changed and what you asked for) that lives off your machine, survives any session, and restores in one click. Restoring never deletes anything, so even an undo can be undone.

The habit that makes it work

End work with "save this to Plyo" the way you'd end a document with save. Agents are reliable about it once asked; the tool description even reminds them. If you switch to Cursor or any other tool next month, the same home keeps working. That's rather the point.