One real run
Real components · real record · waiting time compressedLoading the replay…
What happens in the run
- 01Ask once, then build
You send one sentence. It asks ten questions first, then writes the requirements, the architecture and the plan. Each of the three is a gate that waits for your approval.
- 02Build a step, check a step
In DEVELOP it works through tasks T1 to T15 in order and runs the tests and the typecheck after each one. The plan on the right ticks off as it goes, and you can look at the page as soon as it runs.
- 03You talk, it takes notes
Tap the meeting button. Four people each say what they want changed, and you add three more points. It recognizes each voice, writes the transcript and the minutes, and puts the items you tick on the board.
- 04The whole batch, one click
Run everything on the board: implement → independent review → grade when a signal fires. The code is written and reviewed by different models.
- 05Only what needs your call comes to you
It needs a decision on what happens when the seats run out, so it lays out four options. You tap one on the card, and it builds the waitlist and the promote button, then asks for an independent review.
- 06Verified, shipped
In VERIFY, R1 to R15 are checked one by one in a real browser, covering the production build, phone size and both languages. The results go into VERIFY.md, and then it requests the DEPLOY gate.
- 07It keeps working after you log off
When the quota runs out it waits where it is, and when the quota resets it carries on. In the morning you get one card listing what got done and what needs your decision.
- 08A weekly report from one line
The Assistant is yours alone. It sees all your projects and remembers what you said. Ask it in one sentence and it writes the weekly report.