One agent, one computer, and it can do magic.
Fill in the latest funding for the 40 companies in my spreadsheet.
Put 4 researchers on it; filled funding, stage and lead investor for all 40. Flagged 3 conflicts for your review.
Make four cover options for the launch post.
Made 4 in parallel; kept the 2 that still read at thumbnail size. Saved with the prompts that made them.
Draft a reply to the funding email, in my voice.
Pulled the thread and your last few replies for tone. Drafted a concise yes with two clarifying questions — awaiting your OK to send.
Ship the notes dashboard as a real app.
It’s running and supervised. If it ever dies I’ll bring it straight back up and tell you.
Update the deck with the numbers from the new model.
Pulled the revised model, updated six slides and the two charts that read from them. Left your commentary alone.
Anything waiting on me?
Two things: approve the funding reply, and confirm Thursday’s calendar change. Everything else is done or still running.
It has a computer.This is what it does with it.
01 — Research
It goes and finds out.
- Reads the filings — says what moved
- Fills a spreadsheet — row by row
- Runs 4 researchers — at once
- Flags what it’s unsure of — for your review
40 rows · 4 researchers · 4 minutes
02 — Create
It makes the actual thing.
- Makes 4 images — keeps what fits
- Charts your numbers — from your own files
- Writes the brief — doc, deck or PDF
- Keeps the prompt — that made each one
4 made · 2 kept · 90 seconds
03 — Build
It ships it, running.
- Writes code — and runs it
- Ships an app — on a live port
- Restarts it — when it falls over
- Reads the error — then fixes it
2.1s build · live on a port · watched
Revenue
30 daysMRR
£12,480+3.1%
Churn
1.2%−0.3%
- Launch planmoved to March
- Launch post4 covers kept
- Launch metrics3 charts
Overnight
Run while I sleep
Wake me for blockers
next run 23:00 · saved
04 — Watch
Then it carries on without you.
- Wakes on a schedule — no one watching
- Works overnight — reports by morning
- Drafts the reply — waits for your OK
- Says when something needs you — and only then
212 rows · 6 briefs · 1 retry, nothing lost
Every job getsits own keys.
It never holds every permission at once. You put it in a mode, and the mode decides what it can reach, what it is refused outright, and what it has to come back and ask you for.
Find out why api-2 is throwing 502s.
systemctl status nginxactive (running) · 4d 2hss -tlnp14 listeningjournalctl -u nginx --since 1h2 warnings · 0 errorscat /etc/shadowrefused · secrets never enter its contextsystemctl restart nginxasks you · a restart can’t be taken back
- On its own
- Refused
- Comes back to you
The longer it runs,the less you explain.
One long memory instead of a fresh start every morning. Corrections hold, preferences stick, and everything you built up last month — the people, the projects, the reasons — is still there, so your time goes into the work.
First timeMarch 3
Draft the investor update.
Happy to — three things first: which numbers go in, what structure do you like, and who is it going to?
3 answers from you
Three weeks inMarch 24
Draft the investor update.
Done — your usual structure, Friday’s numbers, in your voice. Waiting for your OK to send.
nothing needed · your structure, your voice
It can do anythingyou can put into words.
Built by Recursion Endeavours
lovelace is an open source project