# Working with coding agents

> Turn a musical brief into a working audio tool without becoming a plugin-framework specialist.

Canonical: https://maru.audio/docs/working-with-coding-agents
Documentation index: https://maru.audio/llms.txt

Maru is designed for a coding agent to handle most of the technical
loop while you direct the product. Start with a working project, explain the
sound and interaction you want, and judge each meaningful change in the
development workbench.

> **In the Help Center:** [Use Maru with an assistant](https://maru.audio/help/using-maru-with-agents.md) for working with an assistant without code.

You do not need to learn C++, JUCE, native plugin plumbing, or a separate DSP
language before making something useful. Basic comfort opening a project and
talking to a coding agent is enough to begin.

For hosted agent chat and the desktop editor, start with the
[Studio workflow](https://maru.audio/docs/studio-workflow.md). This guide explains the collaboration
loop and connecting an external coding agent to a local project.

Install the [Maru agent skill](https://maru.audio/docs/skills.md) for reusable plugin, sample-kit,
bank and inference workflows. The skill guides the agent; the `maru` CLI
supplies the tools.

## Your part

You bring the decisions that make the tool worth using:

- the musical problem or creative idea;
- the few controls that should feel immediate;
- references for sound, movement, and visual character;
- listening feedback and the final call on what feels right.

The agent can handle graph assembly, parameter wiring, interface code, tests,
validation errors, build commands, and supported release bundles.

## A productive loop

1. Create a project with `maru init`, or open the closest example.
2. Ask the agent to read `https://maru.audio/llms.txt`, run `maru doctor` and
   inspect the project.
3. Describe one musical outcome and a simple interface direction.
4. Let the agent make a small working pass, then listen in the workbench
   (`maru dev`).
5. Respond in product language: darker, wider, less busy, faster to understand.
6. Ask the agent to run `maru module check` and build the supported outputs.

The workbench keeps this collaborative. You can hear the graph, move the real
controls, inspect visual feedback, and send any error directly back to the
agent. The code remains available when you want to inspect or change it, but
code is not the only useful way to participate.

## Connect your agent

Install the agent skill with `npx maruaudio skill install`. For an agent or
editor that speaks the Model Context Protocol, `maru mcp` serves the same
operations as MCP tools, so the agent chat in Studio, the CLI and your MCP
client all work on the project the same way. `npx maruaudio mcp install --both`
registers it with your coding agents, together with the hosted connector for
your Maru account. [Use Maru from your agent](https://maru.audio/docs/agent-setup.md) explains which
pieces you need.

## A prompt that leaves room for judgment

```text
Read https://maru.audio/llms.txt and inspect the starter already open.

Build a playable stereo delay that feels warm and immediate. Keep the main
interface to Time, Feedback, Tone, Width, and Mix. Add a clear tap visualization
and make the layout feel like a finished musical tool, not a settings panel.

Let me hear each meaningful pass in the workbench. Run maru module check and
build every target supported by this project before you finish.
```

Start with the [Quickstart](https://maru.audio/docs/quickstart.md). The [CLI overview](https://maru.audio/docs/cli.md)
explains the commands the agent runs behind the scenes.