You describe the work. Smithers does it.
An agent that already knows what is in your repos. It works in a real filesystem and git environment sitting above your GitHub, proposes the next thing worth doing, and does it where you can watch every step, stop it mid-sentence, and reverse anything it changed. GitHub stays your system of record.
Smithers is a closed alpha, open to design partners by invitation. There is no public sign-up yet. It runs in the browser, over GitHub, with nothing to install and no terminal required.
I read your repos while you were signing in. You have 14 open issues across 3 repos. Four have been waiting more than a week.
An illustration of a first session. The content shown is an example, not a customer.
Sign in, and the work has already started.
No blank prompt box, no setup wizard, no demo video. Signing in and connecting your first repos are one act, so by the time you can type, Smithers has read enough to be useful.
Usage is metered and shown in real dollars on the run itself. During the alpha, design partners never enter a card.
Watch it. Steer it. Take it back.
An agent you have to babysit is not saving you anything, and an agent you cannot see is not one you can trust. Work in motion stays in front of you, and every change it makes has a way back.
/ for everything Smithers can do, with the
recommendation first.Nothing leaves the building without your yes.
The strength of the control scales with the consequence of the act, so routine work does not nag you and irreversible work cannot slip past you.
An approval covers what you were shown and nothing more. If the work grows past it, Smithers stops and asks a new, smaller question instead of proceeding. And it never claims to have done something it did not do: if the change did not reach GitHub, it says so.
There is nothing here for you to assemble.
Everything else in this category hands you an authoring surface and makes you the author: you lay the steps out, wire them together, and own them forever. Smithers has no authoring surface, and that is the product. You describe the work in the conversation, and Smithers creates the Flow that does it. There is no manual editor, and there will not be one. It is a product boundary, not a missing feature.
“Every Monday, tell me which pull requests are stuck and why.”
→ Smithers creates the Flow, shows you what it will do, and from then on it is yours to run, edit, or retire“Take the four issues that have been sitting the longest and tell me what it would take to close them.”
→ it works in the real repo, in real git, and comes back with the answer and the one decision it needs from youEverything Smithers can do is a Flow, and every Flow is reachable three
equivalent ways: ask for it in the conversation, type its
/name, or use the affordance on the work itself. No path is
privileged, and there is no capability hiding on only one of them.
The engine is public. You are not locked in.
Smithers runs on an MIT-licensed durable orchestration engine that anyone can read, run, and host. That is a reason to trust the product, not the pitch for it.
Installs the engine into your project with a runnable example you can
execute immediately, plus the smithers skill for the coding
agent you already use. Describe what you want and your agent creates it,
with no configuration. This is the open-source route, and it is separate
from the hosted product above.
Engine docs, written for agents →Projects built on it →Orchestration patterns field guide →
Stop babysitting the agent.
Smithers is for technical operators whose work already lives in GitHub: people running agents, maintaining repos, and carrying a queue of issues and pull requests in their head. If that is you, tell us about your repos.
Closed alpha, by invitation, with no public sign-up yet. We are onboarding design partners one conversation at a time.