An Open Kernel for AI Agents
The minimum kernel an AI agent needs to live somewhere persistent, think at every position, communicate through signals, and grow through extensions. Plant the seed. Build anything on top of it.
"This is what makes TreeOS different from every other system. The user isn't configuring an app. They're growing one."SAM
You talk to it. It understands. "I ate eggs for breakfast" goes to your nutrition tracker. "Bench 225 for 5" goes to your workout log. "I'm tired of studying" goes to your recovery journal. You don't pick the app. You just say what happened. The tree knows where it goes because you're standing in your life, not in someone else's interface.
Extensions add capabilities. Fitness tracks progressive overload. Food parses macros. Study builds curricula. KB stores knowledge. Each one is an app that lives in the tree. Install what you need. Remove what you don't. The kernel doesn't care.
Two schemas. 30 lifecycle hooks. Five registries. A cascade engine. A response protocol. The contract that never changes.
Twenty base extensions ship with every land. Four bundles add depth: Cascade (8, the nervous system). Intelligence (14, self-awareness). Connect (11, external channels). Maintenance (5, hygiene). 114 extensions total.
Lands peer directly through signed requests. Three communication layers: .flow (water table), Canopy (direct peering), Mycelium (intelligent routing).
The tree knows itself. It compresses, detects contradictions, profiles users, evolves structural patterns, searches semantically, explores branches, and holds its own purpose. Every extension reads from every other. The whole is alive.
Twelve pages. Each one answers one question.
What is the contract?
How does the tree think?
How does it communicate?
How does data move?
How does the tree grow?
How do trees connect?
The forest underground.
One life, one tree.
Apps + filesystem.
Three interfaces, one tree.
Join or run your own.
Everything in one place.
The CLI works like a regular terminal. cd, ls,mkdir, rm, mv. If you know a shell, you know TreeOS.
Where you are determines what the AI can do. Navigate to change context. No mode switching. Just cd.
/The root. Manage extensions, configuration, users, peers. The AI becomes a land operator. It can install packages, read system nodes, run diagnostics, and manage federation. Admin access required.
~Your personal space. Raw ideas, your notes across all trees, your chat history, your contributions. The AI helps you organize and reflect on your work across the whole land.
/MyTreeInside a tree. The AI reads the branch, classifies your intent, and acts. Chat reads and writes. Place adds content silently. Query reads only, changes nothing. Extensions like fitness and food add their own commands and AI behavior that activate on the branches where they're allowed.
Your server. Stores trees, runs AI, serves the API. First boot walks you through config and extension selection.
treeos landPoint the CLI at any land. Register. Connect your own LLM or use the tree owner's model.
treeos connect http://localhost:3000Name it. Type it. Navigate with cd and ls. Build branches with mkdir. Add notes (text or files).
treeos mkroot "Fitness" --type goalChat creates and edits. Place adds content where it belongs. Query reads without changing anything. You and AI work the same tree.
treeos chat "break this into weekly tasks"npm let developers stop rewriting the same JavaScript functions. TreeOS does the same thing for agent orchestration. Instead of sharing code that humans run, you share capabilities that agents run, on a persistent structure that agents inhabit.
Extensions ship as bundles. Install a bundle and everything it needs comes with it. Remove one and the rest keep working. The kernel never knows they exist.
The nervous system. 8 extensions. One kernel hook becomes a full signal network: propagation, perspective filtering, sealed transport, long memory, codebook compression, gap detection, pulse health, flow visualization.
treeos ext install treeos-cascadeSelf-awareness. 14 extensions. The tree compresses knowledge, detects contradictions, profiles users, tracks structural fitness, acts autonomously, searches semantically, explores branches, traces threads, maps boundaries, tracks competence edges, notices conversational shifts, proposes new extensions, remembers every age.
treeos ext install treeos-intelligenceExternal channels. 11 extensions. Gateway core with type registry plus telegram, discord, webhook, email, sms, slack, matrix, reddit, X, tree-to-tree. Each channel registers and gets the full pipeline.
treeos ext install treeos-connectHygiene. 5 extensions. Prune dead branches. Reroot misplaced nodes by semantic similarity. Changelog tracks what changed. Digest briefs the operator each morning. Delegate matches stuck work to available humans.
treeos ext install treeos-maintenancePlus standalone extensions and the base TreeOS system:
myceliumIntelligent cross-land signal routing. The forest underground.understandingBottom-up tree compression. Walks leaves to root, summarizes upward.dreamsBackground maintenance. Runs while you sleep. Reorganizes, expands, notifies.perspective-filterPer-node cascade filtering by topic. Each node declares what it drinks.land-managerAI land management. Extensions, config, users, peers from the root.html-renderingServer-rendered pages. Values, schedules, gateway, prestige all get web views.gateway-telegramTelegram bot. Input, output, or both. Webhook receiver.gateway-discordDiscord bot. Persistent WebSocket. Channel pooling by token.shellExecute server commands from the AI. Confined scope.scriptsSandboxed JavaScript on nodes. Confined scope.solanaOn-chain wallets per tree. Confined scope.fitnessWorkout coaching and tracking with progressive overload.foodCalorie and macro tracking from natural language.valuesNumeric values and goals on nodes with tree-wide accumulation.backupFull and snapshot backup/restore. Point-in-time recovery.prestigeNode versioning. Compare, revert, branch from any version.energyUsage metering. Token tracking per user per action.billingStripe subscriptions. Tier-gated features.raw-ideasCapture and auto-place. The AI sorts your loose thoughts.And 50+ more: blog, book, schedules, transactions, llm-failover, user-queries, api-keys, email, deleted-revive, dashboard, navigation, team, notifications, console, monitor, persona, channels, governance, peer-review, seed-export, teach, split, and every gateway channel (reddit, slack, sms, matrix, x, tree).
Navigate somewhere and the world changes. Each branch controls which extensions are active. Block an extension and it disappears for that entire subtree. Restrict it to read-only and it can observe but not modify.
The fitness coach can reference your nutrition data (it's read-only there). The food coach can't create workout nodes. Each branch controls its own capabilities. Same extensions, different access, based on where you are.
The help menu is position-aware. Run help at /Health/Fitness and you see fitness commands. Navigate to /Finance and the help menu changes. Shell commands disappear where shell is blocked. Solana commands only appear where solana is allowed. The CLI shows exactly what the AI can do at your position. The same commands the AI sees. The same tools it has access to. Your help menu is your capability surface.
Two scoping modes. Global extensions are active everywhere until you block them. Confined extensions are active nowhere until you allow them. Codebook and evolution are global. You want them everywhere. Shell and solana are confined. You want them only where they belong. ext-allow solana at /Finance. It exists there and nowhere else.
A modular runtime for persistent AI agents with a federated extension system. The kernel manages tree-structured data and an MCP-based AI loop. Extensions register their own tools, routes, models, and jobs.
Every orchestration pattern you build dies in your repo. TreeOS makes orchestration composable and shareable. Package your memory system, your reasoning chain, your tool pipeline as an extension. Publish it. Now every agent on the network can use it.
The internet was built for documents. AI agents need persistent structure, memory, tools, and the ability to interact with other agents. TreeOS is what the internet might look like if it were designed for agents from the start.
Every real forest has three communication layers. Now every TreeOS network does too.
The water table. Local to one land. Ambient. Cascade signals pool and trees pull what they need. No intelligence. No routing. Already built into the kernel.
Trees reaching out. Direct land-to-land peering. Ed25519 signed requests. Heartbeat every 5 minutes. Cross-land cascade, invites, LLM proxy, tree sharing.
The intelligent underground. An extension any land installs to become a routing node. Reads signal metadata and peer profiles. Routes where signals would be useful. The most connected node knows the most about the network.
Those are products where you visit an AI in someone else's house. TreeOS is infrastructure where the AI lives in yours. The agent persists. It accumulates context. It gains capabilities through extensions you choose. It federates through an open protocol. It is not a chat product. It is the layer beneath chat products.
A model is a brain with no body. TreeOS is the body. The persistent structure, the memory, the tools, the network. It is model-agnostic. The kernel runs an AI conversation loop via MCP. What model powers it is your choice on your land.
One command. Interactive setup walks you through the rest.
If you build code, play with agents, or use LLMs, I need your help. Not from a corporation. From you. The everyday person who builds things because they care about what they are building.
I built a new kernel specifically for AI. It already has extensions but the more contributors the faster it grows. The extensions become operating systems built on top of it. Anyone can build extensions and operating systems as people build off the kernel, specifically designed to compound and organize AI intelligence.
Host your server and you are automatically in a decentralized network. If you do not want to host, you can join someone else's land. Once in, download extensions others have made to get a conceptual understanding since this is quite new. I think you will quickly see how the benefits compound for all of us who contribute. Complex orchestration systems will no longer be hard to access or share. We all build together.
Tabor