In-house · not for sale

Kaylee, the system that runs Campfire Tales.

Kaylee is the company's in-house AI operations system. It runs on one Windows PC, keeps the company's records in a local database, and does the overnight work. It is built in public.

Read the build log
What it is

Five parts, one PC.

  1. 01

    A local brain

    The company's records, decisions and to-dos, kept in a database on the same PC, not in a hosted service.

  2. 02

    An overnight build lane

    Specs drafted and small builds run on their own branches overnight, checked before anything lands.

  3. 03

    A morning brief

    One email at 7:30 every morning: what ran overnight, what is due, what is waiting on a decision.

  4. 04

    A voice console

    Requests by voice, from the dashboard or the phone.

  5. 05

    Phone asks

    Anything that needs a yes reaches the phone as a notification that names it.

How it runs

One person, with the routine work scheduled.

Campfire Tales is one person. Kaylee is how one person runs a software company: scheduled jobs on one Windows PC do the overnight and early-morning work — backups, health checks, research, drafting the next specs — and the founder reads the results and makes the calls in the morning. Every job, its schedule and its last run are visible on the dashboard below. First build: .

Kaylee's Ember dashboard, home view: the company's projects drawn as worlds in orbit around Kaylee, beside a command-center panel of counts and alerts.
The system picture. Every project in one view, with what is waiting on a decision.
Kaylee's crew page in the Ember dashboard: one card per scheduled job, with its role, its model, its last run time and its exit code.
The crew. One card per scheduled job: what it does, the model it runs on, when it last ran.
Kaylee's choreography view in the Ember dashboard: the scheduled jobs laid out by when they run, in overnight, morning and all-day columns.
The choreography. When each job runs: overnight, morning and all day.

Screenshots of the live dashboard, taken October 10, 2026. Names on screen are the jobs' own.

Build log

What landed, and when.

Newest first. Each entry is a dated item from Kaylee's own build history.

  1. The research browser refuses private addresses

    Built overnight by Kaylee's own build lane and merged before 6 am: the browser her morning research uses now stops every request to a private address, redirects included, before it leaves the machine.

  2. Shop prices kept in step

    Kaylee reads each print-on-demand provider's cost and shipping and keeps the shop's prices in step with them.

  3. Phone alerts by web push

    Asks and alerts reach the phone through the dashboard's own web push. The dashboard installs as an app.

  4. Build watch

    Every building agent now works under a watch: an exact file list, stop rules, and a done-check it has to pass.

  5. First build-in-public video

    The first video about building Kaylee went up on TikTok.

  6. Voice console, tightened

    Five fixes from the first week of talking to Kaylee from the phone. Anything an outside AI wrote is now labelled when it is read back.

  7. Ember, the new dashboard

    One view of every project, job and decision — the screens shown above.

  8. Kaylee on the phone

    The dashboard and the voice console reach the phone, behind a login. Kaylee rings only when something cannot wait.

  9. Park by voice

    A to-do can be parked by voice from the console, and undone the same way.

  10. The morning-after check

    After a night of work, Kaylee first checks what actually ran, from each job's own logs, before the night's draft is read.

  11. Phone asks

    A decision waiting on a yes reaches the phone as a notification that names it.

  12. First build

    Kaylee's first commit.

Build in public

The videos.

Short videos of Kaylee being built, as they are posted.

Campfire Tales on TikTok