Documentation
Everything you need to write DSP in TypeScript, put a web UI on it, and ship it as a plugin. Start with the quickstart if you want sound in ten minutes; start with How it works if you want to know why any of this is shaped the way it is.
Getting started
From an empty folder to a pedal making sound in your browser, then the same pedal as a VST3.
The four nouns — kernel, schema, engine, shell — and how a sample travels through them.
What the scaffold puts on disk, which files you actually edit, and what is generated.
Tutorials
Distortion into tone into delay, built up one stage at a time — the shape of FX Mini.
Oscillator into filter into ADSR into gain, with voice allocation and note events — the shape of OSC Mini.
No audio path: take note input, emit chords, and route the result to another tool or your DAW.
Move an existing Tone.js chain onto kernels, node by node, checking parity as you go.
Sdk
The public entry point: createAudioEngine, isNativeHost, the codexHost bridge, and backend selection.
The shared types: ParamSchema, AudioKernel, KernelIO, AudioEvent, GraphPlan, and the normalize math every surface agrees on.
Stock restricted-TypeScript DSP kernels, their ScriptC library profiles, and the rules kernel sources follow.
The browser transport: the ScriptC WASM reactor loader, the WASI shim, and the result-bytes convention.
The native and offline backends: a compiled-TypeScript AudioContext control API over the native ScriptC audio engine.
Manifest-driven codegen for the native plugin shell: VST3 param tables, deterministic class ids, the state-chunk codec, and the codexHost protocol.
Cli
Scaffold a plugin project from a template, with the full template list, flags, and what lands on disk.
Hot-reloading dev server, live parameter inspector, and MIDI device selection.
Build VST3 and standalone targets from your manifest, plus platform requirements and what lands in build/.
Submit a tool to the directory: required assets, the review checklist, and versioned updates.
Fork any published tool into a local project and start editing it.
Concepts
What sample-identical means, how it is tested, the f32 rules you inherit, and where the gaps currently are.
The full lifecycle: metadata, assets, review, versioning, and deprecation.
Where licensing stands during the research preview, and the upstream obligations that already apply to anything you build.