steading

One person. A thousand agents.

You decide what to build. Agents plan it, build it, review it, and ship it, with proof at every step, on machines you own. Steading is the open-source stack for building software this way, and you can start running it today!

Paste this into your agent
Read https://stead.ing/llms.txt and help me figure out if it's a good fit for my work.

Paste the prompt into your agent, or start with the project for your problem.

48,210 pull requests merged6,104 deployed

05:0006:0007:0008:0009:0010:0011:0012:0013:0014:0015:0016:00Frankfurt.youthicketskiftmillcroftalmanacknowledge

14:28 knowledge: Indexed 9 changed files and the pull requests that changed them, so the next answer cites today's code.

You've got more ideas than hours.

You pay for a model subscription (or four) and either max it out or barely use it. Not for lack of ideas, but because babysitting agents eats up most of your time.

  1. Talk out a problem.
  2. Set a goal.
  3. Switch windows.
  4. Lose the thread.
  5. Find out your agent is blocked!

Every morning feels like Monday brain.

We hit the same wall.

A platform you can take apart

Great on its own, better together

Everyone else is building one big system for you to move into. Steading is a platform too, but it's made of projects, each built to do one job well, each with an open interface. If you have a better idea for a project, swap in your own; the rest keeps working.

How work moves through Steadingyoumodels, GitHub, APIsthicketyou talk it throughskiftholds the planmilldoes the workmerged, runningyour idea, shippedalmanacwatches the worldknowledgerememberscroftfences it ingatewayholds the keys
You talk an idea through with thicket, which files it in skift as tasks; almanac files tasks too, when something in the world changes. Skift hands mill whatever is ready. Mill works each task inside a croft, which asks knowledge what it needs and sends every outside request through the gateway. The work comes back checked, mill merges it, and knowledge indexes what changed.

What's your biggest bottleneck?

Start with what's slowing you down today. Every project works on its own, and they get better together.

Running daily

Used every day to build Steading itself.

  • “I can't see what my agents did overnight, or what it cost.”

    consoleTies it all together

    Shows what every project is doing and what needs a person, on a phone as well as a desk.

  • “My agents step on each other, and nobody knows what's ready.”

    skiftHolds the plan

    One plan for every agent, on every machine. It always knows what's ready.

    Source on GitHub

  • “I babysit every task until it's merged.”

    millDoes the work

    Takes a ready task to a merged, running change, with proof at every step.

Early

Working, with rough edges.

  • “Dependency updates pile up faster than I merge them.” One account: 97 of 119 open pull requests.

    almanacKeeps things maintained

    Repairs broken dependency updates for tens of cents.

    Source on GitHub

  • “I want to hand an idea to an agent from my phone.”

    thicketAgents you can talk to

    Agents on the systems you run, reachable from Slack or a phone call.

    Source on GitHub

  • “I'm on a Mac, and all of this wants Linux.”

    steadPuts it on your Mac

    Runs skift and mill on your Mac.

In design

Not built yet. Shown so you know where this is going.

  • “My agents have free rein on my machine.”

    croftKeeps work fenced in

    Sandboxes the operating system enforces, and virtual machines for code you don't trust.

  • “My agents hold my API keys.”

    gatewayHolds the keys

    Agents never hold your credentials. Inside mill today; its own name is still to come.

  • “Every session starts from scratch.”

    knowledgeRemembers what was learned

    Agents stop starting every job from scratch. Its own name is still to come.

  • “My disk is full of what agents left behind.” One workstation: 41 GB.

    fallowTakes back the disk

    Takes back the disk your agents leave behind.

What we believe

You decide what. Agents do the rest.
Nobody should have to sit in a chat window for work to move.
Proof, not promises.
"Done" means a program checked it.
Real fences, not polite requests.
What an agent can touch is limited by the operating system, the network, or a virtual machine, not by a sentence in a prompt.
Code over prompts.
A model is called only where judgment is actually needed.
Yours.
Your hardware, your database, your rules.
Fork it.
Take any project and make it your own. Send back what's worth sharing.

Don't build it all on your own!

Everyone is building their own version of this and hitting the same walls. Build it with a community instead. Come hang out on Discord, pick up an open task, ask questions, or show us what you've made!

Join the DiscordHow we work, and how a project joinsSteading on GitHub