Yardsort
Orchestrate any coding agent — on Linux, macOS and Windows.
Open-source desktop for Claude Code, Codex and any CLI agent you already use. Parallel tasks get their own git
worktrees; several agents can share one. Hand the work to the next agent with the context Yardsort already
recorded — no re-explaining the branch. Agents can read what the others said, and write smoke tests that Yardsort runs.
yardsort.sh ·
Download ·
Quick start ·
Documentation ·
Contributing ·
Contact

## What it is
A sorting yard is where rail cars are sorted onto parallel tracks and later joined back into one
train. That is the job: fan work out onto parallel branches, then merge it back — and hand a car
from one crew to another without retelling the whole journey.
You describe a task, pick an agent, and press Enter. Yardsort creates a branch and a **git
worktree** for it — a separate folder — and starts the agent there in a real terminal. Start
another task on another track, or start a second agent in the same worktree. **Hand off** writes
the next agent a first message from what happened here: your task, the branch, who wrote each file,
what every run did. Project memory carries the short lessons you approved. On the right you watch
the files each one touches, live, with diffs. An agent started beside another can read what that
one was asked and answered, and a smoke test an agent wrote checks the result step by step.
It is modeled on tools like Conductor and Superset, with the requirement they do not meet:
**Linux, macOS and Windows are all first-class**, built and tested together on every change.
## Highlights
- **Track tokens and machine resources.** Open **Usage** from the sidebar to compare Claude
Code, Codex and Grok by day, model and workspace, see estimated API costs and Codex's last
reported plan limits, or inspect live CPU and memory for every terminal's process tree.
[More below](#usage-tokens-cost-estimates-and-machine-resources).
- **Keyboard navigation you can configure.** A command palette, panel focus and workspace/tab
switching, with an in-app [shortcut cheat sheet and editor](docs/guide/shortcuts.md).
- **A guided first look.** An optional welcome tour explains the main panels; replay it from
Help / Tour any time.
- **Any terminal agent.** Claude Code, Codex, Grok, OpenCode, OMP, Cursor and Pi
[out of the box](#supported-agents); add any other with a few lines of configuration — no
plugin, no release to wait for.
- **The terminal is the truth.** Agents run in a real PTY with their own interface. Whatever they
can do in your terminal, they can do here — and Yardsort never parses their output.
- **Plain git, no lock-in.** Workspaces are ordinary worktrees and branches. Inspect or undo
anything with `git`. Worktrees made elsewhere can be imported, and never appear uninvited.
- **Closing the window doesn't stop them.** Terminals live in a small background process, so
agents keep working while Yardsort is closed — or after it crashes. Open it again and every
screen is repainted where it got to. Closing with work in flight asks first.
- **Pick up where you left off.** For conversations that really did end, press **Resume** — it is
intact. **Fork** one to try a different approach without losing the first.
- **Hand the work to another agent.** One click writes the next agent's first message from what
Yardsort recorded — your task, where the branch stands, who wrote each file, what every agent
run did and what is not known — for you to read and edit before it goes. Codex after Claude,
without retyping the story. [More below](#hand-the-work-to-another-agent).
- **Agents that know what the others said.** An agent started in a workspace where another has
been working is told so, and `ys workspace context` reads it what you typed and each turn's reply,
from the agents' own transcripts, without tool output. Every built-in agent can be read, nothing
is stored, and a project can turn it off, since what an agent reads goes to its provider.
[More below](#shared-conversations-agents-that-know-what-the-others-said).
- **Build on work in progress.** **Fork into new workspace…** starts a new branch from a
workspace's branch, in a worktree of its own, and tells the new agent what was recorded about the
one you forked. [More below](#hand-the-work-to-another-agent).
- **Workflows: named agent work, in steps.** A short YAML file — have a second agent review
this pull request, then tell me and the agent that wrote it — run from the sidebar or with
`ys workflow run`, its steps drawn as a chart, every mistake named at its line. The built-in
code review is one click in a workspace's menu. Describe one in your own words and a model
writes the file, for you to check and save. [More below](#workflows-named-agent-work-in-steps).
- **Smoke tests: the ten-minute check, repeatable.** The steps a person runs by hand before
saying "done" — start the server, open a page, click, look for a word — written as a YAML file
in your repository, that an agent writes and Yardsort runs, step by step, with every output,
screenshot and reason for a failure kept. **Tests**, in the sidebar, lists every test and every
run. A file from a repository never runs until you have seen it.
[More below](#smoke-tests-the-ten-minute-check-repeatable).
- **Schedules: at a set time, or on a routine.** Run a workflow or a smoke test once at a time
you pick, or again and again — every weekday at nine, every two hours, a cron expression — in
a workspace you already have, or for a workflow in a new one made for each run, while Yardsort
is open. A notification tells you when a run fails. [Schedules](docs/guide/schedules.md).
- **Triggers: when something happens.** Start a workflow or a smoke test when an agent says its
work is done, someone reviews the pull request, its checks fail, a run ends, or something you
name happens. Ready-made ones — address reviews, fix failing checks, review or smoke test the
work when it is done — are a box to tick when you start a workspace. A cap per pull request, an
hourly limit and a limit on chains keep a trigger from looping.
[More below](#triggers-when-something-happens).
- **See what happened.** Live list of changed files, character-level diffs, a file tree, and
image previews. Edit text files inside Yardsort, with retained drafts and a check before
overwriting a file changed on disk, or open them in your editor. With an agent reporting,
each changed file says who wrote it: an
agent that reported writing it, one that was running a command when it was last written, or
nobody the record knows of.
- **Send it on without leaving.** Commit what an agent wrote, push it, and open the pull request
from the panel you reviewed it in — the title written from the commits. With the
[GitHub CLI](https://cli.github.com) the pull request opens from here and its number and check
results appear on the workspace row, with any others the workspace opened beside it — those
opened in other repositories too, like the nested clones of a parent project, once Yardsort
sees an agent open one or an agent or you track it; one that conflicts with its base can be handed back to the agent that opened it
to resolve. Without
`gh`, your browser opens the forge's own form, on GitHub, GitLab, Bitbucket or Gitea alike. See
[Commits & pull requests](docs/guide/commits-and-pull-requests.md).
- **Every pull request in one place.** **Pull requests**, at the top of the sidebar, lists the
pull requests of every project on GitHub — yours, a teammate's, an agent's — with their checks,
reviewers and size, filtered by project, author and review status. Open one to read its
description, its checks, the conversation and its diff, with every comment beside the lines it
is about; reply, or select lines and send a note about them to the agent working on it. Start
a workspace on one, merge it, close it or reopen it from there, each confirmed first and naming
whose it is. A pull request an agent opens in another repository — a nested clone of a parent
project — is listed too, with the workspace it came from, and is merged, replied to, read and
[reviewed](docs/guide/workflows.md#a-pull-request-in-another-repository) the same way. It reads
GitHub through `gh`; Yardsort still holds no credential.
[More below](#every-pull-request-in-one-place).
- **Your issues, where the agents are.** **Tasks**, in the sidebar, lists every project's open
GitHub issues and counts the ones that need an answer — where the last person to speak was
not a maintainer. Open one to read it, then **Delegate**: the composer opens with the issue
as the agent's first message, marked as text other people wrote, and nothing starts until you
say so. The workspace remembers the task it came from. Open a new task, answer one, close,
label and assign it from the same view. `ys task` does all of it from a terminal, so an agent
can tell you what is open and file an issue when you ask. Everything goes through `gh`.
[More below](#your-issues-where-the-agents-are).
- **One agent that sees everything.** The [Floor Manager](docs/guide/floor-manager.md), in the
bottom bar's corner or **Mod+J**, is an agent you pick that has every project in view through
`ys`. Ask what is running, which pull requests nobody has reviewed or which need attention, or
to start a task. It suggests a workflow, opens workspaces on other people's pull requests and
starts reviewers on them. How much it may do on its own is a setting: read only, ask first
(the default) or trusted. `ys` enforces it. Deleting a workspace, closing a task and
attaching stay refused. A shell command that is not `ys` is outside that gate.
- **Start from a repository or a link.** **Clone a repository** lists the repositories your `gh`
account owns or collaborates on — type to narrow, pick one, clone — or takes a clone URL from
GitHub, GitLab, Bitbucket, Gitea, Forgejo or a host of your own. **Start from a link…** takes
an issue's or a pull request's address and opens it, ready to delegate; a repository that is
not a project yet is cloned on the way. See [Projects](docs/guide/projects.md#clone-a-repository).
- **Know who needs you.** Status dots show which agents are working and which are waiting; a
desktop notification tells you when one finishes while you are elsewhere, and
[Notifications](docs/guide/notifications.md) lists, over every project, what waits for you
and what finished while you were not looking: agents that ask for a permission or are done,
workflows waiting for an approval or an answer, smoke tests waiting to be let run, and
schedules and triggers that could not start. Other computers you reach are in the same list.
- **Careful with your work.** Deleting or archiving a workspace always keeps the branch, and
never discards uncommitted changes without a second, explicit confirmation.
- **A second pair of eyes, if you want one.** [Assist](docs/guide/assist.md) asks
[Jev](https://docs.typesafe.ai), TypeSafe's judgment model, small typed questions about each
changed diff, and badges the files that look unrelated to the task, or that add a secret, weaken
a test or switch a check off. It can also suggest a harness and an effort for the message you
are typing. Off unless you bring your own TypeSafe API key — see
[below](#assist-judgment-from-jev-if-you-want-it).
- **Private by construction.** No account, no telemetry, no keys of ours. Agents use their own
logins; Yardsort just starts them. It talks to the network to check for new versions, which you
can switch off — and, only if you switch Assist on and add your own key, to ask Jev about your
diffs, or, only if you turn on [Remote](docs/guide/remote.md), to the server you choose.
- **A record of what ran.** Yardsort keeps a local note of when each agent started in a
workspace and how it ended — even if it ended while the window was closed — without reading a
word the agent printed. Turn it on, and every built-in agent — Claude Code, Codex, OpenCode,
Grok, OMP, pi and Cursor — reports its own tool calls, file changes and turns to the same
record, as metadata, with its own settings untouched. An experimental timeline shows it;
`ys activity export` writes it out. See [Activity](docs/guide/activity.md).
- **Project memory, approved by you.** Short lessons about a project for its agents — "the tests
need `TZ=UTC`". You write them; agents propose them with `ys memory propose`, and those wait for
you. Only what you approve reaches an agent: after its first message, cited, and in handoffs —
unless you turn that off for the project. See [Memory](docs/guide/memory.md).
- **Outcomes, in your words.** After you archive or delete a workspace, one optional click says
how it went; a merged pull request counts as kept until you say otherwise. Each agent's history
on your own work sits beside the composer's picker — and says "too few to say" until there is
enough of it. See [Outcomes](docs/guide/outcomes.md).
- **Choose how agents start.** Enable **Always start in auto mode** per harness in
[Settings](docs/guide/settings.md#auto-mode). For Claude Code and Codex,
with activity capture enabled, a [context hint](docs/guide/terminals-and-sessions.md#when-an-agents-context-fills-up)
offers **Compact** when a conversation reaches 80 % of its context window.
- **Keeps itself current.** Signed in-app updates on macOS, Windows and the Linux AppImage — one
click, and your agents' conversations resume afterwards.
- **Scriptable.** [`ys`](docs/guide/cli.md), a small command-line client that comes with the app,
starts a workspace and an agent without opening the window: `ys workspace new