Show HN: MindFlock – Parallel AI coding agents, each in its own Git worktree

Uh oh!

There was an error while loading. Please reload this page.

Notifications You must be signed in to change notification settings

Fork 0

Star 4

BranchesTags

Open more actions menu

Folders and files

NameName

Last commit message

Last commit date

Latest commit

History

23 Commits

23 Commits

.github

.github

backend

backend

docs

docs

electron

electron

frontend

frontend

scripts

scripts

tests

tests

.gitattributes

.gitattributes

.gitignore

.gitignore

.gitnexusignore

.gitnexusignore

.gitnexusrc

.gitnexusrc

.pre-commit-config.yaml

.pre-commit-config.yaml

.secrets.baseline

.secrets.baseline

AGENTS.md

AGENTS.md

CHANGELOG.md

CHANGELOG.md

CONTRIBUTING.md

CONTRIBUTING.md

LICENSE

LICENSE

NOTICE

NOTICE

README.md

README.md

SECURITY.md

SECURITY.md

TRADEMARKS.md

TRADEMARKS.md

TROUBLESHOOTING.md

TROUBLESHOOTING.md

config.toml.example

config.toml.example

install.sh

install.sh

pyproject.toml

pyproject.toml

uv.lock

uv.lock

Repository files navigation

Run a flock of AI coding agents — each in its own git worktree and tmux session — supervised from one desktop app.

What is it? • How is this different? • Quick Start • Download • How It Works • Documentation

Four agents · four git worktrees, side by side — one working, one waiting for your input, one running commit hooks, one reviewed with checks green.

Why

Staring at a terminal waiting for an AI agent to finish is mind-numbingly boring — so you run several at once, and then you have six terminal windows and no idea which one needs you. MindFlock exists to answer one question at a glance: which agent needs me right now?

What is MindFlock?

MindFlock turns one repository into a fleet of parallel, isolated AI coding sessions. Each session is a git worktree (or clone) plus a tmux session running the coding-agent CLI of your choice — any agent, declared in a TOML file — surfaced in the desktop app as a live terminal with a guided commit → push → PR → merge workflow. An optional ingestion pipeline can watch your issue tracker (Shortcut, Jira, Linear, GitHub Issues, Asana) and reviewed pull requests, and spin up a ready-to-work session for each — automatically.

How is this different?

Parallel-agent orchestrators are a crowded category, and several of them are good. Here's an honest read on where MindFlock actually differs.

MindFlock Claude Squad Conductor Claude Code Agent Teams

Interface Cross-platform desktop app + phone UI Terminal TUI Native macOS app Built into the CLI

Platforms Linux, macOS, Windows (WSL2) macOS, Linux macOS only Anywhere Claude Code runs

Agent CLIs Any — declared in a TOML file Several, bundled (Claude Code, Codex, Gemini, aider, OpenCode) Claude Code, Codex, Cursor, OpenCode Claude only

Session isolation git worktree + tmux git worktree + tmux git worktree git worktree

Git workflow one-click commit → push → PR → merge (gh) commit + push branch per-task diff + review manual (agent runs git)

Agent-state detection deterministic — provider-defined hooks (working / idle / needs-input) inferred from the tmux pane built-in, per supported agent Claude-native

Ticket → session ingestion Shortcut · Jira · Linear · GitHub Issues · Asana — — —

PR-review → session ingestion reviewed PRs become sessions — — —

Remote / phone control tailnet + QR, full action bar — — —

Comparison as of July 2026; these tools move fast. If a cell is out of date, please open an issue or PR and we'll correct it.

MindFlock is a ground-up parallel-agent workspace. A few things set it apart:

