# CLAUDE_CODE_DISABLE_FILE_CHECKPOINTING

> Set to 1, it saves no copies. Then /rewind cannot undo edits.

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** CLAUDE_CODE_DISABLE_FILE_CHECKPOINTING=1

## Think of it like

It is like you turn off undo in a drawing app.

## Definition

CLAUDE_CODE_DISABLE_FILE_CHECKPOINTING set to 1 stops the copies. Claude Code saves a copy of a file before each edit. With this set, it does not. Then /rewind can no longer bring back your code. It wins over the matching setting.

## Example

Emma runs Claude Code in a throwaway container that is wiped after each job. Saving copies there is wasted work, so she sets this.

## Example code

```bash
export CLAUDE_CODE_DISABLE_FILE_CHECKPOINTING=1
claude
```

Skip saving copies before edits.

## Why it matters

Checkpoints use disk and time. Where you never need undo, you can skip them.

## Common mistake

Setting it on your own laptop. A bad edit then has no quick way back but git.

## Three principles

- **No checkpoints.** Before edits.
- **No /rewind for code.** When set.
- **Wins over the setting.** fileCheckpointingEnabled.

## Related terms

- [Claude Code Checkpoint](https://learn.benibix.com/term/ai/claude-code-checkpoint)
- [Edit Tool](https://learn.benibix.com/term/ai/edit-tool)

---

Source: https://learn.benibix.com/term/ai/claude-code-disable-file-checkpointing-variable
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-16
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
