Free · a gift

Build the dashboard yourself. We'll send you the prompts.

People keep asking how something like this is built. So here it is, for nothing: four prompts for Claude Code, and by the end of an evening you have your own dashboard with a particle orb and a voice that answers you.

Done — the file is on its way to your inbox. If it isn't there in a few minutes, check the spam folder.

Got it — your trial request is in. The trial is limited and we hand it out in order; a real person will reply to your e-mail.

What you get

01A dashboard with an orb made of particles. The same idea as the one talking to you on the front page.
02Voice through your microphone. You talk, it answers out loud.
03The orb reacts to sound. It moves while it speaks, instead of sitting there.
04Bonus: a memory. It writes what you tell it into a plain text file, so something survives from one session to the next.

What you'll need

Claude Code. That is where the prompts get pasted — one after another.
Your own keys: the brain runs on your Claude Code subscription (flat rate, no Anthropic API key needed; an API key works too). Groq for speech-to-text, free: get a key · 2-minute video. ElevenLabs for the voice, the free tier is enough: sign up · how to get the key. You register them yourself and they stay yours — we never see them.
An evening. An actual evening, not ten minutes. That is rather the point.

The honest part

What you build is a skeleton, and the skeleton is the easy part. It talks, and it comes with a simple visualization. Tell Claude Code what you want and make the orb your own: how it moves, how it reacts to your voice, the background, the colours. If you see something you like, snapshot it, hand it to Claude Code and keep going — generate images, try new effects. Just know where you stand: you are at the very beginning. You get four prompts from us; Darwin is built on more than 7,000. The skeleton does not read your mail, does not touch your files, does not run a team of agents, does not remember across months — and nothing in it stops it from doing something you never asked for. The rest is Darwin: the guardrails, the mistakes already made, the evenings that ran into the night. Nobody writes that in one sitting, and we are not going to pretend otherwise.

Two more things said plainly. We cannot support this — you get the file and the rest is yours, that is what free means here. And if you would rather see the finished thing than build one, ask for a trial with the second button below. The trial is limited: we hand it out in order, to a small number of serious requests at a time, so we can actually help each of them. One sentence about what you would use Darwin for helps us pick.

Before you start, read this.

Eighteen things that decide whether it works every day — or sends the wrong thing at three in the morning.

Permissions, prompt injection, where the keys live, memory, retries, audit, cost. It is not a list of reasons to give up — it is the list of things we worked through one at a time.

What to watch out for ›

And if you want to see how many such decisions sit behind a finished assistant: 100 questions from behind Darwin ›

Where should we send it?

We keep your e-mail so we can send you the file. If we ever write again it will be about Darwin, and one click gets you off the list. Details in the privacy policy.

‹ back to Darwin