Skip to main content
Reagent starts in Default permissions, which shows an approval card before every change. Looking at your project, analyzing audio and reading files never ask.

​
The Three Modes

​
Which Mode to Use

  • Default permissions while you learn how Reagent handles a task. You see every change before it happens.
  • Auto-review for tidying files and adding project markers or regions. Everything else still asks, including item edits, scripts, renders, metadata, Wwise changes and adding take markers at peaks.
  • Full access for long batches you’ve already tried on a few items. Switch back when you’re done.
Even in Full access, file actions only reach the folders in Where Reagent Can Reach and don’t replace existing files unless Reagent sets them to overwrite. Renders and scripts aren’t limited this way.

​
Change the Mode

In the message box, click the button next to + (it shows the current mode), then choose Default permissions, Auto-review or Full access. Hover over a mode for a one-line description.
  • The mode applies to every chat, not only the one you’re in, and Reagent remembers it after you restart.
  • You can change it while Reagent is working. The new mode applies from Reagent’s next action.
  • A waiting approval card covers the message box and the mode menu, so answer the card first.

​
What Asks in Each Mode

Default permissions asks before every action below, and Full access asks before none of them. Each action is named by its approval card’s title, where … stands for the details, as in “Move 12 items” or “Create folder Stems”.
Auto-review decides from the kind of action and a few of the settings Reagent gives it, such as whether a move or copy is set to overwrite existing files. It doesn’t use AI to judge actions, and it doesn’t look at your project or your disk.
  • Run script covers anything Reagent does through a Lua script, which is how it handles requests no built-in tool covers, such as “Create 4 new tracks”. See ReaScript.
  • Edit media items covers splitting, deleting, copying, trimming or moving items.
  • Mark peaks asks only when Reagent adds take markers at peaks, not when it just finds them.
  • Render media renders to audio or video files.
Write audio metadata can still appear, but Reagent can’t write metadata into audio files yet. If you allow it, the write fails with an error and your files stay as they were. See Writing Metadata.
Use Wwise subagent appears when the task Reagent writes for the Wwise subagent contains a change word, such as “set”, “create”, “delete” or “apply”. The subagent itself only reads your Wwise project, even though the card says it may modify it. Any change comes afterward as a separate Wwise change, which follows your permission mode.

​
What Never Asks

These don’t change your project or your files, so they never show a card:
  • Looking at your REAPER project: tracks, items, markers, plugins and project settings.
  • Analyzing audio, reading audio metadata and classifying sounds.
  • Listing, finding, reading and searching files.
  • The Wwise subagent’s own lookups in your Wwise project.
  • Loading one of Reagent’s skills.
  • Drafting a script for you to review, shown as Create script. Nothing runs until you click the play button (Run script) on the code yourself.
  • Dialogue and documentation: transcribing, analyzing and translating dialogue, and searching REAPER and Wwise documentation. These send audio, transcripts, reference scripts or search text through Reagent’s servers to third-party AI services, for example ElevenLabs for transcription and Voyage AI for documentation searches. See Dialogue and Privacy & Security.

​
The Approval Card

When an action needs your OK, Reagent pauses and a card replaces the message box. Answer it with a button or its shortcut:
  • Allow (Cmd+Enter on macOS, Ctrl+Enter on Windows): Reagent runs the action and carries on.
  • Deny, or the X (Esc): Reagent doesn’t run the action. Esc also stops the reply.
The card’s title names the action. The rest depends on the kind of action: To read a script’s code before you approve it, click the Run script summary line in the chat above the card, then Show code.
Approve with Allow on the card. The play button in the code panel runs the script straight away, outside the card, and Allow would then run it again.
Also good to know:
  • One approval covers one action, but an action can do a lot: a batch of up to 100 file moves, copies, renames or folders, or a script that changes many REAPER items or Wwise objects. Several approvals come one card at a time.
  • Approval cards don’t send a desktop notification. If you switch to REAPER while Reagent works, check back to see whether it’s waiting for you.
  • If a shortcut doesn’t respond, click the card and try again.

​
When You Deny

Nothing changes for that action. When you click Deny or the X, Reagent is told you declined and continues its reply without the action. Open the action’s summary line in the chat to see the step marked Cancelled. To steer Reagent, say what you want instead in your next message. To deny and stop the whole reply, click Deny and then the stop button (Cancel request) in the message box.

​
Questions Aren’t Approvals

Reagent sometimes asks a question with options, for example which track you mean. Questions appear in every mode, including Full access. If Reagent isn’t the front window, a question also sends a desktop notification titled “Reagent needs your input”. See Answering Reagent’s Questions.

​
Undoing Changes

Files replaced by a move, copy or render can’t be recovered by Reagent or REAPER’s undo.
In REAPER’s undo history, most of Reagent’s changes are named reagent: …, for example reagent: Delete 3 item(s). A script’s undo point uses the description Reagent gave it.

File Operations

What Reagent can do with your files and where it can reach.

REAPER Tools

Every REAPER tool, and which ones change your project.

ReaScript

How Reagent writes and runs Lua scripts.

Wwise

Connect to Wwise, approve changes and mix a running game.