One project
The sound, controls, routing, saved state, and interface stay together instead of being split across several toolchains.
Audio tools should be easier to finish.
A good instrument can start as a five-minute idea and disappear into weeks of plugin plumbing. Syntho keeps the sound, interface, and build process in one project so more of that time goes into making the tool.
Making the sound is only the beginning.
You can sketch a filter, delay, sequencer, or small instrument in an afternoon. Turning it into something another musician can install and trust is where the project gets heavy.
Suddenly you are dealing with realtime processing, MIDI and timing, parameters, saved state, interfaces, plugin formats, packaging, and host behavior. Most of that work has nothing to do with the reason you opened the project.
The usual stack asks for a lot up front.
Before the first useful version, you may already need C++, a DSP language, a native widget system, build scripts, plugin hosts, and format-specific knowledge. Coding agents can help, but they still need a project with clear boundaries and a way to hear what they changed.
Web tools are wonderful for the interface. Audio frameworks are good at the realtime work. The awkward part is still joining them into one product.
So we put the pieces in one project.
In Syntho, a coding agent can work on the sound graph and the actual interface in the same project. You can play each change in the workbench, give feedback, and keep the source available to inspect or change yourself.
Built for coding agents
Typed contracts, working examples, and clear checks help an agent build without guessing at the audio rules.
Live in the browser
Play the graph through the real interface while you and the agent are still changing it.
Ready for supported builds
When the tool feels right, run the checks and build the plugin, standalone, or hardware targets supported by the project.
Go from an idea to a working audio tool.
Start from a prompt or the closest working module. Let the agent assemble the graph and interface, then listen and direct the next change. A utility can stay personal, become a plugin, or grow into a product for other musicians.
Use the included controls or build the interface with normal web tools, including custom visualization and 3D. Add custom audio code when the included building blocks are not enough. When the project is ready, run its checks and build the formats it supports.
Bring a sound, a problem, or a half-finished idea.
Start with the closest module and shape it with a coding agent. Listen to each change, keep what works, and turn it into a tool that feels like yours.