Skip to main content

Super Memory

Persistent shared knowledge layer for AI coding agents.

AI coding agents (Claude Code, Cursor, Aider) suffer from session amnesia. Every new session starts cold — rediscovering architecture, re-exploring codebases, repeating mistakes. Super Memory fixes this with a .memory/ directory that any agent can read and write.

How It Works

A .memory/ directory in your repo holds structured markdown files with YAML frontmatter:

  • systems/ — Architecture docs for each subsystem (committed)
  • decisions/ — Architectural Decision Records (committed)
  • gotchas/ — Known pitfalls and bug patterns (committed)
  • research/ — Investigation findings (committed)
  • people/ — Per-person context and ownership (committed)
  • sessions/ — Session summaries (gitignored)
  • scratch/ — Working memory during sessions (gitignored)

Agents read these on session start (warmup), write discoveries during work, and commit knowledge at session end (cooldown).

Quick Start

# Install
pip install atlas-memory

# Initialize in your project
cd your-project
atlasmemory init

# Set your identity
atlasmemory whoami yourname

# Auto-discover codebase systems
atlasmemory systems discover

# Start coding with your AI agent — it reads .memory/ automatically

Non-Interactive Init

atlasmemory init \
  --project "my-project" \
  --me mitch \
  --platform claude-code \
  --tracker beads \
  --obsidian \
  --auto-discover

CLI Commands

atlasmemory init                              # Initialize .memory/
atlasmemory whoami [name]                     # Get/set identity
atlasmemory systems                           # List system docs
atlasmemory systems discover                  # Auto-discover modules
atlasmemory systems stale                     # Show stale docs
atlasmemory query --system auth               # Query by system tag
atlasmemory query --concern race-condition    # Query by concern tag
atlasmemory summary                           # Regenerate SUMMARY.md
atlasmemory health                            # Check memory health
atlasmemory check-conflict path/to/file.py    # Check DO NOT TOUCH claims

Agent Platforms

Super Memory integrates with:

Platform What init Does
Claude Code (--platform claude-code) Appends protocol to CLAUDE.md
Cursor (--platform cursor) Appends protocol to .cursorrules
Aider (--platform aider) Generates .aider.conf.yml

Obsidian Integration

Pass --obsidian to atlasmemory init to generate Obsidian vault config. Then open .memory/ as an Obsidian vault for graph view, tag filtering, backlinks, and Dataview queries.

Issue Tracker Integration

Super Memory complements (doesn't replace) issue trackers. Use --tracker with: beads, linear, github, or jira to enable backlink fields in templates.

Team Usage

  1. Each team member runs atlasmemory whoami theirname
  2. Memory files are committed to git and shared
  3. Person files track who's working on what (agents check "DO NOT TOUCH" sections)
  4. Sessions and scratch stay local (gitignored)

License

MIT

Metadata

Release files for atlas-memory 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for atlas-memory 0.1.1
File Size Uploaded
atlas_memory-0.1.1.tar.gz 35.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for atlas-memory 0.1.1
File Interpreter ABI Platform
atlas_memory-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 57.3 kB

Release files / atlas_memory-0.1.1.tar.gz

Download URL atlas_memory-0.1.1.tar.gz
Size 35.3 kB
Tags Source
SHA-256 checksum
How to use checksums
9a77964e91300d4cf426b1abc617f96a3d6f56f40994fa63864e43e038ce3063
BLAKE2b-256 checksum
How to use checksums
3bdece083b720120f8d7eab59997a0c639f64f6a52496eb1ea60f29753c4ae98
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 7, 2026.

Transparency log

Release files / atlas_memory-0.1.1-py3-none-any.whl

Download URL atlas_memory-0.1.1-py3-none-any.whl
Size 22.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
62daa314afffd999e37510efd480783274b219da6fdcc2a847db51fe507dcc18
BLAKE2b-256 checksum
How to use checksums
e821b2705b42b1309ebe1bc90a532a399b1c18028f89ce6a503b383794ae131c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 7, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page