What You Can Control During a Run
Once a scenario appears in workspace chat, your control moves from template configuration to run execution.| Moment | What you control | What is already fixed |
|---|---|---|
| Before launch | Whether to start after reviewing the launch preview | The installed template version and installation mappings |
| At launch | Launch inputs supplied by chat context and defaults | Runtime mappings that backend preflight resolved |
| While running | Continue, retry, resume, or cancel the scenario timeline | The saved manifest, compiled workflow, runtime snapshots, and initial inputs |
| After completion | Inspect history/details and start another run | The completed run snapshot |
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.| Gate | Where to fix it | User-visible result when blocked |
|---|---|---|
| Installed in the organization/workspace scope | Templates & Builder | It is not available as an installed scenario |
| Allowed for new runs | Settings → Scenarios → My scenarios | Hidden with a disabled reason |
| Chat toolbar visibility enabled | Settings → Scenarios → My scenarios | Hidden from the chat toolbar |
| Backend preflight OK | My scenarios → Configure launch | Hidden or launch-blocked with a preflight issue |
| Backend preflight runnable | My scenarios → Configure launch or runtime presets | Hidden or launch-blocked until runnable |
| Current Codex attempt is idle | Workspace chat | Toolbar action can be disabled with a wait message |
Start a Scenario
Open a workspace chat
Open the workspace and thread where the scenario should run. The scenario will
use that workspace, session, and host context.
Choose the scenario action
Open the chat toolbar workflow/action picker and choose the installed scenario
by its display name.
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.
Launch Preview
The launch preview is the last check before a scenario starts.| Preview section | What it tells you |
|---|---|
| Workflow | The scenario name that will start |
| Steps | The expanded linear step order |
| Runtime preset/config | Runtime source for the run, usually installation runtime mappings |
| Preflight blockers and warnings | Backend errors/warnings that may block the start button |
| Default and launch inputs | The exact input object after default inputs and launch inputs are combined |
| Runtime requirements | Requirement keys and resource expectations from the template |
| Expanded steps | Source workflow, source step, call path, mapped preset, human gate message, and prompt details |
| Runtime details | Runtime source, skill/MCP summary, executor policy, and implementation prompt |
Inputs at Launch
Installed scenarios use two input sources:- Default launch inputs saved on the installation.
- Launch inputs supplied by the workspace/chat context when the scenario is started.
| Situation | Result |
|---|---|
Default has objective, launch has no objective | The default objective is used |
Launch has objective | The launch objective overrides the default |
| Workspace chat supplies an implementation prompt | It is passed as implementation_prompt for scenarios that use that input |
| Neither default nor launch provides an expected field | Prompt placeholders for that field may render empty or fail validation, depending on the template |
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.| Runtime source | Used by |
|---|---|
| Workspace default runtime | Agent prompt steps without an isolated runtime requirement key |
| Installation runtime mapping | Agent prompt steps with an isolated runtime requirement key |
| Runtime preset snapshot | The exact skill/MCP selection frozen into the run at start |
Scenario Run Timeline
After a scenario starts, the workspace chat shows a workflow timeline.| Timeline item | Meaning |
|---|---|
| Workflow: name | The primary active or most recent scenario run |
| Status summary | Run status and progress, such as how many steps are done |
| Current | The step currently waiting or running |
| Details | Expands technical metadata for each step |
| History | Shows older scenario runs in the same workspace/session view |
| Cancel tracking | Cancels the scenario run and marks active steps/attempts as cancelled; it does not uninstall the scenario |
Step States and Actions
| Step state | What you can do | What happens |
|---|---|---|
| Running or pending | Wait | The backend runner continues the workflow |
| Waiting manual / human gate | Continue | The workflow records the human decision and starts the next step |
| Failed | Retry | The failed step is retried from the latest saved attempt |
| Waiting manual with parse/review issue | Retry | The review/gate step is retried |
| Blocked and retriable | Resume | The runner attempts to resume the blocked workflow |
| Completed | Inspect details/history | No action is required |
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.| User action | Behaviour |
|---|---|
| Continue | Marks the gate as continued and starts the next runnable step |
| Retry | Re-runs the gate/review step when the timeline exposes retry |
| Resume | Continues a blocked retriable run |
| Do nothing | The scenario remains waiting or blocked until acted on |
Running Scenario vs Sending a Normal Message
| Behaviour | Normal chat message | Installed scenario workflow |
|---|---|---|
| Prompt | You write it directly | Template renders prompt steps from saved launch inputs |
| Runtime | Chat runtime selector/defaults | Installation runtime mappings and workspace default as required by steps |
| Multi-step flow | Manual conversation | Saved linear workflow with automatic step progression |
| Human review | Normal approvals or your follow-up messages | Explicit human gate steps in the scenario timeline |
| Reuse | Copy/paste or remember instructions | Start the installed scenario again |
| Existing run after settings change | Not applicable | Existing run keeps its launch snapshot |
What Settings Changes Mean While You Are Working
| Settings change | Current active run | Next run |
|---|---|---|
| Disable installation | Keeps running from snapshot | Cannot start while disabled |
| Turn off Toolbar | Keeps running from snapshot | Hidden from toolbar |
| Change runtime mapping | Keeps old runtime snapshot | Uses new mapping after preflight |
| Change default inputs | Keeps old input snapshot | Uses new defaults, unless launch overrides them |
| Edit flow copy | Keeps source snapshot | Only used after the new version is installed/configured |
| Reorder steps on the builder board | Keeps current run order | Applies only to future runs after the edited version is saved and installed |
| Uninstall | Does not rewrite the run snapshot | Installation is gone from future toolbar use |
Troubleshooting
I cannot click the scenario action
I cannot click the scenario action
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.
Start scenario is disabled in the preview
Start scenario is disabled in the preview
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 scenario used an old prompt or old default input
The scenario used an old prompt or old default input
The run likely started before the Settings change. Start a new run after saving
configuration and passing preflight.
The timeline is waiting for me
The timeline is waiting for me
Look for a human gate message in the timeline. Continue, retry, or resume using
the action shown next to the waiting step.
A nested scenario appears as multiple steps
A nested scenario appears as multiple steps
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.