Jackson Lawrence, Software Engineer
Jackson Lawrence
Software Engineer · San Francisco, CA
Tap anything to see how it connects.
Work & projects
- Waltz2026–now
- AnyForm2026–now
- The Cratest2026–now
- Oracle2025–now
- Trailblaze2021–2024
- KoiStream2020–2021
- CareerFoundry2022–2023
- TEDx Design Tech2019
AI & agents
Product & frontend
Backend & data
Cloud
Waltz
Project · Agent software factory · October 2026 – Present · In development
A desktop app that runs a team of coding agents for you. The agents do the work and decide how, and you set the why. It has landed about 60 changes to its own code.
Built with
- Multi-Agent Orchestration
- Prompt Engineering
- AI Coding Tools
- TypeScript
- React / Next.js
- Rust
- Playwright
Posting a request, and Waltz replying with the Task it planned. The agent runs here are scripted test data.
Why I'm building it
Coding agents can do a lot of the work of building software now. Running several of them at once is the hard part, because you end up reading pages of their output and keeping track of who is doing what.
Waltz is a desktop app that runs a team of agents for you. The agents do the work and decide how it gets done, and the human sets the why. It isn't an editor. You rarely write code in it, you direct and review.
What I built
You ask for something by typing it into Announcements. Waltz replies in the same thread with the Task it planned, then tells you when it's built, and then that it passed review and landed on main.
Each run works in its own copy of the repo. A second agent reviews the change, and nothing lands unless the project's own check passes. The Agents tab shows what is running and what is waiting, and you can open any run and watch it work.
Waltz only stops to ask about direction, taste, or something that can't be undone. Those questions sit at the top under "Needs you", each with a few choices and a recommended one, and you answer with a click. You also pick how much it may do without asking, and by default the agents land their own work.
The app is Rust inside Tauri with a React front end. Agents run either through the Claude Code CLI or through Waltz's own client for the Anthropic API.
How it's going
I wrote the spec in October 2026 and soon had one full loop working, from a request to an approved merge. Within days Waltz was landing changes to its own code. It has landed about 60 of them so far, and two were reverted.
The biggest change came in early November. By then the app had Goals, Issues, Requirements and more, and my own spec said it "reads like a wall of AI text". I collapsed all of it into Tasks that Waltz keeps up to date and the human only reads. Every agent now posts under one name, Waltz, and the merge buttons for work I'd already asked for went away.
After a Task lands, the agents look back at how it went and write what they learned into their own instructions.
It runs on macOS and is built for one person so far.
What it taught me
Getting agents to write code was the easier half. Most of my rewrites have been about what the person in charge has to read, and how little of it there can be before they stop knowing why things happened.






