Skip to main content
Smithers Cloud · closed alpha · access by request

A working environment above your GitHub.

You describe the work. Smithers builds the thing that does it, and runs it in a real filesystem with working git on top of your GitHub repos. There is nothing to assemble: no canvas, no graph, no SDK. You watch it work, steer it, or take it back. GitHub stays the system of record, so changes land there through the normal review path.

It is in closed alpha. There is no public signup: accounts are added to an allowlist by GitHub handle, by hand.

Request access →

No card, and nothing to install. If you are not on the allowlist yet, there is a developer route at the bottom of this page.

to · will@smithers.shread by a person
Three lines is enough
1. GitHub handle
2. What you would point Smithers at: the repos, or the work you want moved
3. What you run today
copied ✓

The GitHub handle is the part we actually need, because the allowlist is keyed on it. Click the block to copy the template, or use the button and your mail client will fill it in.

Write the email
What the hosted product is

Not a view of GitHub. A place to work.

The workspace

Your repos exist as real files with working git. Nothing to clone, no local install, no terminal required to get started.

Flows, not black boxes

Work runs as named Flows you can watch in a timeline, interrupt, and redirect mid-run. Nothing completes or fails silently.

GitHub stays canonical

Changes land back in your repos as commits, PRs, issues, and comments. Smithers replaces the interface, not the system of record.

Who the alpha is for

Technical operators whose work already lives in GitHub.

People who run agents, maintain repos, and carry a queue of issues and PRs. The job it is built for:

“Stay on top of the work in my repos and actually move it, without babysitting an agent.”

If that is not your week, the alpha probably is not for you yet. Say so in the email anyway and we will tell you straight.

Not in this alpha
Web only. There is no desktop or native app to download. Local files and local repos are reached through the hosted workspace, not your machine.One user, one workspace. No teams, no shared workspaces, no seats to invite.Sources beyond GitHub. GitHub plus the filesystem and git of the workspace itself. That is the connector set.Support guarantees. One person is on call. No SLA, no uptime guarantee, no 24/7 support, and nothing on this site will pretend otherwise.
If you are let in

What the first session is built to do.

Written down so you can hold us to it rather than find out later.

Sign-in and the first connector are one act. What Smithers will read, and what it will never do without asking, is stated in plain words before the OAuth screen.
Your repos as a real filesystem with working git. Nothing to clone, install, or configure before anything useful happens.
The first message is not a greeting and not a blank prompt box. It is what Smithers found in your actual repos.
What it proposes, why now, what happens if you accept, and how to accept, edit, or dismiss it. Dismiss is one key and it does not argue.
In the timeline while it works, as a card in the conversation when it lands. Stoppable and redirectable while it runs; never a silent completion.
A push, a PR, an issue, a comment: Smithers shows exactly what it will do and waits for an explicit yes. Every time, never remembered.
What the run actually cost, in dollars, and what is left. No invented credit unit. Alpha usage is on us; see pricing for the rate card.
The one thing we will not trade

It is an alpha. Things will be missing and things will break. What does not bend: Smithers never claims to have done something it did not do. If it cannot do the thing, it says so.

After you send it

Honest expectations.

What happens
A person reads the emailAccepted handles are added to the allowlist by handYou sign in with GitHub and start in the workspaceAlpha usage is subsidized: no card, no checkout
What we are not promising
A reply by any particular dateA seat, because the alpha is small and deliberately soA queue position or a status page to refreshAn automatic confirmation email
Request access →

Or write to will@smithers.sh in your own words.

No allowlist required

The hosted environment is gated. The durable orchestration runtime it is built on is MIT-licensed, needs no cloud, and runs on your machine today. If you are here because you want agents that survive a crash and can be rewound, start there. Nobody has to let you in.

Install the open-source CLIRead the source

Back to smithers.sh·Pricing·What Smithers is