# Studio workflow

> Create with an agent, edit live, save a revision and prepare a supported release.

Canonical: https://maru.audio/docs/studio-workflow
Documentation index: https://maru.audio/llms.txt

Maru Studio is the editing environment for audio tools. Start with an idea or
an existing module, describe a change, play the result and keep refining it.
The agent operates a real project that developers can also inspect and edit.

> **In the Help Center:** [Create a plugin with an agent](https://maru.audio/help/studio-quick-start.md) for a short walkthrough without code.

For sample-based instruments, follow [Create a sampler bank](https://maru.audio/docs/sampler-banks.md)
to upload sounds, map keys or pads, save versions and export a playable bank.

## Web and local editing

The **web Studio** centers on agent chat and hosted projects. It brings
modules, sampler instruments, MIDI banks and racks into their editing context.
Module source, graph and interface views support different parts of the same
project. [Open Studio](https://maru.audio/studio) with your beta account.

The **desktop Studio** is the local editing surface for module folders and
the local toolchain. It provides workspace tabs, an agent and live module
preview. Developer access and setup are part of the selected-developer beta.
Both editors have preview/reload functionality; their features and target
access are still being brought together.

## From idea to release

1. Choose an existing module or the content type you want to create.
2. Describe the sound, musical behavior and controls. Change one clear aspect
   at a time, audition it, and steer the next edit.
3. Save your work. A draft preview, a saved revision and a built release are
   different states; keep track of which one you are hearing.
   [Projects, library and saved work](https://maru.audio/help/projects-and-library.md)
   explains what each one keeps.
4. Check the sound, parameter behavior, presets, assets and intended host.
5. Prepare the listing and build the formats available for that project.
6. Review and publish through the current beta workflow.

For example: “Make a short stereo delay that stays clear on vocals. Give me
time, feedback, tone and mix controls, with a simple repeat display.” Start
from a suitable effect and use listening feedback to refine its character.

## Current limits

Studio is early software. Existing live reload does not mean every project
supports seamless audio-state transfer, every editor operation or every native
format. Some release steps remain guided. Availability depends on the module,
runtime and build environment, and a preview alone does not qualify a release.

Use [Project structure](https://maru.audio/docs/project-structure.md) for source ownership,
[Publishing](https://maru.audio/docs/publishing.md) for preparation, and [Check, build and export](https://maru.audio/docs/export.md)
for target selection. Developers can continue with the [Audio SDK](https://maru.audio/docs/audio-sdk.md)
and [Working with coding agents](https://maru.audio/docs/working-with-coding-agents.md).