Skip to main content
Reagent works on your REAPER and Wwise projects on your computer and sends your conversation to an AI model. On individual plans (free trial, Lite, Pro and Pro+), that’s Reagent’s hosted AI.

What Stays on Your Computer

  • Audio analysis and UCS classification. Both run on your computer, and the classification model ships with Reagent. The AI model receives the measurements and category labels, not the audio.
  • REAPER and Wwise connections. The Bridge exchanges commands with Reagent through files on your computer. Reagent reaches Wwise Authoring through WAAPI on this computer.
  • Chat history. Your chats, and a copy of each image, PDF and text file attached to them, are saved in Reagent’s data folder on this computer. They aren’t stored in your Reagent account and don’t sync to your other computers.
  • Slash commands and settings. Both are saved as files on this computer.
Signing out doesn’t delete your chats. Anyone using the same macOS or Windows user account on this computer can see them in Reagent, even when signed in to a different Reagent account.
To remove chats, open a chat’s ⋯ menu in the sidebar and choose Delete or Clear all. Deleted chats can’t be restored. Reagent removes their saved attachment copies the next time it starts.

What the AI Model Receives

With each message, the AI model receives:
  • Your conversation. Your message, the earlier messages in the chat, and the files you attached.
  • Your REAPER session. The project name, its track and item counts, the cursor position, time selection and selected tracks, any tracks that use fixed item lanes, and up to five selected items with their names (or file names), tracks, positions and lengths. A larger selection is sent as a count.
  • Working memory. A one-line summary of what Reagent holds for this chat: how many items, up to three source file names, and what it has analyzed.
  • Your Wwise connection. When Wwise is connected, its version and up to 10 selected Wwise objects, each with its name, type, path in the Wwise project and ID. While Wwise is connected to a running game, the number of selected objects instead of their details, plus the game’s name and the Profiler capture status. See What Reagent Sends.
  • Tool results. Results from Reagent’s tools, such as track and item lists, audio measurements, classification labels, transcripts, the text of files Reagent reads for you, and Wwise project data.
File paths and track names often include client or project names, so the model sees those too.

Connections on Every Plan

  • Sign-in and your profile. You sign in on reaperagent.com in your web browser, not inside the app. Your email address, display name and welcome-question answers are stored in Reagent’s account database, hosted by Supabase. The app loads your profile and account status from it, and stays connected to it for account updates while it runs. The reaperagent.com website has its own analytics, described in the Privacy Policy.
  • Updates. Each time Reagent starts, it checks GitHub for a new version, downloads it and installs it when you quit. There’s no setting to turn this off.
  • Release notes. After an update, Reagent fetches the release notes from reaperagent.com. The request contains only version numbers.
  • Analytics settings. When Reagent starts, its analytics library loads its settings from PostHog.
    • On Enterprise accounts, it uses an anonymous ID and doesn’t send usage events or session recordings.

Security Controls

Your permission mode decides what Reagent does without asking. Permission modes don’t cover every request that sends data to a service. On individual plans, dialogue transcription and documentation searches run without asking in every mode. Reagent’s file tools work only in your home folder, REAPER’s Scripts folder and external or network drives, and refuse other locations. External or network drives are drives under /Volumes on macOS and, on Windows, any drive other than the system drive, plus network shares. This limit covers those file tools only. Reagent’s audio tools work on the audio files they’re given, and scripts Reagent runs in REAPER have REAPER’s own access to your computer. In Default permissions and Auto-review modes, Reagent asks before it runs a script. When Reagent opens a file on your computer for the chat, it reads text files only and refuses audio, images and other binary files.

Individual Plans

Each AI request goes from the app to Reagent’s server at reaperagent.com, hosted on Vercel. The server passes it through the Vercel AI Gateway to the model for that job:

Dialogue Transcription

The automatic dialogue editor transcribes the items you select. Transcription doesn’t run on your computer:
  1. Reagent compresses the part of each source file that the item plays.
  2. It uploads that clip to its private temporary file storage, hosted by Supabase.
  3. Reagent’s server asks ElevenLabs to transcribe the clip. ElevenLabs downloads it through a temporary link that expires after five minutes.
  4. Reagent’s server normally deletes the clip after transcription. As a safeguard, a cleanup job deletes anything in temporary storage that’s more than an hour old.
The transcript comes back to your computer and becomes part of the conversation. To find takes and translate lines, Reagent’s server sends the transcript text, not the audio, to Gemini.

