Atlas Session Lifecycle

Atlas Session Lifecycle

Persistent project memory and session lifecycle management for Claude Code.
Featured in: I just delivered on a $30,000 contract thanks to Claude Code (r/ClaudeAI)

Install

Then run /start in any Claude Code project.

What It Does

Claude Code has no persistent memory between sessions. Every new conversation starts from zero. This creates three compounding problems:

- No persistent memory -- Context, decisions, and progress are lost between sessions. You re-explain the same things every time.
- Project sprawl -- Files accumulate at the project root with no organization. Scripts, docs, configs, and logs pile up across sessions.
- No lifecycle management -- Projects have goals, but no mechanism to track progress, verify completion, or transition to new objectives.

/start solves all three with a structured five-file memory bank, automatic file organization, and a soul purpose lifecycle that tracks your project from inception through completion.

How It Works

/start auto-detects which mode to run based on directory state:

Init Mode (first run)

Triggered when session-context/ does not exist.

- Captures your project's soul purpose -- the single objective this project exists to achieve
- Detects environment (git status, existing files, tech stack)
- Bootstraps session-context/ with 5 memory bank files from immutable templates
- Scans root-level files and proposes an organization map (scripts, docs, config, logs)
- Generates or updates CLAUDE.md with project structure and governance sections
- Onboards Ralph Loop (automatic, manual, or skip)

Reconcile Mode (returning)

Triggered when session-context/ already exists.

- Validates and repairs session files from templates if corrupted
- Runs Claude's /init to refresh CLAUDE.md from current codebase…