An official scripting module lets local scripts send commands to Audacity through a named pipe. A separate agent script or bridge is required. For Claude Code, 1 route is explicitly documented by the integration maintainer.
Local scripting interface; an agent-specific client script or MCP bridge is required.
Requirements and limitations
Audacity with mod-script-pipe enabled and a local client script in a language that supports named pipes.
The scripting interface supports one project at a time, and commands can vary by version. Connecting an agent requires a local client script or bridge.
Audacity 4, Node.js 20 or later, and the project native engine; optional FFmpeg for additional formats.
File processing is separate from control of an open editing session. Platform-specific native builds and the optional extension have separate requirements.
Audacity 4, Node.js 20 or later, and the project native engine; optional FFmpeg for additional formats.
Can Claude Code control all of Audacity?
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Which setup should I use?
Choose a route that explicitly documents Claude Code and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.