In active development · local build
Serra runs on your own machine. Two claps wake her. She opens the applications you have allowed, arranges your windows, answers in her own voice — and writes down everything she did. No recording, no network listener, no administrator rights.
Alpha software. Not yet available to download.
double clap · çift alkış
Live
Every value below is read from the current build. The control centre shows what she is allowed to touch — including the two entries that are switched off.
System status
Control centre
Audio
Values from the current build. Serra is in active development and is not yet available to download.
Vocabulary
A fixed list of actions, not open-ended instructions. Each one is written, tested and added by hand. The list grows as the work does.
Brings up the ERP in the browser. The address is on the allowlist, so nothing else can be opened in its place.
Opens the mail client so the morning routine starts without hunting for a tab.
Speaks a reply from a file already on the machine. Nothing is generated or fetched at the moment of use.
Tidies the windows she opened herself. She will not move or resize anything that belongs to another application.
Defined but unavailable on this machine. Shown so the list reflects reality rather than intent.
Deliberately switched off. Anything not enabled is refused, even when the action exists.
“I could not map that to an allowed action.”
What she says instead of guessingWhat she does
Audio is measured for loudness only. No recording is ever written to disk, and there is no transcript.
No open port, no server, no remote control. There is nothing for anyone outside to connect to.
Actions and web addresses come from a list you write. Anything not on it is refused rather than guessed at.
Each action is appended to a dated log file you can read afterwards, in plain text.
How it works
The whole loop runs on your machine. Nothing leaves it.
Audio is watched for loudness only. A clap has to cross 0.040 rms, and there is a five second cooldown so a door closing does not set her off twice.
The request is checked against the list. If nothing matches, she says so rather than improvising something close.
She runs as a normal user, opens only allowlisted addresses, and moves only the windows she opened herself.
The action, the time and the result go into a dated log. Ctrl+Alt+Shift+Q stops everything at any point.
Where she is today
She can open FB Software ERP. She cannot yet create or edit anything inside it.
Opening a page is not the same as working inside one. That comes later.
Depends on interfaces, permissions and platform rules. We will not claim it before it exists.
Build logs go up as the work happens, and the tutorials show how each piece was made — including the parts that failed.