Skip to main content
Find your problem below and try the fixes in order. Most REAPER problems come from the Bridge, a small script that runs inside REAPER and carries out Reagent’s commands.

​
REAPER Connection Problems

Reagent has no connection light. It checks REAPER each time you send a message, so to check the connection, ask:
If REAPER isn’t connected, Reagent can’t use it for the rest of that reply, even if you start the Bridge meanwhile. Fix the connection, then send your message again. When a REAPER step fails, the chat shows a short message, and Show details shows the underlying error.
Try these in order, sending your message again after each.
  1. Open REAPER. Any project works.
  2. Run the Bridge. In REAPER, choose Actions > Show action list…, type reagent in the Filter box, select Script: reagent_bridge.lua and click Run. Not listed? Load it first (see the next item). The Bridge stops when REAPER quits, so run it each time, or start it automatically.
  3. Close any dialog box in REAPER, such as a save prompt. While REAPER waits for an answer, the Bridge can’t respond.
  4. Deselect all media items and ask again. If Reagent now says REAPER is connected, the SWS extension is probably missing. See SWS Extension Missing.
  5. On Windows, check the HOME environment variable. If HOME points anywhere other than your user folder (%USERPROFILE%), Reagent and the Bridge can’t see each other, because the Bridge looks there for the .reaper-mcp folder Reagent uses. Set HOME to your user folder (or remove it if nothing else needs it), then restart REAPER. Not sure how? Ask your IT team, or see Still Not Working.
Typing reagent in the Filter box finds nothing until you load the Bridge once on each computer. Reagent copies it into the reagent folder inside REAPER’s Scripts folder:No reagent folder? Your REAPER may use a different resource folder. See REAPER in a Custom Location.
1

Load the script

In REAPER, choose Actions > Show action list…, click New action… > Load ReaScript…, select reagent_bridge.lua in the folder above and click Open.
2

Run it

Select Script: reagent_bridge.lua and click Run. The Bridge runs in the background, with no window.
The Bridge files aren’t in REAPER’s Scripts folder, usually because Reagent couldn’t copy them. Click Setup to open Device Setup, which copies the files and walks you through loading and running the script.Or open Settings > Connectors (Cmd+, on macOS, Ctrl+, on Windows). Under REAPER Bridge, click Install if the status says Script Not installed, or Reinstall (download icon) if it says Script Installed but you think the files are damaged.Reagent also copies any missing files each time it starts. Then restart the Bridge: quit and reopen REAPER, then run the script, or let it start automatically.
Reagent copies the latest Bridge into REAPER’s Scripts folder each time it starts. If that changes the Bridge, you see Bridge Updated, but REAPER keeps running the old version until you restart the Bridge.Quit and reopen REAPER, then run the script, or let it start automatically. You don’t need to load it again.
This ReaScript task control prompt means the Bridge is already running, for example because it started automatically.
  • Click Abort. The running Bridge carries on.
  • Don’t choose New instance, and don’t save that answer with Remember my answer for this script. Two Bridges would carry out every command, so every change would happen twice.
  • Terminate instances stops the Bridge. If you chose it, run the script again.
  • To restart the Bridge, quit and reopen REAPER, then run the script once, or let it start automatically.
Two Bridges are running: you chose New instance when REAPER asked, or the Bridge runs in two open copies of REAPER. Quit every copy of REAPER, open one, and start the Bridge once.
The Bridge didn’t answer within 30 seconds, the limit for most steps. REAPER may be showing a dialog box, or the Bridge or REAPER stopped.Close any REAPER dialog and check that the Bridge is running. The step may still run once the dialog closes, so check your project before retrying.
The Bridge got the command, but it failed inside REAPER. If the details mention BR_GetMediaItemGUID or SWS, install SWS. Otherwise, read the details or ask Reagent what went wrong.
Reagent couldn’t pass the command to the Bridge. Restart Reagent. If it keeps happening, see Still Not Working.

​
SWS Extension Missing

