Backup & Restore¶

Protect your Echo Agent data with regular backups.

What to Back Up¶

Data	Location	Priority
Configuration	`~/.echo-agent/config.yaml`	High
SQLite database	`~/.echo-agent/data/echo_agent.db`	High
Memory store	`~/.echo-agent/data/memory/`	High
Knowledge base	`~/.echo-agent/data/knowledge/`	Medium
Skills (user)	`~/.echo-agent/skills/`	Medium
Checkpoints	`~/.echo-agent/data/checkpoints/`	Low
Logs	`~/.echo-agent/data/logs/`	Low

Backup Procedure¶

# Stop the service first for consistency
echo-agent gateway stop

# Create backup
BACKUP_DIR="echo-agent-backup-$(date +%Y%m%d)"
mkdir -p "$BACKUP_DIR"
cp -r ~/.echo-agent/config.yaml "$BACKUP_DIR/"
cp -r ~/.echo-agent/data/ "$BACKUP_DIR/"
cp -r ~/.echo-agent/skills/ "$BACKUP_DIR/"

# Restart
echo-agent gateway start

Warning

Always stop the Gateway before backing up SQLite databases to avoid corruption.

Restore¶

echo-agent gateway stop
cp -r "$BACKUP_DIR/data/" ~/.echo-agent/
cp "$BACKUP_DIR/config.yaml" ~/.echo-agent/
echo-agent gateway start

Checkpoint System¶

Echo Agent provides built-in file checkpoints:

echo-agent checkpoint list
echo-agent checkpoint show <id>
echo-agent checkpoint restore <id>

Checkpoints track file-level changes made by the agent and allow targeted rollback.

What checkpoints do not cover

A checkpoint is a shadow Git snapshot of workspace files. Its exclusion list covers the SQLite database, the sessions directory, the memory directory and the logs directory — a file-level snapshot of a live SQLite file would be a torn read — so none of that data is captured.

checkpoint restore therefore does not restore sessions or memory. Recover those from a SQLite backup as described below.