Scenario workflows are installed scenarios that appear as reusable actions in a workspace chat toolbar. They let you start a preconfigured chain of agent prompts and human gates without rewriting the same instructions every time. Use this page for the run-time experience. Use Scenarios for installation, configuration, and authoring.

​
What You Can Control During a Run

Once a scenario appears in workspace chat, your control moves from template configuration to run execution.
Starting a scenario creates a run snapshot. Changing Settings while the run is active does not rewrite that active run. Configure Settings for the next run.

​
When a Scenario Appears in the Toolbar

A scenario must pass every gate below before it becomes a usable workspace chat action. If a scenario should be available but is missing, open Settings → Scenarios → My scenarios and look at Toolbar-hidden scenarios and the row status.

​
Start a Scenario

1

Open a workspace chat

Open the workspace and thread where the scenario should run. The scenario will use that workspace, session, and host context.
2

Choose the scenario action

Open the chat toolbar workflow/action picker and choose the installed scenario by its display name.
3

Review launch preview

Jaidu asks the backend for a launch preview. Review steps, runtime requirements, preflight blockers/warnings, default and launch inputs, and expanded step details.
4

Start scenario

Click Start scenario when the preview is startable. If backend preflight blocks launch, fix Settings and retry.

​
Launch Preview

The launch preview is the last check before a scenario starts. The Start scenario button is disabled when backend preflight says the scenario cannot start.

​
Inputs at Launch

Installed scenarios use two input sources:
  1. Default launch inputs saved on the installation.
  2. Launch inputs supplied by the workspace/chat context when the scenario is started.
Launch inputs override default inputs with the same key. The merged object is shown in launch preview and then frozen into the run snapshot.

​
Runtime During Launch

Installed scenarios do not use the runtime selector in the chat input. They use the runtime mappings saved on the installation and verified by backend preflight. If a mapped preset changes later, the active run keeps its snapshot. Future runs use the latest preset state after preflight.

​
Scenario Run Timeline

After a scenario starts, the workspace chat shows a workflow timeline.

​
Step States and Actions

Human gates show the gate message and available actions. The generic action is usually Continue. Some first-party review gates can show specialized labels, such as retrying a review or running relevance anyway.

​
Human Gates

A human gate is a pause point designed into the scenario template. It gives you a chance to review output before the next agent prompt or nested scenario call.
A human gate is part of the scenario run, not the normal chat approval flow. Continuing it advances the scenario chain that was snapshotted at launch.

​
Running Scenario vs Sending a Normal Message

​
What Settings Changes Mean While You Are Working

​
Troubleshooting

The workspace may already have an active Codex attempt, the scenario may be mutating, or the action may not have a ready launch request. Wait for the current agent run to finish, then try again.
Read the Preflight blockers and warnings section. Common causes are missing runtime mappings, a mapped preset without the required skill/MCP server, or a nested scenario that cannot expand.
The run likely started before the Settings change. Start a new run after saving configuration and passing preflight.
Look for a human gate message in the timeline. Continue, retry, or resume using the action shown next to the waiting step.
A scenario_call step expands into the called scenario’s own linear steps in the backend preview/run snapshot. The call path shows where those nested steps came from.