lemur-os

LemurOS

A personal, local-first developer OS for managing the full lifecycle of fullstack side projects through Claude Code.

LemurOS is not a project management tool with AI bolted on — it is an opinionated environment where the AI is the workflow. Every phase of building a project, from refining the initial idea to ongoing feature work, is driven by a dedicated Claude Code agent reading from and writing to a shared knowledge base.

Hard test of success: LemurOS must be able to manage its own development. If it can't dogfood itself end to end, it has failed.

The three pillars

1. Claude Code Plugin Suite — Skills, agents, and hooks covering six phases: Interview → PRD → Architecture → Tasks → Development → Testing & Review. A single Librarian agent owns all writes to memory; a Sync skill reconciles drift; an Onboarding skill ingests existing projects.
2. Memory Bank — An Obsidian vault inside the repo, structured as markdown with frontmatter and wikilinks. Per-project metadata, PRD, architecture, tasks, decisions, lessons. Cross-project shared patterns. Queryable via Dataview and natural language through Claude Code.
3. Local Dashboard — An Electron desktop app (Vite + React renderer + Node.js main process). Reads the file system directly via IPC — no HTTP server, no open port. Surfaces a project card grid, per-project kanban, and four action buttons that launch the right Claude Code session in the right folder with full context preloaded.

How it works, end to end

• New project → dashboard scaffolds the folder, runs Interview → PRD → Architecture → Tasks agents in fresh sessions, Librarian writes everything to memory, project appears as a live card with kanban.
• Continue developing → one click opens a Claude Code session rooted in the project with the LemurOS plugin and full memory context auto-loaded. On session close, Librarian commits progress.
• New feature → feature-scoped variant of the new-project flow against an existing project.
• Add existing project → Onboarding agent analyzes the codebase, generates an architecture doc, and links the project.

The file system is the source of truth. The dashboard is a view; it never holds canonical state.

Stack

• TypeScript end to end
• Electron (Vite + React renderer, Node.js main process, typed contextBridge preload)
• Obsidian vault (markdown + frontmatter + wikilinks, Dataview)
• Claude Code as the agent runtime; plugin sourced from this repo via symlink to the global Claude Code plugin dir
• pnpm dev starts the entire stack

Status

8 of 12 phases complete. See docs/progress/README.md for the full phase tracker.

Phase	Status
Phase 0 — Repo Foundation & Shared Schemas	✅ Done
Phase 1 — Memory Bank: Obsidian Vault Skeleton	✅ Done
Phase 2 — Plugin Foundation: Manifest, Hooks, Librarian Core	✅ Done
Phase 3 — Plugin: Process Skills (Superpowers-Derived)	✅ Done
Phase 4 — Plugin: Phase Agents and Phase Skills	✅ Done
Phase 5 — Plugin: Slash Commands and Setup Scripts	✅ Done
Phase 6 — Dashboard Main Process: Foundation, IPC, Watcher, Launcher	✅ Done
Phase 7 — Dashboard Renderer: Theme, Components, Store	✅ Done
Phase 8 — Dashboard Renderer: Views and User Flows	🔴 Not Started
Phase 8.5 — Dashboard: User Guide	🔴 Not Started
Phase 9 — Integration, Pressure-Tests, and System Smoke	🔴 Not Started
Phase 10 — Self-Management Dogfood (MVP Acceptance Demo)	🔴 Not Started

Up next: Phase 8 — Dashboard Renderer: Views and User Flows

Quick start

git clone <repo>
cd LemurOS
pnpm install
pnpm run setup       # links plugin into ~/.claude/plugins/, downloads Obsidian plugins, runs doctor
pnpm run doctor      # diagnostic checks; should print PASS/SKIP, exit 0

Use pnpm run setup / pnpm run doctor (full form) — pnpm has built-in setup and doctor commands that shadow the bare shorthand.

What's been built

Phase 0 established the pnpm monorepo, strict TypeScript base config, shared type contracts (@lemur-os/shared-types), Zod runtime schemas (@lemur-os/plugin-schemas), ESLint/Prettier, Vitest, and GitHub Actions CI.

Phase 1 delivered the Obsidian vault skeleton with Templater templates, Dataview rollup pages, the @lemur-os/dashboard package, four vault reader modules, a scaffold-vault-section CLI, and a full round-trip integration test (64 tests green).