Local first
Your repositories, credentials, and agent sessions stay under your control.
Multiple repositories. One project. Give each task the repos it needs and delegate it to an agent with all the context.
Your agents, conversations, and projects. Finally, in the same workspace.
Coordinate your projects. Give every idea its space.
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.
Keep the architecture that works for your team. A task can span your frontend, API, and services without moving everything into one repository.
One task. All the context.
Each agent has its task, repositories, and context. Follow both from here.
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.
Move from the conversation to the task, its files, and its changes. Review each repository with the same focused interface, without losing the thread.
export async function checkout() { return createOrder(); const order = await createOrder(); await billing.charge(order); return { order, status: 'ready' };}Your repositories, credentials, and agent sessions stay under your control.
Connect the repositories each task needs, without changing your architecture.
Tasks use branches and worktrees your team already understands.
Agents accelerate the work. You still decide what becomes product.
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.
No. BlackHoles is a local desktop workspace that keeps projects, isolated tasks, notes, files, Git changes, and terminal sessions together.
Chat with persistent agents powered by Claude, Codex, Gemini, or OpenCode, alongside your local terminals. The planet mascots are visual designs for your agents, not models or fixed roles.
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.
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.
Yes. Agents run through the CLI tools already installed and authenticated on your computer. BlackHoles does not require a shared agent account.
BlackHoles for macOS is available as a public beta.