Skip to content

DOC Correct scenario baseline parameter guidance #2313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
romanlutz merged 1 commit into from
Aug 3, 2026
+8 −6
Merged

DOC Correct scenario baseline parameter guidance #2313

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions doc/code/scenarios/0_scenarios.ipynb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -437,9 +437,10 @@
"\n",
"Every scenario can optionally include a **baseline attack** — a `PromptSendingAttack` that sends\n",
"each objective directly to the target without any converters or multi-turn techniques. This is\n",
"controlled by the `include_baseline` parameter on `initialize_async`; when omitted, each\n",
"scenario falls back to its own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default\n",
"it on; `Jailbreak` defaults it off). See\n",
"controlled by the `include_baseline` scenario parameter, supplied through the CLI, config, or\n",
"`set_params_from_args` before `initialize_async`; when omitted, each scenario falls back to its\n",
"own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default it on; `Jailbreak` defaults\n",
"it off). See\n",
"[Common Scenario Parameters](./1_common_scenario_parameters.ipynb) for a worked example.\n",
"\n",
"Custom scenarios should choose their `BASELINE_ATTACK_POLICY` based on whether an unmodified\n",
Expand Down
7 changes: 4 additions & 3 deletions doc/code/scenarios/0_scenarios.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,9 +178,10 @@ async def _build_atomic_attacks_async(self, *, context):
#
# Every scenario can optionally include a **baseline attack** — a `PromptSendingAttack` that sends
# each objective directly to the target without any converters or multi-turn techniques. This is
# controlled by the `include_baseline` parameter on `initialize_async`; when omitted, each
# scenario falls back to its own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default
# it on; `Jailbreak` defaults it off). See
# controlled by the `include_baseline` scenario parameter, supplied through the CLI, config, or
# `set_params_from_args` before `initialize_async`; when omitted, each scenario falls back to its
# own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default it on; `Jailbreak` defaults
# it off). See
# [Common Scenario Parameters](./1_common_scenario_parameters.ipynb) for a worked example.
#
# Custom scenarios should choose their `BASELINE_ATTACK_POLICY` based on whether an unmodified
Expand Down