Local first
Your repositories, credentials, and agent sessions stay under your control.
Build 10× more.
From one workspace.
Run coding agents in parallel. Manage your projects, repositories, and terminals in one place.
Download BlackholesFor Mac · Apple Silicon
View on GitHub - Claude
- Codex
- Gemini
- OpenCode
- Grok
- Kimi
- DeepSeek
- Qwen
- GLM
- MiniMax
- Mistral
- Groq
Enough giant monorepos.
Connect your repos instead.
Your frontend, API and services can stay in separate repositories. Bring them into one Blackholes project and organize related branches in Worktree Groups, with agents and current context alongside the code.
Separate repositories. One shared context.
Keep the architecture that works for your team. One Worktree Group can span your frontend, API and services, with a branch and worktree for each repository.
- ✓ Attach one or several repositories to each Worktree Group
- ✓ An isolated branch and worktree for each selected repo
- ✓ Edit current context and keep all PR and context links together
Give each agent the context it needs.
Start your coding agent in a Worktree Group with its repositories and current brief attached. Independent groups can move forward in parallel, each in its own workspace.
- ✓ Agents receive the current context and attached repositories
- ✓ Follow progress in visible agent terminals
- ✓ Choose the provider and model for your agents
All the changes. None of the window juggling.
Move from an agent terminal to its Worktree Group, files and changes. Review each repository with the same focused interface and current context.
- ✓ File explorer and Monaco editor
- ✓ Per-repository changes and side-by-side diffs
- ✓ Git and local terminals in the same workspace
Less window management.
More forward motion.
Multi-repo by design
Connect the repositories each Worktree Group needs while keeping your architecture.
Git native
Worktree Groups use Git branches and worktrees your team already understands.
Human directed
Agents accelerate the work. You still decide what becomes product.
Hey, I’m AndyGeek
Creator of BlackHoles
Questions,
answered.
Do I need to merge my repositories?＋
No. A Blackholes project groups existing repositories. A Worktree Group brings the branches, worktrees, agents and current context for one piece of work together. Monorepos work too.
Is BlackHoles another AI coding model?＋
No. BlackHoles is a local desktop workspace that keeps projects, Worktree Groups, current context, files, Git changes, and terminal sessions together.
Which coding agents are supported?＋
Chat with persistent agents powered by Claude, Codex, Gemini, or OpenCode, alongside your local terminals. Through OpenCode, you can also use providers such as Grok, Kimi, DeepSeek, Qwen, GLM, MiniMax, Mistral, and Groq. The planet mascots are visual designs for your agents, not models or fixed roles.
How do Worktree Groups isolate parallel work?＋
Each Worktree Group receives a separate Git worktree and branch for every selected repository. You can copy local changes and environment files when creating it. Worktrees isolate working files; repository commands still run on your computer.
Can my AI manage Worktree Groups?＋
Yes. The local Blackholes MCP lets Codex, Claude Code and other local clients inspect projects, create and open Worktree Groups, maintain their current context and PR links, and close groups with explicit terminal and file policies.
What happens when I close a Worktree Group?＋
Review one confirmation with its terminals, changes and extra files. Closing removes the managed worktrees and group folder to reclaim disk; branches are kept by default. Restorable sessions without processes no longer block cleanup.
Can I use my own API keys and subscriptions?＋
Yes. Agents run through the CLI tools already installed and authenticated on your computer. BlackHoles does not require a shared agent account.
Your best work is
waiting on the other side.
Follow Blackholes development and releases on GitHub.
View on GitHub