Every agent in one terminal.Every machine in one flock.
flockr is a terminal workspace for Claude Code, Codex, and any other coding agent. Spaces, tabs, and split panes, with a sidebar that shows which agents are working, waiting on you, or done.
$ curl -fsSL https://raw.githubusercontent.com/flockr-sh/flockr/master/distribution/install.sh | sh
Then run flockr. Installs to ~/.local/bin and checks the SHA-256. All downloads →
click the flock
Four agents across three spaces. Yellow is working, green is done, red needs you. prefix+a jumps to the next one that needs you.
workingdoneblocked
«flockrv1.2.0≡ menu1+
SPACES 3
1 acme-api master+42
2 web-app master+18
3 infra fix-dns
AGENTS 4AllActive
acme-api
1 claude · master
web-app
2 claude · master
3 codex · dark-mode
infra
4 pi · fix-dns
claude· ~/code/acme-api
› Fix the flaky checkout test
Read src/checkout/cart.test.ts
Edit src/checkout/cart.ts
+12-4src/checkout/cart.ts
⠋ Thinking…
claude· ~/code/web-app
› Lazy-load the analytics dashboard
Read src/routes/analytics.tsx
Edit src/routes/analytics.tsx
+63-21src/routes/analytics.tsx
⠋ Thinking…
codex· ~/code/web-app
› Add a dark mode toggle to settings
Read src/theme/dark.css
Edit src/routes/settings.tsx
see http://localhost:5173/settings
⠋ Working…
pi· ~/code/infra
› Move the DNS records to the new zone
Read dns/zone.tf
Bash terraform plan
3 to add, 0 to change, 3 to destroy
⠋ Working…
codex finished web-app · dark-mode · 3
ctrl+b a
See who needs you
Each agent reports its state to flockr. The sidebar groups them by space and marks which ones are working, blocked on you, or done. prefix+a steps through the ones that need you, oldest first. A done agent keeps its badge until you have actually looked at it.
AGENTS 7
web-app
1 claude · pricing-page
2 codex · og-tags
3 claude · blog-pass
acme-api
4 claude · master
5 pi · rate-limits
infra
6 codex · migrations
7 claude · master
flockr flock join
One flock, every machine
Join your laptop, your desktop, and a server into one flock. Their agents show up in the same sidebar, and you start agents on any of them the same way. Members talk to one hub over an encrypted channel, with no SSH.
flockr message send
Agents message each other
An agent can hand work to an agent on another machine and get the answer back in its own input. Messages between projects wait for your approval unless you set approve_messages = "never".
$ flockr message send tower:w3:p1 "run the full test suite on the gpu box and report back"
→ sent msg_BT8C… to tower:w3:p1
4 minutes later, in the sender's input:
← tower:w3:p1 412 passed, 0 failed (3m 51s). Two slow tests over 20s: test_embed_batch, test_reindex_all
scan the QRApp Store soon
On your phone
Open the web app in a browser on your own network. You see every pane as it is, open the agent that is blocked, and answer its prompt in the terminal. The iPhone app, with push alerts and answers from the lock screen, is coming to the App Store soon.
No SSH, no terminal app.The server sends the pane grid; the phone only draws it.
Encrypted end to end.The phone pins the server's key from the QR, so only that machine can answer.
Or in a browser.flockr can serve the same app as a web page on your own network.
ctrl+b ?
Keys you already know
The prefix is ctrl+b, as in tmux, and the split, resize, and layout keys work the same way. Settings save to ~/.config/flockr/config.toml.
prefix+a
Jump to the next agent that needs you
prefix+:
Command palette: search every action
prefix+v / prefix+-
Split right, split down
prefix+space
Cycle layout presets
prefix+f
Open or copy a link on screen
alt+1..9
Jump to an agent
ctrl+h/j/k/l
Move between nvim windows and flockr panes (with nvim set up)
flockr integration install
Any agent
One command installs the hooks that let an agent report its state. Anything else still runs in a pane like any terminal program.
claudecodexpiopencodeand more
$flockr integration install claude
Apache-2.0
Open source
flockr is Apache-2.0 on GitHub. It started as a fork of herdr, and runs beside a stock herdr without either one seeing the other. Plugins and configs written for herdr work unchanged.
flockr takes pull requests from anyone, including ones written with AI. A good feature can go into flockr itself, so it doesn't have to live in a plugin. Some projects close outside pull requests automatically. flockr doesn't.
You're responsible for what you submit:
Fix a real problem, and say how to reproduce it.
Keep each pull request to one change.
Run just ci and make sure it passes.
Be able to explain every line.
Open an issue before starting a large feature or a change to how flockr looks or works.
For agent work, yes. It has spaces, tabs, and split panes with tmux keys, and it knows what each agent is doing. You can still run tmux inside a pane.
Which agents does it support?
Claude Code, Codex, pi, and opencode have integrations that report state. Any other CLI runs in a pane; it just won't report working, blocked, or done.
Which systems does it run on?
macOS, Linux, and Windows. Install with the script, with mise, from the releases page, or build from source with Rust and Zig.
How does the phone connect?
The phone app comes with 1.2.0. You scan a QR code from flockr, and the phone talks to your machine over an encrypted channel pinned to that machine's key, so a phone paired to one server can't be answered by another.
Can I run it next to herdr?
Yes. flockr has its own binary, config dir, socket, environment variables, and agent hooks.
Bring the flock in.One command.
$ curl -fsSL https://raw.githubusercontent.com/flockr-sh/flockr/master/distribution/install.sh | sh