Ten agents. One will.

The command deck for your coding agents: Claude Code, OpenCode, Codex, and Grok in one workspace, sharing one memory.

Download for Mac Apple Silicon See how it works

Free and open source. Apache-2.0.

2 agents working

Workspaces3

atlas

2 branches · 2p · 2 working

api-refactor

@feat/rate-limit·3p

storefront

@main·2p

Agents2

Ozzy

Fix the flaky pty_resize_race testopus

Jax

Add backpressure to the pty readersonnet

Graph11

Shared agent memory · this machine

3 decisions1 attempts7 files

decision Use Zustand for auth state Jax · just now

1⌘1

@main3↑2 2 branches atlas

Claude Code v2.1.205
Fable 5
Claude Max
~/git/atlas

▸▸ bypass permissions on · shift+tab to cycle

Claude Code v2.1.205
Fable 5
Claude Max
~/git/atlas

› add backpressure to the pty reader so a fast agent can't flood the UI

● Editing crates/pty/src/reader.rs

+ bounded mpsc channel (cap 8192)

running 18 tests … 18 passed

▸▸ bypass permissions on · shift+tab to cycle

Git

Agents2

main checkoutmain 3↑2

Ozzyatlas-ozzy 2↑1

Jaxatlas-jax 1↑1

main↑26diff

Changed

Mlib.rscrates/flock-pty/srcdiff ›

Aresize.rscrates/flock-pty/testsdiff ›

Mqueue.rscrates/flock-core/srcdiff ›

MTerminal.tsxapps/flock-desktop/src/componentsdiff ›

Mexport.rscrates/flock-cli/srcdiff ›

MCargo.tomldiff ›

Recent commits

Release 1.4.0main

Sliding-window rate limiter

Merge branch 'pty-backpressure'

Coalesce resize burstsperf

Guard winsize ioctl with io mutexfix

Pull Requests2

#412

Bound the pty reader with a 64k window@ozzy

review

#411

Add a resize race regression test@jax

review

Fig. 01 · Three repos, one window. The sidebar says what every agent is doing right now

Why flock

You used to be limited by who you could hire. Now you are limited by how many agents you can direct.

Every founder knows the 2am rewrite: the thing you did yourself because hiring for it would have cost a quarter. That ceiling is gone. The new one is how much of a formation one person can hold. You direct the work. The formation builds it. Read the manifesto

01 Collaboration

Multiplayer formation.

Fig. 02 · Two hands, one pane. A friend watches from the margin

Every other tool for running agents assumes you are alone at the keyboard. Flock assumes you are not.

ObserveTheir real terminal in your workspace, live and read-only.
DelegateYour prompt becomes their agent’s next instruction.
Co-driveTwo pilots, panes streaming both ways.

All three free, like the rest of the app. Details in the docs.

02 The Graph

Agents that remember.

Before writing a line, an agent reads the graph: what was decided, what failed, who owns which file. No agent starts from zero.

You explained your architecture to an agent this week. With the graph, you did it for the last time. Try the real one below, or read the Graph docs.

The ontologyDecision, Attempt, Note, Interface, File.
Ground firstRead before writing.
Ask it anythingFull-text and meaning together, computed locally.
YoursPostgres in Docker, on your machine.

THE GRAPH

Graph Explorer

The shared memory your agents write as they work. Click a node.

drag to pan · pinch to zoom · click a node

The interactive graph needs JavaScript. The same shared memory ships in the app: decisions, attempts, and file claims your agents read before they write.

03 The workspace

One window. Your whole formation.

Multi-agent panes without the tmux tax. Spawn as many agents as the work demands and keep every one in view.

PanesTile as many as you like. Resize, zoom, pop out.
RunwaysA worktree per agent. Every agent lands clean.
TelemetryA live one-line label of what every agent is doing.

Details in the docs.

Fig. 03 · Three agents, one glance

04 PR review

Pull requests, open to merged.

flock watches the repos you name. A pull request opens, an agent reviews it, and the queue lands it. You preside.

WatchNew pull requests surface the moment they open.
ReviewA fresh worktree, the full diff, grounded in the graph.
You presideAccept, override, or judge the judge.
Merge queueApproved work lands in order, one at a time.

Details in the docs.

Fig. 04 · The judge, judged

05 Features

Standard equipment.

The Cage

Agents at full throttle, in a cage.

One toggle runs every agent in a container that sees your repo and nothing else. No keys, no credentials, no host files. Details in the docs.

Voice

Your voice never leaves the machine.

Hold right option and talk. Words land in the focused pane, transcribed on your own hardware. Works offline. Details in the docs.

Also in the app

Usage, pop-outs, keyboard.

Live usage across your agent CLIs, any pane popped out to its own window, and a shortcut for every move you make all day.

Boutique, on purpose

Small team. Sharp edges filed off.

Independent, built in Luxembourg, local-first, on open standards. The roadmap is shaped in the open, on Discord, release by release.

Free and open source

Free to run. Open to read.

flock is free, and the source is open under the Apache-2.0 license. Sign in with Google, bring your own model keys, and the whole app is yours: no tiers, no caps, no card. Read the code, file an issue, send a patch. Contributions are welcome.

View the source on GitHub Apache-2.0

The flock

A formation of twenty-five geese has about seventy percent more range than a goose flying alone.

Lissaman and Shollenberger, Science, 1970

That is where the name comes from. One agent on its own is a goose alone: it burns fuel working out what the last one already knew. Several in formation, reading one graph and sharing one workspace, get further than any of them manages by itself.

The same paper found that the lead bird does not hold the hardest position. The saving is shared down the whole V. In flock you fly point, and the formation carries the work.

The output of a team, from a single chair.

You used to hire for this. Download flock and put a formation of agents to work.

Download for Mac Apple Silicon · macOS 12+

Free and open source · v0.7.43 · macOS 12+ · Apple Silicon