Help

Publishing and exporting

Publish a plugin from the terminal or your coding agent

Everything Publish a plugin does on the website, from the maru command line: detect the framework, let Maru build your project, read the health checks and publish a release. Claude Code, Codex and other MCP clients can do the same for you.

Yes. Run maru publish in your plugin's folder. It works out what the project is with the same detector as Publish a plugin, uploads nothing, and offers the same three routes:

  • Let Maru build your project (--route project), for NIH-plug and DPF source.
  • List the releases you build (--route releases), for JUCE and any plugin you already build in your own CI. See List a plugin built with another framework.
  • Publish a Maru module (--route module), if you port it to Maru.

Install the command line with npm i -g maruaudio (or use npx maruaudio) and sign in once with maru login.

Let Maru build it

sh
maru publish --route project

Maru packs the folder exactly as the website does, leaving out .git, node_modules and build output, uploads it once, and reads it. It then shows the framework, plugins, formats and recipe it found and stops: nothing builds until you confirm. To build, name the recipe and platform it offered:

sh
maru publish --route project --recipe nih-plug-xtask/1 --platform linux-x64 --plugins gain

The command follows the build and prints, for each plug-in bundle, its health checks as Passed, Warnings, Failed, Incomplete or Not run, with a hint for each failure and the command to run the same checks on your computer (maru plugin check). A check that didn't run is never shown as passed. The checks measure whether the plugin loads, renders finite, audible output and handles parameter changes; they don't judge how it sounds. Each build also has its page under Your builds.

The same steps are available one at a time: maru build preview, maru build create, maru build status, maru build logs, maru build cancel, maru build allowance and maru build history. During the beta each account has 60 build minutes a month (UTC), counted from when a builder takes a build to when it ends; a cancelled build counts only the time it ran, and detecting a project doesn't use minutes. maru build allowance shows what is left and when it resets. A public GitHub repository works too: maru build preview --repository owner/name --ref v1.0.0.

Publish the build as a release

sh
maru release check <build>
maru release publish <build> --release-version 0.1.0 --notes "First release."

maru release check shows the same checklist as the build page: a profile handle, at least one download and release notes are needed; a licence and passing health checks are recommended. The release appears on your plugin's page, and Maru Desktop can install it. Builds stay unsigned until Maru signs them after review.

Ask your coding agent

Tell Claude Code, Codex or another agent "publish this plugin on Maru" in the project folder. With the Maru skill (maru skill install) or the Maru MCP server (maru mcp install), it runs the steps above, shows you what Maru found before building, reads the health checks and asks you for release notes. Copy for your agent on Publish a plugin gives it the same steps as text. Agents connected to your Maru account at /mcp can build from a public GitHub repository; building a folder on your computer needs the command line or maru mcp.

When something goes wrong

Every refusal says what to do next and ends with a short code in brackets, such as [rate_limited] or [juce_licence]. A failure on Maru's side says nothing in your project needs to change; build again. Your inbox tells you when a build or detection finishes, and you can also get an email for it: turn on Hosted build results in your notification preferences.