Skip to main content
For ready-to-copy prompts, see Example Workflows.

Writing Effective Prompts

Say what should change, where, and how. Names, numbers and units help. Instead of “Fix the tracks”, try:
Name the scope, using track, marker and region names exactly as they appear in REAPER: Describe the result, not every step:
When the method matters, name it, or ask for a plan before anything changes:
  • Dialogue. Silence trimming is for sound effects and other non-speech audio. For voice-over, dialogue or podcasts:
    • Ask Reagent to edit the dialogue instead.
    • Tell Reagent exactly which time ranges to remove, or edit in REAPER yourself.
  • Repeated prompts. Save them as slash commands and type / to run one.

Working with Selections

Each time you send a message, Reagent reads your selected items and tracks, the edit cursor and the time selection. When Wwise is connected, it also reads your Wwise selection. Select first, then keep the request short:
When selecting is awkward, such as across the whole project, describe the scope in words. Reagent is built to match “this”, “these” and “the selected” to what’s selected when you send, not to something mentioned earlier:
  • Words like item or track mean your REAPER selection. Words like event, bus or soundbank mean your Wwise selection.
  • If items and tracks are both selected, Reagent works on the items. Say “these tracks” to mean the tracks.
  • After you change the REAPER selection, a follow-up that says “this”, “these” or “the selected” uses the new one. Multi-step jobs under way, such as classifying items or editing dialogue, keep the items they started with.
  • While Wwise is connected to a running game, Reagent ignores your Wwise selection for requests about a sound you heard, unless you say “selected” or “selection”. See Live Mixing.

New Chat or Same Chat

For an unrelated task, start a new chat so earlier work doesn’t confuse the new request. For follow-ups, stay in the chat so Reagent can build on what it just did. In a long chat, Reagent may not recall the fine details above the “Earlier context summarized” divider. Start a new chat and restate what matters. See Long Chats and the Context Ring.

Undo and Recovery

1

Stop the request

Click the stop button (Cancel request) or press Esc. If an approval card is showing, click Deny first, then stop Reagent if it carries on.
2

Undo in REAPER

Before you send another request, press Cmd+Z (macOS) or Ctrl+Z (Windows) in REAPER once for each Reagent entry in the undo history. One request can leave several, and most start with reagent:. To see them, open Actions > Show action list…, search for “undo history” and run the action that shows the window.
3

Try again

Send a clearer request. Mention that you undid the last attempt, so Reagent doesn’t build on it.
REAPER’s undo only restores your REAPER project, not files on disk or Wwise (Undoing Changes). Before a large change to an important project, save a copy of it and back up any files a render, move or copy will replace.

Troubleshooting

Fixes for common problems.