Canopy runs parallel Claude Code sessions as tabs in one native macOS window — each in its own git worktree, each its own Claude. Close the app and every session resumes with its conversation intact. One-click "Merge & Finish" handles the merge-and-cleanup dance, a split shell pane lets you run git without interrupting Claude, and an Activity dashboard shows where your tokens actually went. Native SwiftUI, no Electron. macOS 14+, AGPL-3.0. Built by someone who uses it daily.
Hi everyone 👋
I'm Julien. I built Canopy because I use Claude Code every single day, and two problems kept getting in my way: avoiding parallel task collisions and being comfortable letting an agent run commands on its own.
Canopy solves both with isolation at two levels. Each task runs in its own git worktree — its own branch, its own directory — so parallel Claude sessions never step on each other's files. And each session can run in a sandboxed container, either Docker or Apple's native Container framework, so Claude runs in a contained runtime rather than running loose on your machine. Worktree isolation for your code, container isolation for peace of mind.
On top of that, it's all one native macOS window — each session a tab, Cmd+1–9 to jump between them. Close the app and every session resumes with its conversation intact, no session IDs to hunt down. A few other things that came out of my own daily annoyances:
→ Merge & Finish — replaces the five-command merge-and-cleanup dance with two clicks
→ Split shell pane — run git or tail a log without interrupting Claude
→ Activity dashboard — finally see where your tokens actually went
Native SwiftUI, no Electron, no bundled Node — it launches fast and behaves like a Mac app. Free and open source under AGPL-3.0.
Fair warning: it's macOS-only and built specifically around Claude Code — not a general worktree manager. It's young, so it's been battle-tested mostly against my own workflow. Bug reports and feedback are genuinely welcome — that's a big part of why I'm sharing it here.
Git worktree isolation for parallel sessions is such an obvious idea once you see it, but I've never seen anyone actually build it cleanly like this. The sandboxed container part is what sells me though — letting Claude run commands on its own feels a lot safer when it's contained. Another Windows user wishing this existed for me too.
the hard part of parallel claude code sessions is clobbering each other's git state and working dir. if each session gets a genuinely isolated checkout, that's the whole ballgame — the rest is ui.
Congrats on the launch. The worktree + container split is the part that feels most useful: code isolation and runtime isolation are different problems.
One edge case I’d love to understand: when two Claude sessions touch shared project surfaces like package manifests, migrations, env examples, or generated types, does Merge & Finish detect cross-worktree conflicts before merging, or is the workflow still “merge one, then resolve manually”? That conflict boundary is where parallel agents usually stop feeling parallel.
About Canopy on Product Hunt
“Parallel, sandboxed Claude Code sessions on native macOS”
Canopy launched on Product Hunt on June 16th, 2026 and earned 73 upvotes and 7 comments, placing #32 on the daily leaderboard. Canopy runs parallel Claude Code sessions as tabs in one native macOS window — each in its own git worktree, each its own Claude. Close the app and every session resumes with its conversation intact. One-click "Merge & Finish" handles the merge-and-cleanup dance, a split shell pane lets you run git without interrupting Claude, and an Activity dashboard shows where your tokens actually went. Native SwiftUI, no Electron. macOS 14+, AGPL-3.0. Built by someone who uses it daily.
Canopy was featured in Mac (103.6k followers), Developer Tools (515.4k followers), Artificial Intelligence (473.1k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 213.5k products, making this a competitive space to launch in.
Who hunted Canopy?
Canopy was hunted by Julien Simon. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Canopy stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Julien Simon