Slash Commands and Quick Replies

Slash commands and quick replies exist to reduce repetitive typing and make scene control faster.

They are especially useful in group chat, long campaigns, and workflows where you keep repeating the same steering moves.

Why These Two Systems Both Exist

At first glance, slash commands and quick replies can look redundant.

They are not.

They solve two slightly different problems:

• slash commands are better when you think in a typed command language,
• quick replies are better when the same actions should stay visible and one-tap.

Used together, they turn repeated scene steering from a memory test into a workflow.

Slash Commands

Slash commands are typed into the composer and triggered with a leading slash.

There are built-in commands, and you can also create your own custom commands.

They are best when you want speed without filling the screen with more buttons.

Custom Slash Commands

Custom commands let you define:

• a name,
• a description,
• a text value,
• and an action.

Supported actions are:

• Insert: place text into the composer without sending.
• Send: submit the text as a user message immediately.

Custom command names use alphanumeric characters and hyphens only.

That restriction is useful because command names need to stay predictable while you type.

Good Uses for Custom Slash Commands

• reusable scene directives,
• short formatting macros,
• frequently used out-of-character steering,
• recurring narrator cues,
• and repeated group-control actions.

If a behavior starts feeling like muscle memory, it is a good candidate for a custom slash command.

Built-In Command Workflows

Built-in commands matter most when the app already knows how to act on a structured instruction.

This is especially valuable in group chat, where command-style control is much faster than repeatedly opening menus or manually editing the same kinds of guidance.

Common examples include room-level speaker and target controls such as:

• moving to the next speaker,
• setting a specific speaker,
• targeting one participant,
• or clearing the target so replies address the room.

Quick Replies

Quick replies are on-screen shortcut buttons rendered above the composer.

They are useful when you want one-tap actions instead of repeatedly typing the same command language.

Quick replies are especially strong when:

• a scene has a stable rhythm,
• you use the same steering actions constantly,
• or you want important actions to remain visible under pressure.

Visibility Rules

Quick replies are not just static buttons.

They can be filtered by context.

Supported visibility scopes include:

• all chats,
• group chats only,
• and non-group chats only.

They can also react to conditions such as:

• whether the composer is empty,
• whether the composer already contains text,
• whether the runtime is idle or in an error state,
• and whether the current target is the room or a specific character.

This makes quick replies much more useful than a flat macro bar.

The point is not to show every macro all the time. The point is to show the right macro when it is actually relevant.

Multi-Step Quick Replies

Quick replies can contain multiple ordered steps rather than acting like one-shot inserts.

This is powerful because one button can perform a short sequence consistently.

For example, a quick reply can:

1. insert text,
2. send a slash command,
3. then send another message,

all in a deliberate order.

That makes quick replies useful for scene choreography, not just canned phrases.

Composer Clearing

Some quick reply steps can clear the composer after they run.

Use this when the macro should behave like a finished action instead of leaving old draft text behind.

That is especially useful when you treat a quick reply as an automation rather than as drafting assistance.

A Good Division of Labor

Use slash commands when:

• you prefer typing,
• you want minimal screen clutter,
• or you need flexible command-first control.

Use quick replies when:

• the same actions happen constantly,
• visibility matters,
• or one-tap execution is more important than typed precision.

Use both when:

• you want quick replies to trigger slash-style actions in a repeatable sequence.

Sync Behavior

Your macro library is part of your creative workflow rather than just local decoration.

That means custom slash commands and quick replies are designed to follow your wider workspace preferences across devices, even though the exact usefulness of a given macro still depends on the scene and route available on that device.

Practical Advice

Start with the macros you already type every day

The best automation is usually the one you were already repeating manually.

Keep labels obvious

Fast control is only fast if you can recognize the right action immediately.

Avoid macro bloat

Too many macros create their own friction. Start with the handful that actually save time every session.

Related Pages

• Read Group Chat if your main need is multi-character orchestration.
• Read Output Rules if the problem is final text cleanup rather than scene control.
• Read Settings Reference for where these controls live in the broader settings model.