Reagent works on your REAPER and Wwise projects on your computer and uses an AI model to understand what you ask. On individual plans (the Lite, Pro and Pro+ plans, and new accounts using their free trial credits), that model is Reagent’s hosted AI. This page is for sound designers and for the studio IT and security teams who review tools like Reagent.
At a Glance
Individual plans
Enterprise
What Stays on Your Computer
- Audio analysis. Reagent measures peaks, silence, loudness, spectrum and transients on your computer. The AI model receives the measurements, not the audio.
- UCS (Universal Category System) classification. The classification model ships with Reagent and runs on your computer. The AI model receives the category labels it produces.
- REAPER and Wwise connections. The Bridge, a small script inside REAPER, exchanges commands with Reagent through files on your computer. Reagent reaches Wwise Authoring through WAAPI (the Wwise Authoring API) 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. Commands you create in Settings > Commands are saved as files on this computer, and so are your app settings.
What Reagent’s tools find, such as track names, measurements and transcripts, becomes part of the conversation that goes to the AI model.
Signing out doesn’t delete your chats. Anyone who uses Reagent while logged in to the same macOS or Windows user account on this computer can see them, even if they sign in with a different Reagent account.
What the AI Model Receives
On Enterprise accounts, the AI model is your organization’s endpoint instead of Reagent’s hosted AI.
When you send a message, the AI model receives the following:
- Your conversation. Your message, the earlier messages in the chat, and the files you attached. Your chat history isn’t kept in your Reagent account, so each request carries the conversation so far.
- Your REAPER session. The project name, its track and item counts, the cursor position, time selection and selected tracks, and up to five selected items with their names (or file names), tracks, positions and lengths. A larger selection is sent as a count.
- Your Wwise connection. When Wwise is connected, the model also receives the Wwise version and up to 10 of the Wwise objects you’ve selected, each with its name, type, path in the Wwise project and ID. While Wwise is connected to a running game, it receives the number of selected objects instead of their details, plus the game’s name and the Profiler capture status. See What Reagent Sends on the Wwise page.
- 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. See Chat for the file types you can attach.
Connections on Every Plan
Reagent makes these connections on individual plans and Enterprise accounts alike:
- Sign-in and your profile. You sign in on reaperagent.com in your web browser, not inside the app. Your account details (email address, display name and your answers to the welcome questions) are stored in Reagent’s account database, hosted by Supabase. Reagent loads your profile and account status from it, and stays connected to it for account updates while the app runs. The reaperagent.com website, where you sign in, 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.
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.
File access. The tools Reagent uses to list, read, search, move, copy and rename files and create folders work only in:
- Your home folder.
- REAPER’s Scripts folder.
- External or network drives: on macOS, drives under
/Volumes; on Windows, any drive other than the system drive, plus network shares.
They refuse other locations. 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. See Where Reagent Can Reach on the File Operations page.
When Reagent opens a file on your computer for the chat, it reads text files only and refuses audio, images and other binary files. Files you attach yourself are covered in Where Attachments Go.
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, a Vercel service that forwards requests to AI providers, to the model for that job:
Dialogue Transcription
The automatic dialogue editor transcribes the speech in the items you select. Transcription doesn’t run on your computer:
- Reagent compresses the part of each source file that the item plays.
- It uploads that clip to its private temporary file storage, hosted by Supabase.
- Reagent’s server asks ElevenLabs to transcribe the clip. ElevenLabs downloads it through a temporary link that expires after five minutes.
- Reagent’s server normally deletes the clip once transcription is done. As a safeguard, a cleanup job deletes files in temporary storage that are 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
When you attach a PDF, TXT, CSV, TSV, Word or Excel file, Reagent also uploads a copy to the same temporary storage so the dialogue editor can use it as a script. When it does, Reagent’s server turns the file into text (Gemini reads PDFs) and sends that text to Gemini with the transcript. The same cleanup job deletes these files once they’re more than an hour old.
Documentation Searches
When Reagent looks something up in the ReaScript API documentation (REAPER API search), or the Wwise subagent looks something up in the Wwise documentation, the search text goes to reaperagent.com. Reagent writes this text from your request. Reagent’s server sends it to Voyage AI to find matching documentation.
Feedback You Send
When you use the feedback button in the title bar (tooltip: Send Feedback), 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 Reagent writes the feedback for you in a chat, it asks you to approve it before sending, unless you use Full access mode.
Usage Analytics
Reagent uses PostHog to understand how the app is used. Once Reagent confirms that your account isn’t an Enterprise account, the app sends usage events to PostHog, for example:
- 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 SSO or a password. This section describes normal operation on an Enterprise account.
If your organization uses single sign-on, you sign in through your company’s identity provider by way of WorkOS, the sign-in service Reagent uses for SSO. See Single Sign-On.
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 (a helper that works through large results) and the Wwise subagent (a helper that reads your Wwise project).
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, and 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 Reagent’s storage also 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 for Enterprise accounts.
For every difference, see Feature Availability.
