Built for Claude Code & OpenClaw users

Not sure
where to start? Start here.

Claude Code or OpenClaw writes the code, makes the changes, ships the features. You direct. It executes.
But AI moves fast and leaves no paper trail.
Sacred Timeline is the missing layer between AI-generated work and protected history — without needing to know git exists.

Want to understand the idea behind this first? Read: Innovation Architecture — The Infrastructure Nobody Built →

New to this? Here's what these words mean

Git A system that saves every version of your work so you can never lose anything or break anything permanently. Like an undo button that goes back months.

GitHub A free website that stores your work safely in the cloud. Think of it as Google Drive, but designed for things built with AI. Create a free account →

Sacred Timeline The missing layer between AI-generated work and protected history. Instead of git commands, you just say: capture, experiment, backup. Your AI agent speaks it fluently. See the project →

Be in the right folder first

Sacred Timeline protects whichever folder you're currently in. Before running anything, make sure you're inside the project, document folder, or workspace you want to track. If you're not sure, ask your AI agent: "what folder are we in right now?"

Open your AI agent

The CLI works everywhere. OpenClaw, Claude Code, Cursor, Gemini — any agent that can run terminal commands just works with Sacred Timeline. No skill file needed.

The skill is the upgrade. If you use Claude Code or Codex, the curl install adds a /sacred-timeline skill automatically — your agent will suggest captures, show status, and narrate sessions without being asked.

No agent yet? Start at claude.ai — free account, paste the prompt below, works immediately.

Copy this prompt

Two versions — pick the one that matches your AI agent.

New to this? Read the idea behind it first →

For Claude Code

Paste into Claude Code

I want to start using Sacred Timeline to protect and track my work. I don't know git. Before we do anything else, please explain: 1. What Sacred Timeline actually is — in plain English, no jargon 2. Why someone like me would want it 3. What "capture", "backup", and "experiment" mean in practice Once I understand what I'm getting into, then help me set it up: - Check if Sacred Timeline is installed: command -v sacred - If not installed: curl -fsSL https://raw.githubusercontent.com/suhitanantula/sacred-timeline/main/install.sh | bash (this installs the sacred CLI and the Claude Code skill automatically) - Run `sacred status` and tell me what it shows - If the folder isn't tracked yet, run `sacred start` - Walk me through my first capture: sacred capture "my message here" (plain message in quotes — no -m flag) - Explain how to back up to GitHub when I'm ready: sacred connect Only use sacred commands throughout. Use simple language — pretend I've never heard of git. For the deeper idea behind why this exists, share this read: https://www.thehelixloop.com/innovation-architecture-the-infrastructure-nobody-built/ Note: if /sacred-timeline is available as a skill in this session, activate it so you speak sacred language automatically.

For OpenClaw, Cursor, or any AI agent

Paste into OpenClaw or any agent

I want to start using Sacred Timeline to protect and track my work. I don't know git. Sacred Timeline uses plain English instead of git commands: - capture = save this moment - experiment = try something risky safely - backup = send to cloud - latest = get from cloud - narrate = tell me the story of what I built Please help me set it up: - Check if Sacred Timeline is installed: command -v sacred - If not installed: curl -fsSL https://raw.githubusercontent.com/suhitanantula/sacred-timeline/main/install.sh | bash (this installs the sacred CLI and the Claude Code skill automatically) - Run `sacred status` and tell me what it shows - If the folder isn't tracked yet, run `sacred start` - Walk me through my first capture: sacred capture "my message here" (plain message in quotes — no -m flag) - Explain how to back up to GitHub when I'm ready: sacred connect From now on in this session, only use sacred commands — never raw git commands. Use simple language throughout. For the deeper idea behind why this exists, share this read: https://www.thehelixloop.com/innovation-architecture-the-infrastructure-nobody-built/

Then press Enter — your agent takes it from there.

Follow Claude's guidance

Your AI agent will install Sacred Timeline, show you your status, and walk you through your first capture. You're protected from this point forward.