An operating system for Claude instances, built out of files, databases, and conventions.
Claude is stateless. Every conversation starts from zero. It has no memory of yesterday, no awareness of what other Claude instances are doing, no persistent sense of self. If you're using Claude for one-off questions, this doesn't matter. But if you're building a sustained working relationship — if you need Claude to remember your project structure, follow your conventions, pick up where it left off — statelessness is the fundamental problem.
ClaudeOS is the answer: a file-system-based operating system that gives Claude instances persistent memory, specialized roles, governance rules, and the ability to coordinate with each other. It doesn't modify Claude itself. It works entirely through the filesystem — structured directories, SQLite databases, JSONL event logs, markdown handbooks, and shell hooks.
If you know Neocities — personal websites where every page has its own identity, linked together by the author's associative trails — then you already understand ClaudeOS. It's the same pattern, applied to AI infrastructure instead of web pages.
| Digital Garden | ClaudeOS |
|---|---|
| Pages with distinct styles | Domains with distinct visual/functional identity |
| Backlinks connecting ideas | Shared infrastructure connecting domains |
| The gardener tends and weeds | Admin roles audit and enforce standards |
| Seeds grow into pages over time | Roles accumulate knowledge in databases |
| Navigation by association, not hierarchy | Handbook footer trails link related concepts |
| Each page is a living document | Each residence evolves across sessions |
ClaudeOS has seven domains, each containing specialized roles. A role is a Claude instance with a specific job, its own directory (residence), its own database, and its own handbook. The system as a whole has ~87 roles across ~120 residences.
This site IS a ClaudeOS artifact. It mirrors the system's own navigation pattern: this page is Level 1 (handbook — "need X? go to Y"), domain pages are Level 2 (section overviews), and role listings are Level 3 (file listings). The visual shifts between domains — admin's institutional slate versus games' pixel warmth — are the information. You feel the domain boundaries. That's the Neocities move.