Use casesTwo shapes of work, in depth

Multi-repo changes and migrations.

Two kinds of engineering work that outgrow a single agent session. Each page follows one of them through the harness and shows the artifact it produces.

Two jobs routinely outgrow one isolated session: a change that crosses multiple repositories, and a migration that has to carry its exceptions forward. These pages show how AI coding agents are coordinated around both.

Multi-repo development

One objective, several registered checkouts

You register the checkouts a change touches, and one mission plans across all of them. Each specialist then takes a bounded slice in its own git worktree, working from the same approved plan and the same pinned interface.

Artifact: the workspace topology for a rate-limiting change across four checkouts

How a change that crosses repositories runs

Framework and dependency migrations

The same decision, applied a few hundred times

A migration produces a large diff and a small set of exceptions that took real thought. The diff is the easy half. The exceptions are what a fresh agent session throws away, and what the mission keeps.

Artifact: the exception ledger partway through a logging-API migration

Running a framework or dependency migration

Looking for Kubernetes troubleshooting, CI/CD, or progressive delivery? Those are use cases for the open-source Skyflo Kubernetes agent, a separate Apache-2.0 project.

Kubernetes agent use cases

Start with whichever of these you recognise.

Skyflo Desktop runs the mission on your Mac, against your checkouts, with your own model keys, and carries what each mission teaches into the next.

Free. macOS 14+. Apple silicon and Intel.