Open Source · Local-First · v0.1.4

Git preserves source code.
Ithos preserves institutional memory.

The institutional memory layer for AI-assisted development.
Decisions, lessons, patterns, regressions — captured in markdown,
stored in your repo, owned by you.

npm install -g ithos ithos-mcp

The Problem

Code is generated at 10× velocity.
Human comprehension remains 1×.

AI writes code faster than teams can absorb it. Git records what was built — but the reasoning, rejected alternatives, and hard-won lessons vanish into ephemeral chat windows and scattered threads. Weeks later, even the original author can't explain why.

Core Pillars

Why Ithos?

🔒

Zero-Cloud Dependency

Your memory lives locally inside .ithos/. No external databases, SaaS subscriptions, or internet required.

🌲

Git-Native

Memory files participate in branches, commits, merges, and pull reviews. They move with your code.

📖

Markdown Source of Truth

Frontmatter-enhanced Markdown. Fully readable in VS Code, Cursor, Obsidian, GitHub, or a terminal.

🤖

AI-Assisted, Human-Approved

Your AI assistant drafts memory files via MCP as you code. You review and approve.

Git

records what changed

Commits, diffs, and blame tell you which lines were modified and by whom.

+

Ithos

preserves why it changed

Decisions, tradeoffs, lessons, and rejected alternatives — the reasoning behind the code.

How It Works

Three steps to institutional memory

01

Preserve

Your AI assistant captures decisions, lessons, and session logs via MCP — structured, frontmatter-tagged, and saved to .ithos/.

02

Recall

Search memory with ithos search or let your AI assistant automatically query past decisions when solving a bug or making a change.

03

Understand

Run ithos timeline to see the project's full institutional history unfold chronologically — like watching the project remember itself.

Timeline

Your project's engineering history, at a glance

ithos timeline
$ ithos timeline

2026-07-02

  📌  Decision      Use Prisma over TypeORM
  → Better migrations and developer experience
  → Schema-driven client with strong TypeScript inference
  ↳ .ithos/decisions/use-prisma-over-typeorm.md

────────────────────────────────────────────────────

2026-07-05

  💡  Lesson        Avoid nested transactions
  → Caused connection pool exhaustion under load
  → Use sequential queries with explicit savepoints instead
  ↳ .ithos/lessons/avoid-nested-transactions.md

────────────────────────────────────────────────────

2026-07-08

  ⚠️  Regression    Auth middleware broke guest routes
  → Middleware applied globally instead of per-route
  → Fixed by splitting into authenticated and public pipelines
  ↳ .ithos/regressions/auth-middleware-guest-routes.md

  🧠  Session       Implemented MCP server
  → Created search_memory capability
  → Integrated with Cursor and Claude Desktop
  ↳ .ithos/sessions/implement-mcp-server.md

────────────────────────────────────────────────────

2026-07-13

  📌  Decision      Institutional Memory over Engineering Memory
  → Better captures the organizational, durable nature of the concept
  ↳ .ithos/decisions/institutional-memory-terminology.md

  5 entries across 4 days

Repository Layout

Everything lives inside .ithos/

.ithos/
├── README.md            # Memory overview for AI agents & developers
├── project.md           # Project context, stack, conventions
├── decisions/          # Engineering decisions with tradeoffs
├── architecture/       # Structural changes and ADRs
├── features/           # Feature records and capabilities
├── patterns/           # Reusable patterns and conventions
├── lessons/            # Post-mortems, bug resolutions
├── regressions/        # Regressions and context
├── defects/            # Defect records
├── gaps/               # Known gaps and deferred work
├── releases/           # Release notes and milestones
└── sessions/           # Developer session outcomes

Get Started

Three commands. That's it.

1 Initialize

$ npm install -g ithos
$ ithos init

Creates the .ithos/ structure in your project root.

2 Connect MCP

$ npm install -g ithos-mcp

Add to your AI client config and restart your editor.

{
  "mcpServers": {
    "ithos": {
      "command": "ithos-mcp"
    }
  }
}

3 Read the Timeline

$ ithos timeline

Watch the project's institutional memory unfold.

CLI Reference

Commands

CommandDescription
ithos initInitialize the .ithos/ directory
ithos validateVerify repository structure matches the spec
ithos doctorInspect local setup and diagnose issues
ithos recordRecord a decision, lesson, session, or other artifact
ithos search <query>Search across all institutional memory
ithos exportExport the full memory directory to stdout
ithos timelineChronological timeline of all institutional memory

Architecture

Layered monorepo

              ┌──────────────┐
              │  Future App  │
              └──────┬───────┘
                     │
    ┌─────────────┐  │  ┌──────────────┐
    │  Ithos CLI  │  │  │  MCP Server  │
    └──────┬──────┘  │  └──────┬───────┘
           │         ▼         │
           │   ┌───────────┐   │
           └──►│   Core    │◄──┘
               └─────┬─────┘
                     │
                     ▼
              ┌─────────────┐
              │  Local FS   │
              └─────────────┘

ithos-core

Domain logic: init, validate, record, search, export, timeline. Every consumer reuses this — zero duplication.

ithos

Thin CLI. Renders core output with colors and icons. Contains no business logic.

ithos-mcp

MCP stdio server. AI assistants call it to query and record memory in real-time.

Principles

01

Memory First

Everything exists to preserve institutional memory.

02

Local First

No internet, no cloud. Your data lives in your repo.

03

Markdown Source of Truth

Indexes and databases are secondary and always derived.

04

Git Native

Merges and PR reviews are the synchronization mechanism.

05

AI Captures, Humans Understand

AI handles the grunt work. Developers own the knowledge.