Provider-agnostic by design. A coding agent in MindFlock is just a TOML file — binary, launch args, prompt seeding, activity-detection hooks, model pricing — so it drives any CLI (Claude Code, Codex, Gemini, aider, OpenCode, or one nobody's heard of) with the same working / idle / needs-input detection and token + cost tracking. Adding an agent is a config change, not a patch.

Work comes to the agents. MindFlock can turn tickets and code review into sessions on its own: it watches your issue tracker (Shortcut, Jira, Linear, GitHub Issues, Asana) for work assigned to you, and GitHub for PRs that came back with review comments, then provisions a worktree and launches a seeded agent for each — nothing typed.

The whole git loop is guided. Every session carries a one-click commit → push → PR → merge action bar (via gh) and live workflow-stage badges, so you drive the change home without leaving the app.

Supervise from anywhere. mindflock serve tailscale prints a QR code; the mobile UI carries the same guided action bar, so you can unblock an agent from your phone.

When another tool may fit better:

Conductor is a native macOS (SwiftUI) app — if you're Mac-only and specifically want a native client, it's a solid pick.

Claude Code's built-in Agent Teams + worktrees are free and already installed. If you only ever use Claude and live in the terminal, you may not need a separate app.

Claude Squad is a mature multi-agent TUI that also drives several CLIs. If you'd rather stay in the terminal than run a desktop app, it's the closer fit.

Features

🎫 Ticket & PR-review ingestion — watches your issue tracker (Shortcut, Jira, Linear, GitHub Issues, Asana) for assigned work and GitHub for reviewed PRs, then provisions a workspace and launches a seeded agent session for each.

🔌 Provider-agnostic — every coding-agent CLI is just a TOML file (Claude Code, Codex, Gemini, aider, OpenCode bundled; add your own). Shared hook-based activity detection (working / idle / needs-input) and token & cost tracking apply to all of them.

🖥️ Desktop app (Electron) — a draggable terminal grid with Agent / Terminal / Diff / Queue tabs per session, workflow-stage badges, and guided next-step buttons, in a window that follows each OS's own chrome conventions (native traffic lights on macOS, frameless with our own – □ ✕ elsewhere).

📱 Phone UI — mindflock serve tailscale prints a QR code; the mobile UI at /m carries the same guided git action bar, so the full flow drives from a phone. Auth-token protected — never open to the LAN unauthenticated.

🌳 Isolated workspaces — every session gets its own git worktree, so agents never step on each other (or on you).

🔀 Guided git workflow — one-click commit → push → PR → merge, driven by the gh CLI.

⚡ Terminal-first, too — the mindflock CLI drives the same sessions as the app (new, ls, attach, rm, open, events), so terminal and UI stay one system.

🧩 Extensible — shell hooks on every session event, a WS /api/events stream, and in-process Python + ES-module addons.

Quick Start

Install first — one command — then, from zero to a supervised agent session (this CLI flow is verified in CI on every push by scripts/quickstart-verify.sh):

mindflock doctor # 1. everything installed + authenticated? cd ~/code/your-repo # 2. the repo you want the agents to work on mindflock serve # 3. start the server (the app can also do this for you) mindflock new . -p "fix the failing tests" # 4. (new terminal) spawn a session mindflock ls # 5. watch it: TITLE REPO STATUS ACTIVITY STAGE DIFF COST

Open the MindFlock desktop app — the session is a live terminal; each one is an isolated git worktree, with Diff view and guided commit → push → PR → merge buttons. mindflock attach drops your terminal into the same tmux session.

mindflock serve binds localhost only; run mindflock serve tailscale to opt into phone/tailnet access — an auth token + QR code are printed, and scanning the QR opens the phone UI at /m.

Download

Each button downloads the newest release · all versions, checksums, and the Python wheel

What you get Anything else?

Windows MindFlock-Setup.exe — the app and the engine (which runs inside WSL2). Set up WSL2 first — see the note below. With a working WSL2 distro in place, the installer does the rest.

macOS MindFlock.dmg (universal — Apple silicon & Intel). Drag to Applications. Nothing. First launch offers Install the engine — one click, no terminal.

Linux MindFlock.AppImage. chmod +x it and run. Same — first launch installs the engine for you.

The app auto-starts the engine every time after that — no terminal, no manual steps. If the engine is missing, the app's waiting page says so and shows the exact command.

⚠️ Windows: finish setting up WSL2 before you run the installer

The engine runs inside WSL2, so a Linux distribution must be fully installed and launchable first — not just wsl --install half-run. In PowerShell:

wsl --install # if WSL isn't set up yet — then REBOOT your PC wsl -l -v # verify a distro (e.g. Ubuntu) is listed wsl # verify this drops you into a Linux shell (first run asks you to create a user), then type: exit

Only once wsl opens a Linux shell should you run MindFlock-Setup.exe. A partially set-up WSL — installed but with no distro, or with a reboot still pending — is the single most common Windows install failure.

These builds aren't from a paid developer account — what you'll see on first launch

MindFlock has no Apple Developer ID or Windows Authenticode certificate (both are paid, per-year subscriptions). The macOS build is signed, but with a free self-signed certificate — enough to keep macOS from re-asking for folder permission on every launch, not enough to satisfy Gatekeeper. So on first launch:

macOS — "Apple could not verify MindFlock is free of malware."

That dialog has no Open button, and the old Control-click → Open shortcut was removed in macOS Sequoia. To open it anyway (you only do this once):

Drag MindFlock into your Applications folder and try to open it. The warning appears — click Done to dismiss it.

Open the menu → System Settings… → Privacy & Security.

Scroll down to the Security section. You'll see a line like "MindFlock was blocked to protect your Mac." with an Open Anyway button next to it. Click it.

Confirm with Open Anyway again and authenticate with Touch ID or your password. MindFlock launches, and macOS remembers the choice — you won't be asked again.

Prefer the terminal? This does the same thing in one line:

xattr -dr com.apple.quarantine /Applications/MindFlock.app

The first time MindFlock reads a folder under Documents, Desktop, Downloads, or an external drive, macOS asks "MindFlock would like to access files…" — click Allow. Because the app is signed, that grant sticks; it won't ask again for that folder.

Windows — SmartScreen's "Windows protected your PC". Click More info → Run anyway.

Linux — no prompt; AppImages aren't signed by convention.

Every release ships a .sha256 beside each installer (and SHA256SUMS for the Python artifacts), and the builds are produced in public by the Release workflow straight from the tag — so you can check both the bytes and what produced them.

Installation

Most people want the download buttons above. This section is the same thing spelled out, plus every other way in.

Two pieces: the server/CLI (runs the engine) and the desktop app (the one client, Electron — electron/README.md). On Windows the .exe installs both; elsewhere it's two commands.

1. Server + CLI

On Linux, macOS, or inside WSL on Windows (the Windows installer runs this for you, inside your default distro):

curl -LsSf https://raw.githubusercontent.com/MindFlock/MindFlock/main/install.sh | sh

No repo clone, no Python setup needed — the installer brings uv (no root), installs the mindflock command, and finishes with mindflock doctor so anything still missing (git, tmux, claude) is listed with the exact install command for your platform.

Note on curl | sh: it isn't a blind one — the uv installer it fetches is version-pinned and sha256-verified before it runs, and the requested branch/tag is resolved to a full commit SHA that is printed and pinned for the install, an audit trail for what actually ran. Threat model and d

[truncated for AI cost control]