Documents You Attach

Attaching a PDF, TXT, CSV, TSV, Word or Excel file also uploads a copy to the same temporary storage, so the dialogue editor can use it as a script. When the dialogue editor uses it, Reagent’s server turns the file into text (Gemini reads PDFs) and sends that text to Gemini with the transcript. The same one-hour cleanup applies.

Documentation Searches

REAPER API search (in the ReaScript API documentation) and the Wwise subagent’s lookups in the Wwise documentation send search text to reaperagent.com. Reagent writes this text from your request. Reagent’s server sends it to Voyage AI to find matching documentation. For REAPER API search, the request contains the search text Reagent writes, such as “get item fade length”, and search settings such as how many results to return. It doesn’t include your project file or your script’s code. For Wwise lookups, see What Reagent Sends.

Feedback You Send

When you use the Send Feedback button in the title bar, or ask Reagent in a chat to pass on feedback, Reagent sends these through reaperagent.com to the Reagent team:
  • The subject and message.
  • Your display name (or your email address if you haven’t set one) and your email address.
  • Your app version and operating system.
  • For feedback from the title-bar form, the category you picked: Bug Report, Feature Request or General.
It doesn’t attach your chat history. When you ask in a chat, the message describes what happened in the chat, so it can include details such as track or file names. Reagent asks you to approve that message before sending it, unless you use Full access mode.

Usage Analytics

To understand how the app is used, Reagent sends usage events and session recordings of the Reagent window to PostHog, once it confirms that your account isn’t an Enterprise account. Examples of usage events:
  • The screens you open and the buttons you click.
  • When you send a message, and how many files it has.
  • Which tools Reagent ran, how long they took and whether they worked.
  • Errors, your app version and your operating system.
  • The category and subject line of feedback you send from the title bar.
These events are linked to your account, including your email address, display name and your answers to the welcome questions. Reagent’s server also records the model, token counts and timing of each AI request, for billing and analytics.

Billing

Your plan and credit balance are stored in Reagent’s account database, and Reagent records the credits each request uses. Polar handles subscriptions and billing, and Stripe processes card payments for Polar. See Plans and Credits.

Model Training

Reagent’s Privacy Policy states that Anthropic, ElevenLabs and Google don’t use API inputs or outputs to train their models. That statement names only those three providers. For every service that receives data, including Vercel and Voyage AI, see Subprocessors.

Enterprise Accounts

Your account is an Enterprise account when its email address is at a domain Reagent’s team has registered for your organization, whether you sign in with a password or with SSO (through WorkOS and your company’s identity provider). This section describes normal operation on an Enterprise account. The Privacy Policy has a section on Enterprise data handling. To request a Data Processing Agreement, use the contact page.

Where Your Conversation Goes

Instead of going to Reagent’s hosted AI, these go from the app directly to the model endpoint in Settings > Endpoint:
  • Your messages, the earlier messages in the chat, and the images, PDFs and text files you attach. These files aren’t uploaded to Reagent’s storage. Whether the model can read images and PDFs depends on that model.
  • Details of your REAPER session and Wwise connection, including your selections. See What the AI Model Receives.
  • Results from Reagent’s tools.
  • The requests that write chat titles and summarize long chats.
  • Requests from the Analyst and the Wwise subagent.
You enter the endpoint your organization gives you, once on each computer. It can be a provider on the internet, a server on your company network or a model server on your own computer. That provider’s terms govern how it handles the data. See Custom Endpoint. The Endpoint URL, Model ID, API key and other endpoint options are saved on this computer, not in your Reagent account. Reagent encrypts them with your operating system’s secure storage when it’s available, and clears them when you sign out or your sign-in session ends.

Features Not Offered

  • Dialogue transcription, take analysis and translation. Reagent doesn’t upload dialogue audio, and its storage refuses audio uploads from Enterprise accounts.
  • Script uploads for the dialogue editor. Word and Excel files are refused with a message that they can’t be attached.
  • Documentation searches. REAPER API search and the Wwise subagent’s online Wwise lookups.
  • Feedback. The feedback button still opens the form, but sending shows a message that feedback is disabled for Enterprise accounts. Use the contact page instead.
  • Usage analytics. The desktop app doesn’t send usage events or session recordings for Enterprise accounts.
For every difference, see Feature Availability. See also the Privacy Policy, Subprocessors, Terms of Service and, for privacy or security questions, the contact page.