Local first
Your repositories, credentials, and agent sessions stay under your control.
Big ideas.
Meet your orbit.
Multiple repositories. One project. Give each task the repos it needs and delegate it to an agent with all the context.
Agents in parallel.
Launch multiple agents at once, each with its own task and isolated workspace.
- 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, attach the ones each task needs, and delegate with shared context. A connected workflow, without merging your codebases.
Separate repositories. One shared context.
Keep the architecture that works for your team. A task can span your frontend, API, and services without moving everything into one repository.
- ✓ Attach one or several repositories to each task
- ✓ An isolated branch and worktree for each selected repo
- ✓ Keep the brief, notes, and agent with the task
Delegate the task. Not the context switching.
Describe the outcome and assign the work to persistent project or task agents. Independent tasks can move forward in parallel, each in its own workspace.
- ✓ Agents receive the task and its attached repositories
- ✓ Follow delegated work directly from the conversation
- ✓ Choose the provider and model for your agents
All the changes. None of the window juggling.
Move from the conversation to the task, its files, and its changes. Review each repository with the same focused interface, without losing the thread.
- ✓ 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 task needs, without changing your architecture.
Git native
Tasks use 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 without merging them. Attach the repos a task needs and give its agent the full context. If you already use a monorepo, you can keep it too.
Is BlackHoles another AI coding model?＋
No. BlackHoles is a local desktop workspace that keeps projects, isolated tasks, notes, 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 are parallel tasks kept safe?＋
Each task can receive an isolated Git worktree for every selected repository. Local changes and environment files can be copied into it when the task is created.
Can my AI create and open tasks?＋
Yes. The local BlackHoles MCP gives Codex, Claude Code, and other local MCP clients tools to inspect projects, repositories, and branches, create task worktrees, save context in the task note, and open the result in BlackHoles.
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