← All work

FREYA

AI assistant · Open source

My own AI assistant, and the reason I trust AI with real work. Freya builds things, checks them herself, fixes what’s broken and only then tells you she’s done.

View on GitHub ↗

Type: Personal project
Runs on: Her own window · voice · terminal
Stack: Go, no outside libraries
Status: Open source, running on my desktop

Greenwood & Sprout, a plant nursery: a site Freya built — Six of the sites Freya has built in her workspace. She wrote every page, checked it and served it herself.

Iron & Shear, a barbershop: a site Freya built — Six of the sites Freya has built in her workspace. She wrote every page, checked it and served it herself.

What it is

Freya runs on your desktop, in her own window or a terminal, and you can type to her or just talk. I wrote her in Go without a single outside library, so she’s one small program that builds in seconds. The thinking is done by Gemini or Claude.

The problem she solves

Most AI tools will tell you a job is finished when it isn’t. Ask for a website and you get pages with broken links and a contact form that goes nowhere. I kept running into this, so I built Freya to check her own work.

Telling her to be careful made her a little better. Having her count the broken links as she wrote them took the number to zero, and it stayed there.

One real run

This is a real run of her building a four-page site for a plant nursery, tool by tool, with her reasoning between the steps cut for length:

❯ build a four page site for my plant nursery

  → file_write   index.html · catalog.html · care.html · contact.html
  → site_check   contact.html: form action="#" submits to nowhere
  → file_edit    contact.html
  → site_check   4 pages, nothing leads nowhere
  → review       three weakest things, from someone who has never seen her work
  → file_write   ×4  rewritten against the review
  → site_check   still clean

24 rounds. Nobody asked her to check the form or to have the work reviewed.

What she can do

Drive a real Chrome browser, with 43 tools for it: click, type, upload files, switch tabs and read pages that keep loading as you scroll.
Use desktop apps by reading their buttons, fields and menus, the same way a screen reader does.
Build a website, check every link and image, serve it and open it on your screen.
Remember where your things live, like which email you use and where your calendar is.
Show her work in a window of her own, where her thinking and every tool call stream in as they happen.
Around 150 tools in all, plus voice input and spoken replies.

Careful with your stuff

Anything that can’t be undone asks you first, in her window, with a preview of exactly what will change. For the really serious actions a quick “yes” isn’t enough. You have to type the word out.

Lean on purpose

About 52,000 lines of Go and 21,000 lines of tests, built on a 2014 laptop with no graphics card. If she runs well there, she’ll run well anywhere.

Tech

Go, Chrome DevTools Protocol, AT-SPI, Gemini, Claude, Speech-to-text