Reagent needs the SWS/S&M extension, which the Bridge uses to identify media items. Reagent doesn’t warn you when SWS is missing. Instead, you see one or more of these:
  • Requests that read or change media items fail with REAPER rejected the operation, and the details mention BR_GetMediaItemGUID or “SWS Extension required for GUID-based lookup”.
  • While any media item is selected, many other REAPER steps fail too, including the connection check when you send a message, so Reagent can say REAPER isn’t connected even though the Bridge is running.
1

Quit REAPER and install SWS

Quit REAPER, then download SWS for your platform from sws-extension.org and follow its install instructions.
2

Check that SWS loaded

Open REAPER, choose Actions > Show action list… and type SWS in the Filter box. Actions starting with SWS/S&M: mean SWS is installed.
3

Start the Bridge

Run the Bridge, or let it start automatically, then send your message again.

​
REAPER in a Custom Location

If your REAPER uses a resource folder other than the default, such as a portable install, point Reagent at it. Otherwise Reagent installs the Bridge, and its updates, in a folder your REAPER doesn’t use. The default resource folder is ~/Library/Application Support/REAPER on macOS and %APPDATA%\REAPER on Windows.
1

Find REAPER’s resource folder

In REAPER, choose Options > Show REAPER resource path in explorer/finder…. That folder, which contains Scripts, is the one you need. On Windows, it usually isn’t the reaper.exe folder, unless REAPER is portable.
2

Change the path in Reagent

Open Settings > Connectors. To open Settings, press Cmd+, on macOS or Ctrl+, on Windows, or click your name at the bottom of the sidebar and choose Settings.Under REAPER Bridge, REAPER path shows the Scripts folder Reagent uses now. Click the folder button (Change path) next to it, select the resource folder or its Scripts folder, and confirm. If the folder you pick contains Scripts, Reagent uses that.
3

Check the result

Reagent immediately removes the Bridge from the old folder and installs it in the new one. REAPER path shows the new Scripts folder, and the status says Script Installed.
4

Load the Bridge from its new location

In REAPER, load Scripts/reagent/reagent_bridge.lua with New action… > Load ReaScript… and run it. See Quick Start.

​
Wwise Connection Problems

For setup steps, see Wwise.
  1. Open Wwise 2021.1 or newer on the same computer as Reagent, with your project loaded.
  2. In Project > User Preferences, turn on Enable Wwise Authoring API (WAAPI), then restart Wwise.
  3. Use the default WAAPI ports that Reagent connects on, 8090 (HTTP) and 8080 (WAMP). If you changed them, set them back.
  4. Wait up to 30 seconds (Reagent remembers the last Wwise check that long), then send your message again.
The failed step shows Something went wrong, and Show details or Reagent’s reply says “WAAPI call timed out”. Wwise is probably waiting on a dialog box. Close it, then ask Reagent to try again.
Reagent works with Wwise 2021.1 or newer. Open your project in a newer version of Wwise.

​
File Access Problems

macOS asks the first time Reagent opens files in a protected folder, such as Documents, Desktop or Downloads. Allow it, so Reagent can read the files you ask about.If you denied access earlier, turn the folder on for Reagent in System Settings > Privacy & Security > Files and Folders (macOS 12: System Preferences > Security & Privacy > Privacy > Files and Folders), then try again.
Reagent’s file tools (find, read, move, copy and rename files, and create folders) only work in:
  • Your home folder.
  • REAPER’s Scripts folder.
  • On macOS, anything under /Volumes, such as external drives.
  • On Windows, drives other than the system drive (usually C:), and network shares such as \\NAS\Audio. Admin shares, whose names end in $, don’t work.
Anywhere else, the step shows Something went wrong and Show details says “Path is outside the allowed roots”, whatever your macOS privacy settings. Move or copy the files into one of these places, then ask again. See File Operations.

