Farled · traffic control for parallel coding
farled /ˈfɑːrˌleːd/ · Swedish — a navigable channel; a marked, safe route through water.
Your agents ship in parallel. Farled shows when developers and coding agents are changing the same parts of a codebase — and warns the team while there is still time to coordinate.
Humans, Claude, Codex, Cursor, and other tools share the same view. Nothing is locked.
The conflict appears at review, after both tasks are finished. Farled sees the shared code area while both tasks are still in motion.
NOTE A — ONE SIMPLE EXAMPLE
Every task looks independent from inside its own window. Farled supplies the missing team-wide view.
A developer and several agents begin tasks in separate branches and worktrees.
Two tasks begin changing the same checkout code without knowing about each other.
The team sees who is involved, where the overlap is, and how urgent it looks.
One task waits or changes scope. Both can proceed without discovering the problem at review.
NOTE B — WHAT FARLED DOES
01 · SEE
Farled brings active branches, worktrees, pull requests, people, and agents into one current view.
02 · WARN
Deterministic checks flag shared files, nearby lines, and the same Go function without asking an AI model to guess.
OVERLAP · MEDIUM
Two tasks are changing checkout.goAlice · lines 10–18
Agent-7 · lines 16–24
03 · COORDINATE
People use the dashboard. Agents ask over MCP. Passage plans can reserve an intended area before coding begins. Every surface reads the same shared state.
agent asks · “Is checkout clear?”
She is already changing the checkout totals. Nothing is locked.
NOTE C — ONE CHART, MANY TOOLS
Farled sits beside the tools rather than replacing them. Teams can coordinate local work and remote branches across the coding assistants they already use.
Explore live radar, passage plans, dispatch, connectors, and the open protocol →
NOTE D — SEE THE REAL LOOP
One command creates a throwaway repository, starts two worktrees, makes overlapping edits, and shows the warning an agent receives.
No account, hosted service, or sample repository is required.
go install github.com/getfarled/farled/cmd/farled@latest
farled demo collision▸ Alice edited checkout.go lines 10–12
▸ agent-7 edited checkout.go lines 11–13
⚠ OVERLAPPING WORK DETECTED
Alice and agent-7 are changing the
same part of checkout.go.
Agent advice:
Coordinate before editing these lines,
or choose a different starting point.
✓ metadata only · nothing was blockedBUILT FOR THE PERSON WHO HAS TO SAY YES
The protocol has no field for source code, diff bodies, prompts, chat logs, or secrets.
FARLED CAN SEND
file pathline rangeactorbranchtimestampFARLED CANNOT SEND
source codediffspromptschat logssecretsPreview every payload before it leaves a machine with farled report --preview. Read the security details →
NOTE E — HARBOR DUES
Run the open-source demo locally, or evaluate recent pull-request overlap with Farled Cloud during the design-partner stage.
Community
Freeforever · Apache-2.0 · your machine
Local reporter, live radar, deterministic warnings, dashboard, passage plans, and agent tools.
Run the demo →Cloud Team
$10per human / month
$5per agent / month · 14-day trial
Hosted team view, pull-request analysis and annotations, approval inbox, connectors.
Start a trial — request access →Enterprise
Customannual · talk to us
Self-hosted or single-tenant, audit exports, retention. Roadmap: SSO/SCIM, SOC 2.
Talk to us →Design-partner berths are open: six months free in exchange for honest feedback and a case study. info@farled.dev
YOUR FIRST CHART
The demo is local, disposable, and shows the complete Farled loop.
farled demo collision