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

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. The mode applies to every chat, and Reagent keeps it after a restart. You can change it while Reagent works, and the new mode applies from its next action. A waiting approval card covers 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. Actions are named by their approval card’s title, where … stands for details, as in “Move 12 items”. Auto-review decides from the kind of action and a few of its settings, such as whether a move or copy is set to overwrite. It doesn’t use AI or look at your project or 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 appear, but Reagent can’t write metadata yet. If you allow it, the write fails and your files stay as they were. See Writing Metadata.

What Never Asks

These never show a card:
  • Looking at your REAPER project’s tracks, items, markers, plugins and settings, and at REAPER’s preferences, themes and the changes Reagent made to them.
  • 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, a card replaces the message box. Answer it with a button or a shortcut:
  • Allow (Cmd+Enter on macOS, Ctrl+Enter on Windows): Reagent runs the action and carries on.
  • Deny or the X: Reagent skips the action and continues its reply without it.
  • Esc: Reagent skips the action and stops the reply.
  • 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.
  • Questions, such as which track you mean, aren’t approvals. They appear in every mode, including Full access. See Answering Reagent’s Questions.
  • Approval cards don’t send a desktop notification, so check back if you switch to REAPER while Reagent works.
  • If a shortcut doesn’t respond, click the card and try again.

Undoing Changes

REAPER Tools

Every REAPER tool, and which ones change your project.