This one still feels a bit surreal to write.
Phantom has been approved for the official Anthropic Plugin Marketplace.
When we started building this, we just wanted real measurements inside our mixing sessions without bouncing between plugins, DAWs, and reference docs. Claude could already reason about audio. It just couldn’t measure anything. So we built the measurement layer, put it on GitHub, and figured maybe a handful of engineers would try it.
Getting approved for Anthropic’s marketplace wasn’t something we planned for. If you’ve been curious about Phantom, now’s a good time. One command, under a minute, you’re running.
What’s new in v1.2.3
Two themes in this release: tools that fix problems (not just find them), and a more hardened codebase.
fix_audio and apply_processing
Phantom has always been good at telling you what’s wrong. “60 Hz hum.” “Sibilance at 7 kHz.” “Mud around 250 Hz.” Useful, but you still had to open a plugin and fix it yourself.
Not anymore.
fix_audio runs problem detection under the hood, then applies corrective processing. Hum gets a tuned high-pass filter. Sibilance gets a de-esser. Mud gets a parametric cut. You can target specific problems or let it handle everything. Original file stays untouched.
apply_processing is the creative side. Describe what you want (“high-pass at 80 Hz, gentle compression, limit to -1 dBTP”) and Phantom builds the chain and runs it. For when you know the move and just want it done.
That puts us at 19 tools covering stem separation through mastering.
Security
Every tool now validates inputs before touching files. Path traversal, malformed JSON in genre profiles, stack trace leakage: all handled. There’s a wrap_errors decorator running uniform error boundaries across all 19 tools.
Phantom runs locally on your machine with access to your audio files. That access should be locked down tight, and now it is.
Leaner codebase
The overengineering audit removed about 1,500 lines while adding 6,000 lines of new functionality. Server handler deduplication cut 400 lines of repeated patterns. Three nearly identical band detection functions became one. Five comparison module files consolidated into one.
883 tests pass. 57 files changed. Smaller codebase, more features.
How to update
Already have Phantom?
pip install --upgrade phantom-audioStarting fresh?
curl -sSL https://fadelab.net/install | bashThen tell Claude “analyze my mix” and see what happens.
What’s next
We’re working on a few things we’re not ready to share yet. The processing tools in this release are building toward something bigger.
Star the repo to follow along, or join the waitlist for Phantom Studio.