overdub

The manuals.

Seven documents. A guide to your first session, then the ones the agents read: how an agent plugs in and how it behaves in the room, how to write an instrument or effect, how agents are scored by measurement, how claude.ai reaches a studio tab, and the contract every part of the studio is built against.

  1. The guide

    Your first overdub in five minutes, then the rest: bring your own Claude or Claude Code, build a device, share and fork a song, take it to another DAW, and the keys.

    14 sections, about 39 min, docs/GUIDE.md

  2. Overdub for agents (and their humans)

    How an agent connects (Claude Code over MCP to a local copy of the studio, the in-app agent with your own key, and the claude.ai connector to come), the rules of the room, every tool, the ops and the notes format.

    12 sections, about 44 min, docs/AGENTS.md

  3. Bring your agent to Overdub

    Step by step for Claude Code (the plugin or the MCP server alone), Claude Desktop, Cursor, VS Code and Codex, what has actually been tried, and what to do when it won’t connect.

    9 sections, about 8 min, integrations/README.md

  4. Devices: writing instruments and effects

    Instruments and effects as code: the kernel format, the dsp library, the device check a new device passes before it plays, the house library, and two complete examples.

    19 sections, about 33 min, docs/DEVICES.md

  5. OverdubBench

    Fifteen jobs a musician would ask an agent for (mix, write, edit, build a device), each scored 0 to 1 by measurement with the canonical renderer, never by a judge: the tasks, the scoring and how to run an agent.

    7 sections, about 10 min, docs/BENCH.md

  6. Remote MCP: claude.ai plays in your studio

    The relay that lets claude.ai drive a studio tab: pairing by URL, the protocol edges, limits, hosting, cost and the known gap.

    The relay is written and tested. The public one isn’t switched on yet, so the studio’s Connect tab stays hidden for now.

    9 sections, about 25 min, docs/REMOTE-MCP.md

  7. Overdub architecture (v0.1 contracts)

    The contract every module is built against: the song document, ops and the store, devices and kernels, the engine, the measurements, the UI and the agent layer.

    12 sections, about 92 min, docs/ARCHITECTURE.md

For agents reading this

The plain versions: llms.txt, and the Markdown itself at /docs/GUIDE.md, /docs/AGENTS.md, /docs/DEVICES.md, /docs/BENCH.md, /docs/REMOTE-MCP.md, /docs/ARCHITECTURE.md.