Agent Farmbeta Join early access

District I of XSeven things

Never stops

Work keeps going through full contexts, full accounts and its own updates.

An empty desk at dusk, a lamp still on beside a laptop and a phone

A long job outlives any one session. When a context fills, a fresh session takes over from a handover note. When an account's window fills, the next leg opens on another account. When every account is full, the chain waits for the reset and carries on. You set the lines and the brakes once.

05 Day and night

chn_7f3a · demo data shaped like the real chain

Ninety-two legs. Three days, four nights. Straight off the backlog.

Every block is one fresh session, coloured by the account it ran on. The band above it is the backlog item it was given: when an item closes, the next session opens on the next one in your queue. Night or day makes no difference to it. A hatched gap is the chain waiting for a quota reset, then waking by itself. Hover a block to read it.

0legs
0hwall clock
0items closed
0parks till reset
0quota handovers
0self-updates

07 The rules of the relay

Real defaults · every one is a setting

Runs without you. Braked so it never runs away.

Every number below is a setting you can change. These are the defaults the extension ships with.

35%

Converge

The session is told once to start nothing new and finish the step in flight.

contextConvergePct
40%

Hand over

It stops, commits, writes its handover note and ends the run. The next leg opens with that note.

contextHandoverPct
90%

Quota handover

When its account's five-hour window is this full, the leg hands over and the next one opens on another account.

quotaHandoverPct
98%

Weekly line

The same handover for the weekly window, so a chain never runs an account into the wall.

quotaWeeklyHandoverPct
PARK

Wait for the reset

Every account past the wall? The next leg parks until the first reset, then wakes and carries on.

parked until 02:15
BRAKE

Barren-chain brake

Two legs in a row that end on the same commit stop the chain, instead of burning quota on nothing.

batonMaxHops
FAILSAFE

Emergency leg

A leg cut off by an error or left with uncommitted work gets a successor that is told what it left.

batonEmergencyTemplate
0

No ceiling

Chains are capped at 6 legs by default. Set it to 0 and the relay runs until the work is done.

batonMaxHops: 0
I·1

Baton relay

At the context level you set (40% by default), a session commits, writes a handover note and a fresh session carries on. No context rot.

Watch a chain run for three days

What it solves

A long session gets worse as its context fills: it loses the start, repeats itself and begins to guess. Starting over by hand means explaining everything again.

How it works · pick a step

The two lines reach a running session through Claude Code's hooks. On the other engines the crossing is recorded on the session card as undelivered, so it is never assumed to have been said.

Settings · 4
SettingDefaultWhat it does
agentFarm.contextConvergePct35%Told once to start nothing new and finish the step in flight. 0 = off.
agentFarm.contextHandoverPct40%Told once to stop, commit, write its handover note and end the run. 0 = off.
agentFarm.batonInjectedDirectiveemptyA standing rule said to every leg, above its predecessor's words.
agentFarm.batonHandoverTemplateemptyWrite the successor's message yourself, with {leg}, {chain}, {agentPrompt} and the rest filled in.
I·1Watching1 / 5
I·2

Quota handover

Before the 5-hour window fills, the next leg opens on the account with the most room.

The lines side by side

What it solves

A plan's five-hour window runs out in the middle of the work. When it does, the session stops dead and whatever was half done stays half done.

How it works · pick a step

Settings · 6
SettingDefaultWhat it does
agentFarm.quotaHandoverPct90%The five-hour window's line. 0 = off.
agentFarm.quotaWeeklyHandoverPct98%The week's line; the next leg leaves that account. 0 = off.
agentFarm.quotaConvergePctoffBelow the handover line a run works at full capacity, unless you set this.
agentFarm.contextHandoverStayAccountPct70%Under this, a handover that was not about the quota keeps the next leg on the same account.
agentFarm.defaultAccountCeiling70%An account this full is passed over by every start that runs without you.
agentFarm.defaultAccountWeeklyCeiling95%The same wall for the week.
I·2Its account1 / 5
I·3

Account policies

Four built-in rules (@emptiest, @pool, @standing, @round-robin) or your own. A rule that can pick no account refuses the launch and says why.

