Symphony, a daemon that builds issues from docs and calls a person when it gets stuck — plus Lassorun, our docs and QA platform
I built it because people were babysitting recurring issues by hand — checking progress, reviewing, asking again. Symphony picks up an issue, has AI agents build it from the docs, and pings a human on Slack when it’s stuck. Docs, test cases and reports all flow through Lassorun.
What people said
Ultimately I’d like it to be manageable from a dashboard, even by people who aren’t developers.
My part
- 1
Symphony
I designed and built, on my own, a daemon that takes an issue, develops from the docs and calls a person on Slack when it gets stuck.
- 2
Lassorun · feedback widget
I built Lassorun, which ties docs, test cases and reports into one flow, and the widget for leaving feedback right on the screen.
- 3
Spreading it in-house
I ran the internal demo in 2026.07 and turned Claude Code tips sharing into a regular session.
Specials — what I changed
- 1
Issue handling
BeforePeople checked progress, reviewed and re-requested by hand every time
AfterWhen an issue comes in, AI agents build it from the docs and ping a person on Slack when they get stuck. After the internal demo in Jul 2026, it went to work on the KITS teacher and admin web apps.
About Internal dev automation
- When
- May 2026 – present
- Role
- Design, build, rollout across the team
- Scope
- Symphony · Lassorun · feedback widget
- With
- CEO · in-house developers






