Reagent connects to REAPER through a Lua Script Bridge, giving you full control over your projects through natural language. This page covers what you can do and how it works.
How It Works
The Bridge is a script that runs inside REAPER and listens for commands from Reagent. When you send a message:
- Reagent figures out what you want to do
- Sends commands to REAPER through the Bridge
- REAPER executes the commands
- Results come back to Reagent
All operations are wrapped in undo blocks, so you can always undo any changes with Cmd/Ctrl + Z in REAPER.
Reagent has access to a set of specialized tools for interacting with REAPER. You don’t need to know the tool names—just describe what you want in plain language and Reagent picks the right tools automatically.
These tools read information from your project without making changes.
These tools make changes to your project.
These tools analyze audio content within your REAPER project.
REAPER Subagent
For complex multi-step tasks, Reagent can delegate work to a specialized REAPER subagent. The subagent focuses exclusively on executing REAPER operations — analyzing items, editing, classifying content — while Reagent handles the higher-level planning.
When a subagent is working, you’ll see a live activity view in the chat showing each step as it runs. The subagent executes tools sequentially to ensure reliable results, and all changes remain undoable in REAPER.
You don’t need to do anything special to use the subagent — Reagent decides when delegation is appropriate based on the complexity of your request.
Limitations
Some things aren’t possible through scripting:
- Operations requiring modal dialogs
- Real-time monitoring
If something isn’t possible, Reagent will explain why and suggest alternatives.
Modal dialogs or popups in REAPER will block Reagent until dismissed.
