Two toys from one-line briefs: a sequencer and a guitar tuner built with Kaisen

We gave Kaisen (in preview) two small briefs, a browser sequencer and a guitar tuner, and kept giving feedback. Nine runs, about $0.31 in total, two live apps you can try, and the main limit: it cannot hear or click what it builds.

Share

We pointed Kaisen, our build agent (in preview on PicoPaaS), at two deliberately small briefs and then kept giving feedback like a normal user would. The results are live and you can try them: a browser sequencer at sequencer.picopaas.xyz and a guitar tuner at tuner.picopaas.xyz. Both were built in the same Demo project with Claude Haiku 5.5.

The sequencer (jamtunez)

The brief was vague on purpose, verbatim: "I want an in-browser music production application with a piano roll, multiple tracks, basic audio effects, and the ability to export the audio and the track (i should be able to open an existing song and continue editing it, too)."

  • Run 1: 28 steps, about 4 minutes, $0.04. Plain Web Audio, no libraries. Tracks with sine, triangle, square and sawtooth voices, volume, pan and mute; a piano roll; a per-track low-pass filter, drive and delay; WAV export through offline rendering; save and open of a .jam.json project; autosave; 19 node tests. It also listed what it left out, including "no arrangement timeline", and suggested a multi-pattern arrangement as the next step.
  • Run 2: Chas reported that a repeated chord only sounded once. 10 steps, $0.02. Kaisen said it could not reproduce the audio and that the fix addressed likely causes, not a confirmed root cause. It added a regression test using Chas's song, and it played correctly afterwards.
  • Run 3: a pattern-based arranger. 36 steps, about 7 minutes, $0.13. Patterns of 1 to 4 bars per track, an arrangement timeline where you place, drag, duplicate and delete clips, songs up to 128 bars, multi-select with copy and paste, undo and redo, a noise/drum voice, and project format v2 that still opens v1 files (old notes become one pattern at bar 1). 39 tests.
  • Run 4: edits now apply live during playback. 17 steps, $0.02; 40 tests.

Four runs, about $0.21 in total. None of them hit the 40-turn per-run limit: the feedback rounds split a big project into small runs on their own. We also checked in a real browser that v1 migration and clip playback render correctly.

Rough edges, honestly: live edits rebuild the whole audio graph on every slider tick, which causes clicks and cut notes; the toolbar wraps on narrower screens; patterns cap at 4 bars. Chas's verdict was that it needs a lot of polish, but as a tool to get started building something it is genuinely useful.

The guitar tuner

The brief: a tuner that plays all six strings, with alternative tunings (drop D, E flat, DADGAD, DGCGCD and so on), an animated guitar, and strings you click to loop until you click again.

  • Run 1: 9 steps, $0.013. An animated canvas neck, looping strings, keys 1 to 6, and 10 tunings. The brief had the typo "DADGAG"; Kaisen read it as DADGAD and said so.
  • A microphone tuning meter (pitch detection in the browser, a cents meter, audio never leaves the browser), a custom tuning editor, and bass, ukulele and banjo tunings: 17 steps, $0.03.
  • Arrow-key navigation: 8 steps, $0.004.
  • A Chords tab with 16 chord diagrams and strummed progressions in any key: 15 steps, $0.02.
  • A capo selector that transposes chord names and diagrams: 27 steps, $0.03.

Five runs, about $0.10 in total.

What we learned

Kaisen cannot hear or click what it builds. Every summary said so plainly ("I could not run the UI in a browser"). That is why audio and UI bugs, like the chord that only played once, come back through a person. It is the main limit today, and the human feedback loop is what makes these apps work: small, specific reports ("this chord only sounds once") turned into small, cheap runs.

If you want to poke at the results, open the sequencer and the tuner. Kaisen is in preview on PicoPaaS, and we would like to hear what you build with it.