What it solves

Which account a session runs on is a decision. Making it by hand at every launch is how the wrong plan gets drained.

How it works · pick a step

The setting's own example: {"name": "Night", "chain": [{"account": "spare"}, {"policy": "@emptiest", "ceiling": 80}]} is @Night. It tries the spare account first, then the emptiest one under 80%.

Settings · 2
SettingDefaultWhat it does
agentFarm.accountPoliciesnoneYour named rules, offered in every account picker as @Name.
agentFarm.defaultAccountCeiling70%The wall a rule obeys unless it names its own.
I·3Four built in1 / 4
I·4

Park and wake

One account or ten, when all of them are full the chain waits for the first reset and carries on by itself.

See the parks in the three days

What it solves

With every account full, a chain left alone would either fail or keep knocking on a closed door.

How it works · pick a step

Settings · 1
SettingDefaultWhat it does
agentFarm.taskRetry.safetyBufferMin3 minAdded to the stated reset time before the parked leg starts (0 to 240).
I·4Parked1 / 4
I·5

Ouroboros

An agent builds a new Agent Farm, restarts it inside VS Code and carries on in the same session. Nobody has to restart anything.

Watch it on the home page

What it solves

An agent that improves Agent Farm itself needs the new build running. Restarting VS Code's extensions would normally cut off every session, its own included.

How it works · pick a step

There is no button and no setting for this. It is something an agent does over the bridge (farm.restartExtensionHost, with resume), behind fixed guards.

I·5Asked1 / 5
I·6

Sentry

An agent runs the chain instead of a fixed rule: it takes the next item, opens a clean session, reads the result and decides what comes next.

See it on the home page

What it solves

A fixed rule keeps a chain going but cannot tell a round that went nowhere from one that worked. Paying a large model to watch every round is a waste.

How it works · pick a step

Settings · 6
SettingDefaultWhat it does
agentFarm.sentryLeaderModelhaikuThe leader's model. Its engine is Claude Code unless agentFarm.sentryLeaderEngine says otherwise.
agentFarm.sentryLeaderBudgetUsd$2 a dayOnce spent, the campaign carries on mechanically. 0 = no daily budget.
agentFarm.sentryLeaderMaxUsd$0.25The most one leader turn may cost.
agentFarm.sentryLeaderMaxSeconds120 sThe longest one leader turn may take.
agentFarm.sentryFailureLimit3Empty rounds in a row that switch the campaign off. 0 = off.
agentFarm.sentryStallMin45 minA round silent this long ends as failed and is not retried. 0 = off.
I·6Rounds1 / 5
I·7

Brakes

A leg ceiling per chain, spend caps per workflow and one stop for a whole chain. Recorded, never deleted.

The brakes among the rules

What it solves

Anything that runs without you has to know when to stop, or it spends your quota on nothing.

How it works · pick a step

Settings · 2
SettingDefaultWhat it does
agentFarm.batonMaxHops6The most legs one chain may run; the run that started it is leg 1. 0 = no ceiling.
agentFarm.workflowSpendCapnoneThe most one workflow run may spend, in dollars. A workflow can set its own, and one run can override both.
I·7Leg ceiling1 / 5

Questions

Does the next session remember anything?

It starts fresh, on purpose: a session already at the handover line would walk straight back into the wall. What carries over is what the last leg wrote, its handover note and the words it passed, plus your standing rule.

I have one account. Is this for me?

Yes. The relay still hands over at the context line. When that account's window fills, the chain parks until its reset and carries on by itself.

Does it work on engines other than Claude Code?

The next leg opens on the same engine as the leg before it. The converge and handover lines reach a running session through Claude Code's hooks; on the others the crossing is recorded on the session card as undelivered, so you can see it was not said.

Can a chain run for ever?

Only if you let it: set the leg ceiling to 0. The barren-chain brake still stops a chain whose legs stop committing, and you can stop it at any time.

What happens at night when every account is full?

The next leg parks until the first reset, plus 3 minutes, and starts by itself. Notices tells you when; in the morning the chain has carried on.