Rewire.
Join waitlist

Rewire Editor

Build the plugin you wish existed.

Visual DSP graph, live UI, code, and an AI agent that scaffolds and verifies — then load your VST3 in the same desktop suite's Studio, or ship it to Rewire Market.

Download Rewire DesktopRequest Editor access

Part of Rewire Desktop · LM Studio for AI · Local JUCE toolchain

Inside the Editor

From idea to loadable VST3

The Editor is the plugin workbench in the Rewire suite. Build tools you'll load in Studio, then share them on Market.

Workbench

Graph. UI. Host. One editor window.

Each plugin opens in a dedicated editor. Switch modes without losing context — wire signal paths, lay out controls, edit code, and audition.

Graph

Wire signal paths — code regenerates from your architecture.

UI

Lay out knobs and sliders with live binding to graph params.

DAW

Load your VST3 in the built-in host and hear it in context.

  1. Graph

    Visual signal architecture — the source of truth for audio routing and processor params.

  2. UI

    Drag-and-drop control layout with live binding status mapped to the DSP graph.

  3. Host

    Mini host to load your built VST3, automate params, and hear changes in context.

  4. Files

    Project tree with tabbed code editor, quick-open, and find-in-files.

  5. Monitor

    Runtime stats and build telemetry while you iterate.

  6. Diagnostics

    Verify results, build logs, and structured checks before you ship.

DSP graph

Wire real processors — not mock nodes

The graph is the source of truth. Connect audio through delays, EQs, saturators, filters, and synth oscillators. Parameter IDs flow into the UI and regenerate JUCE processor code automatically.

  • Effect chains: audioIn → processor → audioOut
  • Synths route MIDI through oscs, envelopes, and filters
  • Bypass is always a UI toggle — never a graph node
audioInaudioOutdelayeq3saturatorfiltergainoscenvelopelfomixernoisefattenertransitionmeter

Real toolchain

Not a toy — actual JUCE on disk

Projects live in a local folder you own. CMake builds produce loadable VST3 binaries. Generated regions stay in sync; you never hand-edit scaffold markers.

  • Effect and synth templates out of the box
  • Resources/dsp-graph.json drives processor codegen
  • Build, launch, and debug from the same workbench

Verify loop

Ship with confidence

Every graph edit and file write can be validated before you build. The agent is trained to re-run verify until the project is green.

  • Schema checks on dsp-graph.json
  • Binding validation between UI and graph params
  • Structured diagnostics instead of guess-and-check

AI agent

LM Studio–powered assistant, on your machine

The agent rail sits beside your editor — thread history, tool calls, verify feedback, and starter prompts. Models run locally; nothing leaves your machine unless you publish.

  1. Ask

    Read-only research — search the project, explain code, answer questions without touching files.

  2. Agent

    Full edit loop — write dsp-graph.json, sync UI, run verify, fix until checks pass.

  3. Plan

    Research the codebase and publish a step-by-step plan for a follow-up Agent turn.

Workflow

From blank slate to listed plugin

  1. 01

    Describe your idea

    Start from a plain-language brief or draft a marketplace listing with AI — name, category, formats, summary.

  2. 02

    Scaffold a JUCE project

    Generate a real C++ project on disk — CMake, processor/editor stubs, and sync regions ready for your graph.

  3. 03

    Design the signal path

    Wire nodes in the DSP graph. The editor regenerates processor code from your architecture.

  4. 04

    Lay out the UI

    Place knobs, sliders, and toggles. Controls bind to graph parameters — bypass stays UI-only.

  5. 05

    Build & listen

    Compile a VST3, load it in the host, and audition on Studio tracks without leaving Desktop.

  6. 06

    Ship to Market

    Push your listing to Rewire Market. Buyers find you on the web; you keep building in the Editor.

Same suite

Load in Studio. List on Market.

The Editor isn't a silo — it's how you invent tools for the music you're already making in Rewire.

  1. Studio

    Audition where you produce

    Drop your built VST3 on arrangement tracks. Hear it with clips, mixer, and stems — not a dead preview window.

    Explore Rewire Studio →

  2. Market

    Ship to independent makers' shelf

    Push listings when you're ready. Musicians browse on the web and install through Desktop.

    See Rewire Market →

FAQ

Common questions about the Editor

What is Rewire Editor?
Rewire Editor is the plugin creator workbench inside Rewire Desktop. Design DSP graphs, lay out UI, edit code, build real JUCE VST3 plugins, and verify with an AI agent — then audition them in Rewire Studio.
Do I need to leave Rewire to test my plugin?
No. Compile a VST3 and load it in the built-in host or onto Studio tracks in Rewire Desktop. Graph, UI, code, and audition stay in one editor window.
How does the AI agent work?
The agent runs locally via LM Studio. Use Ask for read-only research, Plan for a step-by-step approach, or Agent to edit dsp-graph.json, sync UI, run verify, and fix failures until checks pass.
Can I sell plugins I make in the Editor?
Yes. When you're ready, push a listing to Rewire Market. Buyers browse on the web; you keep shipping updates from the Editor.

Get started

Get the Editor inside Rewire Desktop

Download the suite, join the waitlist for Editor access, and start scaffolding real JUCE projects on your machine.

Download Rewire DesktopJoin the waitlist