Skip to main content
Most REAPER problems come from the Bridge. Sign-in doesn’t finish? See 2. Sign In.

​
Reagent Won’t Install on Windows

If 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 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
Or right-click the -setup.exe file, choose Properties and select Unblock under Attributes. No Run anyway button? A Windows security setting or your organization’s policy is blocking the installer. Ask your IT team, or contact support.

​
REAPER Connection Problems

To check the connection, ask Is REAPER connected? Reagent checks REAPER each time you send a message. If REAPER isn’t connected then, Reagent can’t use it for the rest of that reply, even if you start the Bridge meanwhile. After any fix, send your message again. To restart the Bridge, quit and reopen REAPER, then run the script, or let it start automatically.
Try these in order.
  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? See the next item.
  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, SWS is probably missing. See SWS Extension Missing.
  5. On Windows, check the HOME environment variable. If it points anywhere other than your user folder (%USERPROFILE%), set it to your user folder (or remove it if nothing else needs it), then restart REAPER. Not sure how? Ask your IT team.
REAPER lists the Bridge only after you load it once on each computer. Follow Quick Start step 4. No reagent folder in REAPER’s Scripts folder? See REAPER in a Custom Location.
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, in Settings > Connectors 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. Then restart the Bridge.
Reagent copied a new version of the Bridge into REAPER’s Scripts folder, but REAPER keeps running the old one until you restart the Bridge. 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, and the running Bridge carries on. Never choose New instance or save that answer with Remember my answer for this script: two Bridges carry out every change twice. Terminate instances stops the Bridge, so if you chose it, run the script again.
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 doesn’t warn you when SWS is missing. Instead:
  • 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.
To fix it:
  1. Quit REAPER, then install SWS from sws-extension.org, following its instructions for your platform.
  2. 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. 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. In Settings > Connectors, under REAPER Bridge, click the folder button (Change path) next to REAPER path. Select the resource folder or its Scripts folder, and confirm. Reagent immediately removes the Bridge from the old folder and installs it in the new one. REAPER path then shows the new Scripts folder, and the status says Script Installed.
  3. Load the Bridge from its new location. In REAPER, load Scripts/reagent/reagent_bridge.lua with New action… > Load ReaScript… and run it.

​
Silent Renders and Offline Media

With REAPER’s default preferences, REAPER takes your project’s media offline and closes its audio device whenever it isn’t the app in front and isn’t playing. While you chat in Reagent, it never is. Reagent brings the media online before it reads or renders it, and starts the audio device before it records, so you don’t need to change these preferences. Some of this needs Bridge v0.1.5 or newer: after Reagent updates, click Restart bridge in the Bridge Updated notification.
When every file a render made is silent, Reagent reports RENDER_SILENT instead of success and keeps the files. When only some are, it names them. Check the rendered items in REAPER: muted tracks or items, a track whose master send is off, an empty time selection, or media set offline.
Restart the Bridge so REAPER runs the updated script. An older Bridge reads media REAPER took offline in the background as empty.
When Reagent renames, moves or overwrites a file your project uses, or writes metadata to it, REAPER takes those items offline for a moment, then brings them back. Renamed or moved items then point at the new path. If Reagent quit or lost REAPER partway through, the items come back on their own shortly. To bring them back at once, run Item: Set all media online from REAPER’s action list.
Reagent doesn’t change a file while a project that uses it is playing, paused or recording. Stop REAPER’s transport and ask again.

​
Wwise Connection Problems

For setup steps, see Wwise.
  1. Open your project in Wwise 2021.1 or newer, on the same computer as Reagent.
  2. In Project > User Preferences, turn on Enable Wwise Authoring API (WAAPI), then restart Wwise.
  3. Keep the WAAPI ports at their defaults, 8090 (HTTP) and 8080 (WAMP). If you changed them, set them back.
  4. Wait up to 30 seconds (Reagent reuses its last Wwise check for that long), then send your message again.
Wwise is probably waiting on a dialog box. Close it, then ask Reagent to try again.

​
File Access Problems

Allow it, so Reagent can read the files you ask about.If you denied access earlier, turn the folder, Removable Volumes or Network Volumes back 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 only work in certain folders, whatever your macOS privacy settings. Move or copy the files there, then ask again.

​
Chat Problems

The full message is “Something went wrong while generating a response. Please try again.”
  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 Custom Endpoint troubleshooting.
  1. Reagent may be waiting for you. If a card replaces the message box (with a pause symbol where Reagent is working), 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 you send again. See Stopping a Reply.
  • 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: A slow connection, a busy endpoint or a slow model server on your own computer 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.
You’re out of credits. Use the Buy Credits, Upgrade Plan or Manage Subscription button on the card, or see When You Run Out of 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

The Custom Endpoint window stays open until an endpoint passes the test (Connect Your Endpoint). For endpoint errors, such as “Can’t reach your organization’s model endpoint” or “Your organization’s model endpoint returned …”, see Custom Endpoint troubleshooting.
These features aren’t available on Enterprise accounts:
  • 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.

​
Classifying Sounds on an Intel Mac

Classify items and the UCS Renamer skill’s classification step fail on an Intel Mac and on macOS 12 or 13. Windows isn’t affected. See System Requirements.

​
Still Not Working

  1. Install any waiting update with the download-arrow button in the title bar, then check whether the problem remains.
  2. Send the details listed in What to Include through the contact form. 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.