​
Chat Problems

  1. Send your message again.
  2. Check your internet connection.
  3. If it keeps happening in the same chat, start a new one (New chat, Cmd+N or Ctrl+N).
  4. Quit and reopen Reagent.
  5. Check your organization’s endpoint: see Enterprise Endpoint Errors.
  1. Check whether Reagent is waiting for you. If a pause symbol shows where Reagent is working and a card replaces the message box, Reagent needs you to approve a change or answer a question. Allow, deny or answer it.
  2. Check REAPER for an open dialog box. REAPER steps wait up to 30 seconds for an answer.
  3. Stop the reply with the stop button (Cancel request) or Esc. Stopping doesn’t undo changes already made, so check your project before sending your message again. See Chat.
  • Large projects: Requests that read every track or item take longer. Select the tracks or items you mean and say “the selected items”.
  • Many steps: Reagent sends REAPER one command at a time, so many-step requests take longer.
  • Model speed: Replies come from an AI model through Reagent’s service, so a slow connection slows every reply.
  • Your organization’s endpoint: On Enterprise accounts, replies come from your organization’s endpoint, which can be a model server on your own computer. A slow connection, busy endpoint or slow local model slows every reply.
A step that uses Reagent’s online services, such as a REAPER API search, a Wwise documentation lookup or sending feedback, got an error. Wait a moment and ask again. If it keeps happening, check your internet connection, or see Still Not Working.
You’ve run out of credits. The chat shows a Buy Credits, Upgrade Plan or Manage Subscription button, depending on your plan. See Plans and Credits.
“Temporarily rate limited. Please try again in a moment.” doesn’t mean you’re out of credits. Wait a moment, then send your message again.

​
Enterprise Endpoint Errors

When your organization’s AI endpoint has a problem, you see one of the errors below. Quota and rate-limit errors from your organization’s provider also appear here as endpoint errors, never as credit messages. For every endpoint setting, see Custom Endpoint.
Reagent needs a working endpoint before you can chat. Enter the details from your IT team and click Apply. Reagent tests the endpoint first and shows any error under Apply. The window’s only other option is Sign out.
Check that you’re on your organization’s network or VPN, and that the Endpoint URL in Settings > Endpoint is right.
The message goes on with a status code and the endpoint’s message, for example “…returned 401: …”. Your endpoint refused the request.Read the hint under the message, if any. Click Endpoint response to see what it sent back, and share that with your IT team.
These features aren’t available on Enterprise accounts, so this is expected:
  • Transcribing or translating dialogue. A dialogue step can fail with “No transcription data found”.
  • Searching the REAPER API or Wwise documentation online.
  • Sending feedback.
See Feature Availability.

​
Reagent Won’t Install on Windows

If opening the Reagent installer shows Windows protected your PC, Microsoft Defender SmartScreen has stopped an app it doesn’t recognize. To continue:
1

Click More info

Windows protected your PC dialog from Microsoft Defender SmartScreen, with the More info link highlighted
2

Check the app, then click Run anyway

Check that App shows the installer you downloaded from reaperagent.com/download, named like reagent-<version>-setup.exe. Then click Run anyway.
The same SmartScreen dialog after clicking More info, showing the app name and the Run anyway button highlighted
No Run anyway button? A Windows security setting or your organization’s policy is blocking the installer. Ask your IT team, or contact support.

​
Classifying Sounds on an Intel Mac

On an Intel Mac, the Classify items step and the UCS Renamer skill’s classification step fail. On macOS 12 or 13, classification isn’t supported. UCS (Universal Category System) classification runs on your computer and, on a Mac, needs Apple silicon and macOS 14 (Sonoma) or later. Windows isn’t affected. See Audio Analysis.

​
Still Not Working

1

Install any waiting update

A download-arrow button appears in the title bar once an update is ready. Click it to install the update, then check whether the problem remains.
2

Gather the details

Note your Reagent and REAPER versions and the other details listed in Get Help. For errors and crashes, add the relevant lines from Reagent’s log file, main.log:To open the folder, paste its path into Finder’s Go > Go to Folder… on macOS, or into the File Explorer address bar on Windows.
Logs can include file paths and project details. Read the lines before you paste them, and remove anything you don’t want to share.
3

Tell the Reagent team

Use the contact form at reaperagent.com/contact. It works for every account and doesn’t need you to sign in.
  • Send Feedback: click the speech bubble icon in the title bar, or ask Reagent to send a bug report. See Get Help.

Quick Start

Install Reagent, sign in and connect it to REAPER.

System Requirements

Check your computer, REAPER setup and network.

Settings

Manage the REAPER Bridge under Connectors.

Get Help

Pick the right place to get help, and what to send.