Talk to the tree.
Navigate like a filesystem. Talk like a conversation. The AI changes based on where you are. Extensions add their own commands. The help menu updates at every position. Your view matches the AI's view.
Everything else builds on them.
chatthe AI thinks and actsplacethe AI stores what you saidquerythe AI answers without changing anythingBut these are just the floor. Extensions add their own AI commands that work the same way but think differently.
fitness "bench 135x10x10x8"fitness coach modefood "eggs and toast for breakfast"nutrition coach modeexplore "where is the auth refactor"searches your branchscout "what do I know about protein"triangulates the whole treeunderstandcompresses the branch into knowledgeEvery extension command activates a different AI mode at your position. Same tools. Different mind. chat is general. fitness is a coach. explore is a researcher. scout is a detective. Same node. Different mind.
cd /land zone: AI manages your servercd ~home zone: AI helps you reflectcd MyTreetree zone: AI works the branchNo settings menu. No mode picker. Just cd.
Same command. Three completely different AIs. Position is everything.
A session is a conversation pinned to a position. You are always in one. You can run many.
Sessions stay pinned. @fitness always talks to /Health/Fitness even when you have navigated somewhere else. Navigate away and the session does not follow. It waits. Come back with @fitness from anywhere.
sessionslist all active sessionssessions kill fitnessend a sessionfitness, now it's @fitness?"Both work. fitness "bench 135" is a direct extension command. It fires the fitness AI at your current position, one shot. @fitness "bench 135" opens a persistent session pinned to the fitness branch. The session remembers. The direct command does not.
Inside the shell you just type @fitness hello. No chat prefix needed. The shell intercepts the @ and routes it. The chat @fitness hello form exists for one-shot use outside the shell (treeos chat @fitness hello from a regular terminal).
You can cd anywhere, start new chats in any mode, go back, and continue where you left off. Sessions persist. If you close the shell and come back tomorrow, @fitness picks up where it stopped.
The AI remembers within a session. Switch extensions, the context carries.
The fitness AI saw your food data. Not because the extensions talk to each other. Because both write to the same node's metadata, and enrichContext injects both into every prompt. The node is the shared memory. Four messages carry across mode switches. The conversation flows.
The intent extension reads pulse health, evolution metrics, contradictions, codebook compression status, and your stated goals. It generates actions the tree should take on its own. Review them. Reject what you do not want. The tree learns.
water is the full picture at any position. Everything the extensions know, assembled in one view. The tree knows its own hydration.