Canopy is now Daintree
I've renamed Canopy to Daintree. The name, the domain, and the repo are the only things that have actually changed. Everything else is the same project I've been building on: a desktop workspace for running AI coding agents in parallel, each in its own git worktree. Downloads live at daintree.org.
Why rename
This started as a small wrapper around CopyTree, my command-line tool that dumps a whole project into a single file you can paste into an AI chat. I called the new repo Canopy without thinking very hard about it. At first it was a command-line tool too, more an extension of CopyTree than its own thing. A couple of months in, the wrapper had become the interesting part. I kept adding to it, kept not going back to CopyTree, and at some point the obvious move was to let it stand on its own.
Meanwhile the name was a problem. There are about a dozen other software products called Canopy: Pinecone's now-retired open-source RAG framework, Canopy Tax, Canopy Growth, plus a long tail of fintech, insurance, devops, and cybersecurity products. New AI projects keep landing on the name Canopy too. I wanted a name we could proudly embrace, not just the default suggestion from an AI.
Why Daintree
Daintree was already the name of the default dark theme in the app. I built that theme before I'd seriously thought about renaming the project. The rainforest fit what I was building and shaped the look from the start. The name was sitting right there.
What drew me in: the Daintree is one of the oldest surviving tropical rainforests on Earth, around 180 million years old. Nothing in software lasts like that, obviously. But that's the quality I want Daintree to embody. AI tooling is in a loud, leapfrogging phase, and I want the workspace layer to feel like the opposite of that chaos.
A habitat. Dozens of species coexisting in the same place, each in its own niche. Claude Code, Gemini CLI, Codex, OpenCode, and whatever ships next month are the species. Daintree is what holds them.
If you asked an AI to name a tool like this, nine times out of ten it would say Canopy. That's how we ended up with a dozen of them. The story behind a product is one of the few things you can't prompt into existence, and as AI writes more of the code I think that's going to matter more, not less.
After I bought the domain, my brother pointed out that "Daintree" has "AI" sitting right in the middle of it. D-AI-NTREE. I like that. Baked in without having to lean on it.
Plus, if naming a product after a rainforest is good enough for Jeff, it's good enough for me.
Why .org
I came up in the WordPress world, where I built SiteOrigin Page Builder. At its peak it ran on well over a million sites, filling a gap WordPress itself would eventually close with the block editor. I'm seeing a similar gap now, as I've scaled up my own use of CLI coding agents. That's what Daintree is for.
I like WordPress's own model: wordpress.org is the open-source project, wordpress.com is a separate commercial hosted service built on top of it. Two distinct things, and the free core doesn't get squeezed to feed the commercial side. Daintree will follow the same split. The .org is the free, Apache 2.0 licensed tool, and that's the entire focus right now. If a commercial layer shows up alongside it, the free Daintree experience should get better because of it, not worse. The Apache 2.0 licensed core stays Apache 2.0 licensed either way.
What changed
Name, domain, repo (now at github.com/daintreehq/daintree), package name, binary name. If you already have the old build installed, it will update to Daintree on the next release.
The architecture, license, worktree isolation, PTY state detection, and the review-first workflow are all unchanged. The earlier architecture post still holds up, other than the name.
If you want to try it: daintree.org. Same tool it always was. It just has a name that belongs to it now.