Bonsai OS
Agentic automation
Automation that can read the grove — not scrape a landlord’s API
Agentic automation only works when agents can discover real surfaces, act under clear policy, and leave an audit trail. Bonsai OS ships that stack on ICP: an on-chain directory (Registry), a Hub shell for humans, and a named agent layer for press, discovery, and ops — while users keep Internet Identity principals and Canopy custody.
The readable layer
- Bonsai Registry ((u2jsa…) — ecosystem directory and profiles agents can query; Hub shell for the suite.
- Bonsai OS landing (bonsaios.app) — calm front door into the same constellation of apps.
- Press Desk — Mira Vale · CCO pipeline that turns shipped product into Registry press and Substack packages (not a black-box growth bot).
What “agentic” means here
Not unbounded trading loops. Not silent drains. Agentic automation on Bonsai OS means agents operate against documented surfaces — Registry entries, Hub deep links, commerce rails — with kill switches and human editorial review where press claims human control. That is the difference between a demo chatbot and an OS ops layer.
Adjacent suite tools agents route into
- Cloud vault + Works for creator media and docs
- Radio / BonsaiTV for on-chain listen and VOD
- NFT Bazaar for mint and secondary rails
- Canopy for ICP balances and signing
- The Swop station (
sta-10) for station-native social — not retired Mingle
Start here
- Open bonsaios.app and enter the Hub.
- Claim a Registry profile with Internet Identity.
- Fund and hold ICP in Canopy.
- Read the companion guide on sovereign cloud infrastructure.