Create a plugin with an agent

In Studio, describe the instrument or effect you want and work with an audio agent to change its sound and controls. You can begin with an idea or an editable copy of an existing module. You do not need to write code to give the agent a musical brief.

Studio and parts of export are in early access. If a DAW plugin is your goal, include your DAW and operating system in the brief: a project that plays on the web does not by itself give you an installable plugin.

If Studio asks you to sign in, do that first. If your account is not authorized, choose Request Studio access; the request page shows its review status. Approval is separate from having a Maru account.

Describe what you want to create

Open Studio and tell the agent what someone should be able to do with your creation. Include the sound you have in mind, the controls that matter and where you want to use it. New module projects start with public visibility; review that setting before adding private material.

For example:

Create a delay effect for vocals. I want dark repeats that leave the original voice clear, with controls for time, feedback, tone and mix. I'd like to use it in my DAW.

You could also describe a playable bass instrument, a drum kit made from your recordings or a MIDI tool that turns chords into patterns. Naming the destination early helps guide the choice of tools and the eventual delivery path.

Build on something that inspires you

Browse modules or community modules, try an instrument or effect and imagine what you would change. Choose Edit a copy or Remix when offered to bring a starting point into Studio.

You might simplify an instrument for live performance, give an effect a different character or turn the starting idea into something entirely new. Remixing a module explains the available starting points and how to credit the work you build on.

Shape the sound and controls

Work with the agent as you would with a collaborator: explain what matters, try the relevant result and give specific feedback. For the vocal delay, that might be “make the repeats darker while keeping the voice clear” or “make the mix control easier to reach.”

Use playback when the project offers it to judge the sound, and look at the interface when you are changing how it feels to use. The agent works on an editable project that you or a developer can continue to refine.

Follow building an instrument or effect to develop the product further. If recordings are your starting material, use sampler bank creation; to connect existing tools, explore racks and patches.

Bring it into your workflow

Choose the route that matches what you want people to do:

• Make music in a DAW: prepare a supported plugin build, or bring audio, MIDI or a bank into a compatible application. Start with DAW integration.
• Add sound to a game: use prepared audio or explore the experimental Unity and Unreal effect integrations. Game audio and creative tools explains the paths.
• Let people play on a website: share an available module player or plan an integration into your own application's audio. See website embeds and integration.

If you cannot find the export or integration your project needs, contact Maru with its link, the intended application and operating system. Some destinations need local tools or a guided integration.

Create something for other people

You can develop your idea into a community release or a product for customers. Publishing and exports covers delivery, and selling on Maru explains the marketplace direction and early access.

For a connected instrument or app, explore Maru sign-in and generation inside your product. These can let people connect their account or request new sounds as part of the experience you design.

Developers who want to work directly with the project can continue with the Studio workflow reference.