Claude Code Backup
dberuben/claude-code-backup
Backup & restore seguro para Claude Code, sem dependências
Ver no GitHubFerramenta de backup e restore segura e multiplataforma para Claude Code, capturando configurações globais, projetos, histórico de conversas e MCP em um arquivo compactado. Funciona com bash puro, sem dependências externas, e oferece controle total dos dados sem envio para a nuvem.
Instalação
npx convez-ai dberuben/claude-code-backup1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Preservar configurações e histórico do Claude Code antes de trocar de máquina
- Manter snapshot de projetos, skills e agents customizados
- Migrar ambiente completo entre diferentes computadores
Veredito

Solução prática e minimalista para quem depende de Claude Code em múltiplas máquinas. O design sem dependências externas é um ponto forte, mas o escopo restrito (CLI + bash) limita a adoção em fluxos corporativos complexos.
README
A tradução para o português deste README ainda está na fila.
claude-code-backup
Safe, cross-platform backup & restore for Claude Code.
It snapshots your global and per-project config — settings, MCP, slash commands,
agents, hooks, skills, and conversation history — into a single .tar.gz you
control, and restores it on the same or a new machine.
- Pure
bash+tar/gzip— nojq, Python, Node or Homebrew. - macOS & Linux (works under macOS's system bash 3.2).
- No network, no uploads, no telemetry. Works even without Claude Code installed.
Install
git clone https://github.com/dberuben/claude-code-backup.git
cd claude-code-backup
./install.sh # → ~/.local (use --prefix to change)
Make sure ~/.local/bin is on your PATH, then check your setup:
claude-backup doctor
Use
claude-backup # back up → ~/Backups/claude-code
claude-backup --dry-run # preview only, writes nothing
claude-backup list # list existing backups
claude-restore # restore the latest backup (asks first)
Handy flags: --no-history (skip the large projects/ history), --full
(everything), --no-project, --dest <dir>, --strict-secrets, --json.
Full reference: claude-backup --help.
By default a backup includes your config and conversation history, but prunes big regenerable data (plugin code, caches, venvs). Plugin code is not stored — the install manifests are, so you know what to reinstall.
New machine
git clone https://github.com/dberuben/claude-code-backup.git
cd claude-code-backup && ./install.sh
claude-restore
Restore validates the archive, shows a plan, asks to confirm, and takes a pre-restore backup first. Some credentials (Keychain / OAuth / env vars) may need re-login afterwards. Details: docs/restore-safety.md.
Claude Code plugin (optional)
/plugin marketplace add https://github.com/dberuben/claude-code-backup
/plugin install claude-code-backup@claude-code-backup
Adds /backup, /restore, /backup-status, /backup-doctor. It's a thin
layer over the CLI — the CLI works fine on its own. See docs/plugin.md.
Security
Backups can contain secrets (tokens, API keys, MCP auth, private instructions).
Never commit them to git (the repo ignores *.tar.gz) and store them
encrypted. A heuristic scanner warns about likely secrets; --strict-secrets
turns the warning into a hard stop. Full guidance: SECURITY.md.
Status banner (optional)
claude-backup-banner # compact project / backup status line
Configure via ~/.claude-backup/banner.conf — see docs/banner.md.
More
Architecture · Restore safety · Banner · Plugin · Contributing · Changelog
License
MIT © claude-code-backup contributors.