Skip to main content
Reagent is a desktop app that runs next to REAPER on the same computer. It works in your project through the Bridge, a small script inside REAPER. When your setup is ready, follow the Quick Start.

​
At a Glance

​
Operating System

UCS classification suggests Universal Category System categories for your sounds. The UCS Renamer skill uses it, so it has the same limit. Other audio analysis, such as finding silence and transients, doesn’t have this limit.
Leave extra free space. Updates (under 1 GB each) download before they install, and your chat history and attachments are stored on your computer and grow over time.

​
Permissions and File Access

  • File access. Reagent’s file tools only reach your home folder, REAPER’s Scripts folder, and external and network drives. Reagent doesn’t ask for Full Disk Access.
  • Folder prompts. macOS asks for permission the first time Reagent opens a file in your Documents, Desktop or Downloads folder, or on an external or network drive. Allow access so Reagent can work with the files you ask it to use there.
  • If you declined by mistake. Turn the folder, Removable Volumes or Network Volumes back on for Reagent in Files and Folders. File Access Problems shows where to find it.
For more, see File Operations, or File Access Problems if Reagent can’t reach a file.

​
REAPER

Reagent works with REAPER 7.0 or later.
  • Same computer, same user account. Reagent and the Bridge talk through files in your user folder, so Reagent can’t connect to REAPER on another machine.
  • REAPER open, Bridge running. Reagent’s REAPER tools only work while REAPER is open and the Bridge is running.
  • Bridge loaded once per computer. You load the Bridge into REAPER’s action list once per computer, then run it whenever you want Reagent to work in REAPER. The Quick Start shows how.
If your REAPER doesn’t use its default resource folder, such as a portable install, point Reagent at it after you install. See REAPER in a Custom Location.
Each time Reagent starts, it copies the Bridge script (reagent_bridge.lua and its helper json.lua) into a reagent folder in REAPER’s Scripts folder. Reagent uses the Scripts folder in REAPER’s default resource folder:
  • macOS: ~/Library/Application Support/REAPER/Scripts
  • Windows: %APPDATA%\REAPER\Scripts
After an app update changes the Bridge, Reagent shows Bridge Updated, but REAPER keeps running the old version until you quit and reopen it. Then run the Bridge again, or let your startup action run it. You don’t need to load it again.

​
SWS Extension

Reagent needs the free SWS extension (also called SWS/S&M) for REAPER. The Bridge uses it to identify the media items in your project.
Reagent doesn’t warn you when SWS is missing. Without it, Reagent can’t read the media items in your project and many REAPER steps fail, so install SWS before you connect Reagent to REAPER.
Quit REAPER before you install SWS. The Quick Start shows the steps, and SWS Extension Missing lists the symptoms.

​
Wwise (Optional)

You only need Wwise for Reagent’s Wwise features:
  • Wwise Authoring 2021.1 or later, on the same computer as Reagent.
  • The Wwise Authoring API (WAAPI) turned on, with its ports left at the defaults: 8090 (HTTP) for Reagent’s requests and 8080 (WAMP) for live mixing. Reagent connects to them on this computer, at 127.0.0.1.
See Wwise for setup.

​
Account and Internet Connection

  • Account. A Reagent account, and a web browser to sign in with.
  • Credits. Each request uses credits, and new accounts start with free trial credits. See Plans and Credits.
  • Internet connection. Reagent uses the internet for the following:
Reagent’s work in your REAPER and Wwise projects, its file tools, audio analysis and UCS classification run on your computer. What these tools find becomes part of the conversation that goes to the AI model. For every service Reagent connects to and what it sends, see Privacy & Security.

​
Enterprise Accounts

Reagent recognizes an Enterprise account from your company email domain. Reagent’s plans and credits don’t apply. Besides the requirements above, you need:
  • A model endpoint from your organization. OpenAI-compatible, over HTTPS (plain HTTP works only for a model server on your own computer), with an API key and a model with strong tool-calling support. See What the Endpoint Needs.
  • Network access. See Where Your Data Goes on Enterprise.
    • From each computer running Reagent: your endpoint, reaperagent.com, Reagent’s account database (hosted on Supabase) and GitHub (for updates).
    • From your browser, for SSO sign-in: WorkOS and your identity provider.
  • Endpoint setup on each computer. After you sign in, enter the endpoint in the Custom Endpoint window before you can chat. See Custom Endpoint.
  • Company sign-in, if your organization uses SSO. See Single Sign-On.
See the Enterprise Overview for everything else that differs.

Quick Start

Install Reagent, sign in, connect it to REAPER and send your first request.

Troubleshooting

Fix connection, SWS, file access and install problems.