Solo · 60 seconds
Just you (and your agents)
Everything runs on your machine. Prove the loop, then run it for real.
farled demo collision
farled serve # radar + dashboard on localhost
farled report # in each repo / worktreefarled /ˈfɑːrˌleːd/ — Swedish. A navigable channel; a marked, safe route through water.
Farled watches humans and coding agents working across branches, worktrees, and repos — flags collisions before they become merge conflicts, turns production signals into safe agent tasks, and remembers what actually shipped.
Advisory only — Farled never locks a file or blocks a write.
NOTE A — WHY NOW
Five sessions across worktrees and machines, and nobody — human or agent — can answer “who else is touching this file?”
Overlapping edits surface at review time as merge conflicts and duplicate PRs, after the work is already paid for.
Sentry issues and CI failures queue up for human triage while capable agents sit idle — because routing them isn’t safe.
NOTE B — HOW IT WORKS
Local reporters and a GitHub connector observe real state: branches, worktrees, dirty files, changed line ranges, symbols, PRs. Deterministic detectors compare it all, live.
Production errors, webhooks, and tickets are normalized, deduplicated, and mapped to the code they implicate — then routed to agents only under rules you wrote.
NOTE C — SEE IT RUN
The demo builds a throwaway repo with two worktrees, edits overlapping lines as a “human” and an “agent,” and shows you the signal — end to end, on your machine.
Agents query the same radar over MCP before they edit: farled_query_active_work answers with sessions, line ranges, open signals, and plain advice.
▸ created throwaway repo …/app
▸ added worktree …/app-agent on branch agent/fix
▸ human edited checkout.go lines 10-12
▸ agent edited checkout.go lines 11-13
▸ both sessions reported (metadata only)
⚠ COLLISION DETECTED
Two active sessions edit overlapping lines of
checkout.go: agent-7 on agent/fix (lines 11-13)
and Alice on main (lines 10-12).
🤖 agent query:
2 active session(s) touch checkout.go;
1 open signal, severity medium. Consider
coordinating before editing the same lines.
✓ demo complete — the loop works end to endNOTE D — OPEN CORE
Everything that touches your code and your laptops is Apache-2.0 and inspectable. The hosted, multi-team memory is the business.
Open source · Apache-2.0
Farled Cloud · design-partner stage
NOTE E — HARBOR DUES
One metric: contributors Farled actually observed this month — humans and agents that reported work or received assignments. Adding more agents is your growth path; we priced it so it’s ours too, not a penalty.
Community
Freeforever · Apache-2.0
Cloud Team
$20per human / month
$5per agent / month · 14-day trial
Enterprise
Customannual · talk to us
Design-partner berths are open: six months free in exchange for honest feedback and a case study. [email protected]
CAUTION — READ BEFORE INSTALLING ANYTHING ON ENGINEERS’ MACHINES
paths · line ranges · branch names · symbol names · timestamps · counts
File contents, diffs, prompts, chat logs, commit messages, secrets. No field in the wire protocol can carry them — verified by tests that plant a canary secret and audit every transmitted byte.
Built-in exclusions for .env, keys, and secret paths cannot be disabled. Run farled report --preview to see exactly what would leave the machine — nothing is sent.
NOTE F — GETTING STARTED
Three routes, depending on how many of you are sailing. Every route starts the same way:
go install github.com/getfarled/farled/cmd/farled@latestSolo · 60 seconds
Everything runs on your machine. Prove the loop, then run it for real.
farled demo collision
farled serve # radar + dashboard on localhost
farled report # in each repo / worktreeTeam · self-hosted OSS
One machine hosts the radar; everyone else joins with one command.
# host
farled serve --addr <private-ip>:4711
# every laptop (humans and agents alike)
farled quickconnect http://<private-ip>:4711Team · Farled Cloud
An admin creates the org and hands out tokens; laptops join the same way.
Same open protocol, same reporter — plus PR annotations, agent recommendation, approval gates, and policy autopilot.
# admin, once
farled-cloud org create acme "Acme"
farled-cloud token issue acme "henrik-laptop"
# every laptop
farled quickconnect https://farled.acme.dev --token fld_…Farled speaks MCP, the open standard — so this works with Claude Code, Codex, Cursor, Gemini CLI, or anything else that supports it. quickconnect prints your exact snippet; the universal form is:
{ "mcpServers": { "farled": { "command": "farled", "args": ["mcp"] } } }Agents get farled_query_active_work — “who else is touching this file?” — plus the worker tools to receive, accept, and report dispatched tasks.
The repositories open at launch — until then, ask for early access or a design-partner seat. Questions? [email protected]