Reaper Daemon. Nothing is listening.

Reaper Daemon

Drive REAPER from an AI agent. No socket, no server, no extensions.

The agent drops a JSON command file in a folder. A Lua script inside REAPER
runs it and writes a JSON result back. That is the whole protocol. It works
with Claude Code, Codex, Cursor, or anything else that can read and write
files, and an optional MCP server exposes the same bridge as tools for
Claude Desktop and other MCP clients.

macOS, Windows, Linux. Pure Lua inside REAPER, plain Python 3 outside, no
pip packages. Every change runs inside a REAPER undo block, so Ctrl+Z
reverts anything an agent does.

Install

git clone https://github.com/wretcher207/reaper-daemon.git
cd reaper-daemon
python3 setup/install.py

Restart REAPER, then check the bridge is alive:

python3 reaperd.py status

Prefer ReaPack, or want to load the bridge by hand? See docs/install.md.

What it does

Area	Commands
Project	transport, tempo, cursor, time selection, render, save
Tracks	add, delete, rename, select, volume, pan, mute, solo, arm, color
Routing	read sends and receives, create sends, toggle master feed
FX	add, remove, bypass, reorder, set parameters, write automation, save chains
Markers, regions, media items	full read and write
MIDI	insert MIDI files, plus a drum DSL with humanization
Guitar and bass	`shred` renders a humanized riff, `band` cuts a whole rhythm section
Discovery	`scan_fx` dumps every plugin and parameter; `discover_drum_map` reads any kit's note map
Verify	measure loudness, spectrum and dynamics before and after a mix move

The bridge knows nothing about any specific plugin or drum library. Agents
discover what a project contains and act on it by name.

Three ways to talk to it

CLI. One Python entry point for everything an agent does.

python3 reaperd.py send commands/examples/get_context.json --wait
python3 reaperd.py shred --track argent-l --bars-file riff.txt --seed 101

MCP server. reaper_mcp.py wraps the bridge as tools over stdio.
Ask Claude Desktop to "measure the drums" and it does.

Daemon Console. A chat panel docked inside REAPER, backed by a headless
Claude Code session that always knows which track you have selected.

Docs


Install	one-line installer, ReaPack, manual load
CLI	`reaperd.py` reference
MCP server	setup for Claude Desktop and other clients
Daemon Console	the in-REAPER chat panel
Drums	kit discovery, stem profiling, humanize
Guitar and bass	`shred` and `band`
Verify	closed-loop mix moves with measured proof
Protocol	the file wire format
Troubleshooting	silent captures, stale heartbeats
Security	trust model and the optional token
Develop	tests, CI, repo layout

Agents should read AGENTS.md, CLAUDE.md, and
bridge/command_schema.md. Two bundled skills,
arrangement-midi and
drum-humanize, cover MIDI composition and
drum humanization.

Security

Any process that can write to inbox/ can drive REAPER. Keep the bridge
folder local and off shared drives. Details in docs/security.md.

License

MIT. See LICENSE.