Review important user flows with Scenarios
Save durable product context, keep it current, and apply relevant flows to code reviews.
What a Scenario is
A Scenario is a repository-scoped, free-text description of an important user flow. It gives Jina durable human context such as the actors, intent, invariants, and failure modes that matter for that flow.
Scenarios are exploratory review lenses, not scripted test cases. Jina uses the ordinary review harness, tasks, issues, and executable evidence to assess how well each selected flow holds up, then reports a 1–5 merge-readiness score instead of a pass/fail verdict.
Keep the library current
- Open Settings → Scenario automation and select a repository.
- Enable automatic updates to learn, revise, or archive important flows after changes land on the default branch.
- Open Scenarios to inspect the saved library or create, revise, and archive entries manually.
- Use Update corpus now when you need an immediate default-branch refresh.
Run Scenarios with pull-request reviews
When automatic Scenario runs are enabled, Jina freezes the current library, selects up to 10 flows affected by the pull request, and reviews them alongside the ordinary review.
GitHub receives one aggregate summary comment, while ordinary findings with a validated diff location are posted as inline review threads. Findings without an accepted inline location remain in the summary alongside a compact Scenario results table and report links; detailed Scenario narratives stay in their reports, and no Scenario section is shown when none was selected. Scenario reviews also appear in the normal Reviews list with their tasks, issues, and score; command and test evidence stays with the corresponding Runtime Tasks instead of being repeated in the outcome.
Models and manual runs
- Settings → Models selects Codex, workspace API keys, or Jina-managed routing for reviews. Unattended Scenario library updates use workspace API keys or Jina-managed execution, never a personal ChatGPT session.
- Run relevant, selected, or all Scenarios from the dashboard or MCP. A manual run can select up to 10 saved flows.
- One scoped workspace MCP token can expose both Wiki and Scenario tools. Grant only the context, scenarios, and reviews scopes the client needs.