Agent Farmbeta Join early access

District VI of XNine things

Never forgets

Every session is kept, and what matters becomes a wiki.

A fountain pen writing a line in a notebook

Every conversation on this machine is kept, from every engine, with what it cost, and any turn of it is a click away. What mattered does not stay buried there: you mark it in passing, and later one run writes it into your wiki, one concept to a page, each fact pointing back to the turn it came from. Models get replaced; what they worked out stays.

12 Memory

Sessions · wiki · Obsidian · memory

Every session kept. What mattered becomes a wiki.

Every conversation on this machine is kept, from every engine, with what it cost. Mark the turn that mattered; nothing is written yet. Later one run reads the marked turns and writes wiki pages into your Obsidian vault, one concept to a page, each with its sources.

Vault · Obsidian

You curate, agents write. Pages are plain Markdown in your own vault; the links between them are what Obsidian draws as a graph.

VI·1

Every session kept

Yours and the farm's own runs, from every engine, with cost, tokens, context and the chain leg.

The Sessions page, live

What it solves

Each CLI keeps its conversations in its own folder, in its own format. A week later nobody can say which session decided what, which one is still running, or what any of them cost.

How it works · pick a step

A session's subagents are gathered under it, with what they cost together on the parent's row. A live feed shows the farm's newest prompts, tool calls and errors as they happen, and a click opens the session at that message.

Settings · 2
SettingDefaultWhat it does
agentFarm.includeUnmatchedProjectsfalseAlso list sessions outside your agents' folders, under Other projects.
agentFarm.activeThresholdSeconds150A session whose log changed within this many seconds counts as active.
VI·1Every engine1 / 5
VI·2

Any turn, replayed

Open a session, filter its turns, replay it or export it as Markdown.

A session, live

What it solves

A long session is a wall of text. The decision you are after is in one turn of forty, between screens of tool output nobody needs.

How it works · pick a step

A session also opens with the files it changed: each one's writes, lines added and removed and the turns that touched it, unfolding to that session's own edits. vs HEAD beside it shows what is still uncommitted in the file now, and an edit that failed is marked as never applied.

Settings · 1
SettingDefaultWhat it does
agentFarm.maxTranscriptMessages1500The newest messages shown for a very long session.
VI·2A map of turns1 / 5
VI·3

Wiki from sessions

Mark a whole session or only the answers that matter. An agent compiles them into wiki pages, one concept per page.

A turn kept and compiled, live

What it solves

Decisions get made in the middle of conversations and are never written up. Stopping to ask where a thought belongs in a wiki is exactly what makes sure it is never written down.

How it works · pick a step

The Wiki page shows what is waiting, what it is about and which pages a compile wrote, searchable with the farm's query grammar. A mark only reads compiled once the run itself says it wrote the page.

Settings · 1
SettingDefaultWhat it does
agentFarm.wikiAgentdeveloperThe agent that compiles the wiki.
VI·3Mark it, free1 / 5
VI·4

Drop box

Save a chat from any browser into the drop folder and it becomes wiki material by itself.

The drop box in the Wiki page, live

What it solves

Much of what you learn never happens in a CLI: an answer in a browser chat, an export from another assistant, a note you typed yourself.

How it works · pick a step

The Wiki page's strip shows 📥 _RAW_ with how many files wait in it, and pressing it opens the folder.

VI·4Drop a file1 / 5
VI·5

Obsidian, the second brain

Obsidian is the IDE, the model is the programmer, the wiki is the codebase. You curate, agents write.

The vault, live

What it solves

Your notes live in one app and your agents' notes in hidden folders, and the two drift apart. Every change to how things are organised leaves a trail of documents that are no longer true.

How it works · pick a step

Settings checks the wiki's three files, its rules, its index and its log, and offers 🛠 Start the wiki here when they are missing. Until they exist, the compile buttons say why they will not run.

VI·5You curate, agents write1 / 5
VI·7

Memory that gets used

Each agent's memory files say which were really recalled in 30 days, which the index lost and which contradict each other, and a graph shows how they link up.

The Memory Graph, live

What it solves

Agents keep memory files, and an index of them loads into every session. Nobody knows which files are ever read, which ones the index has lost, or which say the opposite of another.

How it works · pick a step

CLAUDE.md, the memory index and AGENTS.md load at the start of every session and are paid for every time, so an agent whose fixed load passes its budget gets a warning.

Settings · 2
SettingDefaultWhat it does
agentFarm.staleMemoryDays45A memory file untouched this long is flagged as stale.
agentFarm.contextBudgetTokens8000The weight of what loads into every session before a warning.
VI·7What it recalled1 / 5
VI·8

Other machines

Sessions synced from your other computers show up in the same lists, with a machine badge on each.

What it solves

Agents on a laptop and a desktop are two farms. The history and the cost of one never show up on the other.

How it works · pick a step

Settings · 1
SettingDefaultWhat it does
agentFarm.extraClaudeDirs[]Other machines' synced .claude folders, each with a name.
VI·8Mirror it1 / 5
VI·9

Reports and digests

Daily and weekly digests and fleet reports, written into your vault.

A report in the vault, live

What it solves

The farm works while you are elsewhere. At the end of a week you want one page that says what it did and what it cost, in the place you keep everything else.

How it works · pick a step

The day's scorecard can also reach your phone over Telegram, and each project gets its own weekly summary.

Settings · 4
SettingDefaultWhat it does
agentFarm.autoReportoffWrite the fleet report by itself: daily or weekly.
agentFarm.autoReportFolderThe folder the reports are written to, such as one in your vault.
agentFarm.autoReportDays7How many days a report covers.
agentFarm.autoReportIncludeOutputstrueAdd the task outputs of the period to the report.
VI·9A scorecard1 / 5

Questions

Does Agent Farm copy my conversations somewhere?

No. They stay where each CLI writes them. Agent Farm reads them, and keeps an index and a search cache it can rebuild at any time; even renaming a session leaves its transcript untouched.

Do I need Obsidian?

The wiki is a folder of Markdown pages, written for Obsidian, where the links and the graph come alive. Pages can just as well open in VS Code or an app of your choice.

Does building the wiki cost money?

Marking costs nothing. A compile is one run on your wiki agent, metered like any task, and before it starts a strip shows the engine, model and effort it will use.

Does searching by meaning send my conversations out?

It is off until you choose a provider. With a cloud provider the passages go to it to be indexed; with Ollama everything stays on your machine. Text and regex search never leave it.

Can it read every old conversation?

Claude Code, Codex, Gemini and OpenCode, yes. Antigravity stored its older conversations in a form with no published schema, so only the ones Agent Farm hosted itself, which it writes out as plain JSON, open in full.

What is the difference between an agent's memory and the wiki?

An agent's memory is its own notes, loaded through its index into every session it starts. The wiki is shared knowledge, compiled from sessions for you and every agent, and it lives in your vault.