- title
- claude-os — A Multi-AI Operating System
Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
A multi-AI operating system. Session protocols, vault architecture, and workflow frameworks built in public.
Built by @AunySillyMe
Claude has Projects. It has memory. It has custom instructions. Most people set those up once and still get generic output.
The problem isn't the tools. It's the architecture.
This is a documented framework for running Claude — and a coordinated stack of AI tools — as an actual operating system. Every session starts with context. Every tool has a defined role. Every workflow has a documented output.
A routing system that loads domain-specific context before every session. Content work loads different files than novel work. Novel work loads different files than music or business. Claude reads what's relevant. Nothing else.
1. IDENTIFY → what domain is this?
2. READ → load only the files for that domain
3. CHECK → pull relevant project tasks
4. WORK → execute
5. UPDATE → mark completed tasks immediately
6. SAVE → write new context to vault if anything changed
Obsidian connected to Claude via MCP. One source of truth. Every Claude tool reads from the same database. No re-explaining. No starting from zero.
What lives in the vault:
Claude, ChatGPT, Grok, and Gemini each have a defined role. No tool does everything. Every tool does what it does best.
A named persona scoped to a specific operational role. Not a personality prompt. A defined collaborator with a job description, behavioral rules, and a reading list it completes before every session.
session-protocol/
vault-architecture/
persona-framework/
multi-ai-stack/
workflow-builds/
Files are added as they're documented. Everything here has been run in production — not theoretical.
MCP (Model Context Protocol) lets Claude read and write to external tools directly — no copy-paste, no switching tabs.
Everything here is documented as it runs.
If this is useful, hit ⭐ — it helps others find it.
Built in public. Documented as it runs. 🕷️
MIT. use it, fork it, build on it.
You are free to:
You must:
You cannot:
If you use this system or build upon it, attribution is appreciated but not required:
Built with claude-os by @AunySillyMe (https://github.com/aunysillyme-dev/claude-os)
A multi-AI operating system. Session protocols, vault architecture, and workflow frameworks built in public.
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Claude Os runs locally over stdio.
Last checked 2026-10-28. A multi-AI operating system. Session protocols, vault architecture, and workflow frameworks built in public.