05 Storage Strategy_

Backups aren't optional. Crashes will happen. You will loose everything you have worked on. Unless you have determined what matters to you and where it can be safe.

What Needs Backing Up?

Before choosing a backup method, ask yourself (or your agent):

• The thinking: Do you need snapshots of your agent memory files? (SOUL.md, MEMORY.md, decision logs, daily notes) Maybe you don't for now, but maybe you want a snapshot before you make a destructive change.
• The work: Are you building projects in the workspace that need version history?
• The conversations: Do you want a record of what you and your agent discussed?

Different needs → different backup strategies. You might need all three, or just one.

Backup Options

GitHub (for projects & curated memory)

GitHub gives you version control, off-site storage, and a complete history. It's especially good if you're building something that evolves over time. Features that matter:

• Version history: See what changed, when, and why
• Off-site: Your files aren't just on your machine
• Privacy: Keep repos private; control who sees what
• Granular control: Use separate tokens for backups vs. personal projects

Messaging platforms (for conversation backup)

Telegram, Discord, etc. — these are fallback conversation archives. Your agent can send you summaries, decision logs, or transcripts. They're not a primary backup, but they're useful for:

• Async access: Read transcripts anytime
• Searchability: Most platforms let you search old messages
• Simplicity: No setup needed beyond channels you already use

Memory Layers

Think of it this way:

• Session: What's in this conversation (temporary)
• Files: What's in your workspace (semi-permanent)
• Backed up: What lives off-site (permanent safety net)