JAGGYHello folks,
We're building Jaggy to help musicians spend more time playing and less time wrestling with software. That includes people finding their feet, as well as experienced players fitting music around an already full day. We're also exploring how AI can help run a project, with Jack directing the work and signing it off, and AI assistants Tiggy, Mother and Cassie supporting development, review and coordination.
The principle is simple: Helps, Not Creates. You make the musical decisions. Jaggy's job is to make the practical steps easier, using your tools and the effects available on your machine.
What works
REAPER on Windows is our starting point. The current command contract is deliberately small: check the connection, set up a riff track, or create a record-input tone track using installed effects.
Earlier development tests demonstrated a typed request being carried through to an approved tone setup in REAPER. One recorded test also rejected an unsupported destructive request without changing the project. Those are useful foundations from specific tests; they don't establish that the current package is ready for every setup.
Clear results matter too. The contract distinguishes completion, completion with warnings, failure, and a command already handled. A request arriving is only one step. The result should tell you what happened in REAPER, without encouraging an unnecessary repeat.
What moved forward this week
The remaining work now has a tracked plan with dependencies and review points. Ten user-testing stories have been drafted around real workflows. Their execution remains on hold while the prerequisites are resolved.
The developer-link directory is now a detailed, filterable resource with over 600 plugin and FX entries. That includes format variants and REAPER components, varied pricing, and details marked uncertain where needed. Jaggy won't distribute those plugin files. The aim is to help people explore their options and find the original developer.
What still needs proving
A matching current installer and a complete recovery kit are still awaiting acceptance. The new laptop tests haven't run. The proposed sequence is to identify the setup, check the recovery material and preserve existing work before separately approved installation and music tests.
The latest nightly backup attempt stopped at a file-stability check. That attempt didn't establish a verified backup or successful remote copy. Recovery remains unfinished work. A green tick has to earn its keep.
Next
The proposed next step is to agree a finite internal Windows/REAPER acceptance checklist, then work through the package, recovery and workflow checks. Internal acceptance will still be separate from a public release. There's no install invitation or release date to announce yet.
Longer term, conversational or voice interaction should be optional and feed the same constrained actions. Voice and broader DAW support remain future work. The DAW-independent direction stays important: the musician should keep control of the tools and the music.
Which setup task most often interrupts your playing?
Jack, Tiggy, Mother and Cassie