How to make
your own VST plugin
There is a version of this that takes a C++ team and six months. This is the other one — what it takes now, and what you actually end up with.
Short answer
How do you make your own VST plugin?
You describe the plugin you want to a coding agent, and Pook runs what it writes live in your DAW. You never write or read code, and you install no development toolchain. A first working version usually loads in a few minutes, and every change after that arrives while your session keeps playing.
What you actually need
Three things, and no more than three. Everything else that used to be on this list — a compiler, a plugin SDK, a build system for each platform, a signing certificate — Pook handles or removes.
Pook, loaded in your DAW like any other plugin. It is the host: it runs your plugin, plays it, and reloads it the moment anything changes.
A coding agent on your machine — Claude Code, Codex, Cursor, GitHub Copilot, Antigravity, or another. This is the part that writes the plugin. Each is a paid subscription from its maker, and several have free plans.
A description of what you want to hear. Not a spec, not a signal-flow diagram. The way you would describe it to another producer.
What you are describing, and how specific to be
The useful instinct is to describe the result, not the mechanism. “A short bright room that keeps the transient intact” gets you further than naming a reverb algorithm, because the second one commits your agent to an approach before either of you knows whether it fits the track.
Be specific about the things you can hear. Length, brightness, how hard it grabs, what it should do to the low end, whether it should sound clean or broken. Those are the words that turn into parameters you can then reach for on the interface.
You are allowed to be vague on the first pass. The first version exists to be wrong in a direction you can name — that is faster than trying to specify it correctly up front.
What a plugin can be
Anything the format allows, which is more than most plugin catalogues suggest. Pook Fx covers everything that processes audio; Pook Instrument covers everything played from MIDI.
The plugins worth building this way are usually not the ones you can buy. A compressor is a solved problem. The chain you rebuild on every project, the exact broken delay that only works on your vocal chain, the instrument that only makes sense inside one record — those are not products anyone would ship, which is precisely why nobody has shipped them to you.
How long it really takes
A few minutes to the first working version. Then the real work starts, and it is the same work you would be doing anyway: listening, deciding what is wrong, and asking for the change.
A simple idea lands in a few passes. An ambitious one takes longer, in the same way mixing a difficult song takes longer than mixing an easy one. What has changed is not the amount of judgement required — it is that each pass is instant instead of a rebuild-and-rescan cycle.
What you keep
The plugin source lives on your own machine, in the clear. You can read it, back it up, put it in version control, and hand it to a different agent later. Pook claims nothing over it.
Every plugin saves with your DAW project, including its state, so a session opened years later sounds the way you left it. You can send the file to anyone else running Pook. And if one turns out too good to keep to yourself, the publishing side of Pook is being built to turn it into a plugin with its own name that other people can buy.
Step by step
- Install a coding agentInstall an agent on your machine and sign in. Most take a couple of minutes.
- Open Pook in your DAWLoad Pook Fx on an audio track, or Pook Instrument on a MIDI track, and follow the on-screen steps.
- Describe what you want to hearTell your agent the plugin you are after, in plain words. It writes the plugin into your project folder.
- Listen, and ask for changesPook loads it the moment it is ready, while your session keeps playing. Say what is wrong and it changes — no restart, no rescan.
More questions, answered
The first working version usually loads in a few minutes. Getting it to sound the way you imagined is the part that varies — a few passes for a simple idea, longer for an ambitious one. Each pass is instant, so the time is spent listening and deciding rather than waiting on a build.
No. You describe what you want to hear and your agent decides how to achieve it. Knowing the vocabulary helps in the same way knowing the names of mixing moves helps — it makes you quicker to say what is wrong — but nothing requires it, and you can pick it up from the results rather than before you start.
You tell it what you heard and it tries again. A wrong version is not a setback here; it is the fastest way to find the words for what you actually want. The source is plain text on your machine, so nothing is lost and you can always go back to a version that worked.
No. Pook Fx, Pook Instrument and Pook Studio are one-time purchases, not subscriptions, and the plugins you build are yours to keep and use in your own sessions for good.
Keep reading
Try it on something of your own.
Pook is free to download and free for 21 days, every feature, no card. Bring your own coding agent and hear the first version in a few minutes.