Ergosphere Run it

Your autonomouscoding factory.

Ergosphere turns coding agents into a factory that runs on its own. It builds what you ask for and repairs the code you already have. You answer only the few questions that need you.

You writeone page.

Describe the change on one page: what you want, the requirements, and the rules that must never break.

Ergosphere checks the page before any agent starts and tells you what is too vague to test. When it is clear, you approve it. That is the only step that needs you.

Not ready: one problem to fix.

See the agents work

S14Invoice dates follow the user's time zone

draft

Outcome

The date column of the invoice table shows each date in the viewer's time zone, not in UTC.

Requirements

R1
A date is rendered in the time zone of the signed-in user.
R2
The table loads fast.
R3
An export keeps UTC and says so in its header.

Invariants

I1
A stored timestamp is never rewritten by a change of zone.test: S14 I1 stored_timestamps_survive_a_zone_change

Readiness

  • Checked before any agent starts
  • The outcome is stated
  • R2 says “fast”: no test can check that
  • I1 has a test named S14 I1
  • No open assumption, no decision left unrecorded
  • Not approved by you yet

Try it: fix the requirement nobody can test, then approve.

The agents do the rest.

  1. build
  2. review
  3. merge
  4. release
  5. watch
  1. Built in isolation.The page becomes tasks. Each one gets an agent in its own copy of the repo, and every change comes with a test.
  2. Reviewed by another agent.One that did not write the code reads the diff and asks for proof. What it finds gets fixed; after three failed rounds the page comes back to you.
  3. Merged on main.Rebased, the full test suite run, merged. If CI turns red, the factory fixes it before the next change goes in.
  4. Released step by step.Behind a flag, to a few users first or as an A/B test. The page says which numbers must hold before everyone gets it. The release waits for your yes.
  5. Watched in production.If those numbers drop, the factory rolls the release back and opens the fix on its own.

It repairs itself.It gets better.

Shipping is half the job. After the release the factory keeps watching: anything that signals a problem becomes a task, and the task becomes a fix on main.

  1. “Checkout fails for some users.”An incident. The factory rolls the release back, reproduces the failure in a test, fixes it and ships again.
  2. CI turns red on main.It finds the commit that broke it and repairs it before anyone notices.
  3. “The invoice shows the wrong date.”A customer email. It becomes a task with the customer's words attached, and a test that fails until it is fixed.
  4. A variant wins its A/B test.It becomes the default, and the code of the one that lost is removed.

When nothing is broken, it looks for work: flaky tests, dead code, slow queries, docs that drifted from the code. Correct an agent twice and the correction becomes a rule every agent follows.

Waiting for you 2
T91May the export change its header? A decision, asked by the lead of S14.waits 4 min
T88Run make integration? A permission, asked by the implementer.waits 1 min
Running
T90build · the zone in the export's header · 4 commitsclaude
T86review · dates in the viewer's zone · round 1codex
T84land · timestamps survive a zone changegemini
Landed today
T83the invoice table reads the user's zone14:02

See who needsyou first.

Thirty-two agents, several providers, a dozen repos: one list. On top, the agents waiting for your answer: type a few words and they carry on. Below, what is running and what got merged.

Your company,as one graph.

Everything connected

Every task, spec, decision, commit, agent session and conversation in your company becomes part of one knowledge graph. Each piece is linked to what it touched: the code, the people, the reasons, the result.

Agents that know the company

Before an agent starts, it reads the graph: why a decision was taken, what was tried before, who owns this part of the code. Nothing gets rediscovered, nothing gets decided twice.

Ask it anything

Why did we drop the old export? Which sessions touched billing this week? What breaks if we change this table? Every answer links back to its source.

Works withwhat you have.

Any agent
Any coding agent, from any provider, side by side on the same work.
Your repo
Any git repo. Tasks and specs are markdown files in it. No lock-in.
Laptop or team
One command on your machine, or one server with the same screen for everyone.
Open method
Based on extremespecification.com.

Start withone command.

Point Ergosphere at a repo. It reads the tasks and specs, finds the agents already at work, and opens your factory in the browser. Nothing leaves your machine.

Star it on GitHub
$ ergo up ~/code/your-repo