A visual interface for the Claude API: a small lesson from Fluffy Parrot
Field Notes, 2026-06-09
The most interesting thing I learned shipping a Claude API control surface had nothing to do with the API.
I shipped Fluffy Parrot, a control surface for the Claude API, and the lesson that stuck had nothing to do with the API itself.
Working with the API directly is lifeless. You set numbers and run prompts, but you get no real sense of where you are in the parameter space you are moving through. That is why I built Fluffy Parrot: to bring every parameter the API exposes to life in a surface you could actually see and feel.
The first version was a custom-designed UI with sliders, buttons and knobs for all of those parameters. Precise, sensible, and a good start, but reading a value off a slider is not far from reading it out of code.
The fix was physical, not technical
The API is all about code, so I made the controls physical: hardware-style knobs in a VST-inspired interface. Same values, same ranges, but tuning suddenly felt tactile. You were turning something, not editing a piece of code. That one change altered how I used my own tool.
The deeper point: when a task is about building intuition, the interface should make the variable space feel like a place you can move around in, not a config file you edit.
But the decision that actually mattered
Giving every run its own tab, with its cost and round-trip time attached, so two takes sit side by side. Once you can read the diff, you stop trusting your memory. That's the moment a playground becomes an instrument.
More field notes