From 9631e1c70d786ea216992b2833313473950f749d Mon Sep 17 00:00:00 2001
From: Evan Bonsignori <ebonsignori@github.com>
Date: Fri, 25 Sep 2026 18:33:19 +0000
Subject: [PATCH 1/3] Match the ordered-list number chip to the Figma prose
 spec (#63361)

---
 .../ui/MarkdownContent/stylesheets/lists.scss | 105 ++++++++++++++++--
 src/frame/stylesheets/index.scss              |  14 +++
 2 files changed, 112 insertions(+), 7 deletions(-)

diff --git a/src/frame/components/ui/MarkdownContent/stylesheets/lists.scss b/src/frame/components/ui/MarkdownContent/stylesheets/lists.scss
index bf59814fc53d..23e6d33a9db9 100644
--- a/src/frame/components/ui/MarkdownContent/stylesheets/lists.scss
+++ b/src/frame/components/ui/MarkdownContent/stylesheets/lists.scss
@@ -3,11 +3,26 @@
   // from the Figma prose spec (node 795:41593), applied via CSS on the existing
   // markup. We can't use the brand OrderedList/UnorderedList components — their
   // ListItem span-wraps children, which breaks nested <ul>/<p>/code inside an
-  // <li> (see github/docs-engineering#6694).
+  // <li> (see github/docs-engineering#6694). The measurements below come from
+  // the "Prose" frame of that spec (node 389:95780).
 
   // Ordered lists: each number sits in a filled rounded "label" chip (muted
   // background, monospace medium, 4px radius) with a 16px gap to the item text.
+  //
+  // Scoped to lists that are top level IN THE PROSE — a direct child of the
+  // article body, plus the container <div>s content-render wraps around a list
+  // on its way here: {% tool %} blocks (which nest, e.g. {% vscode %} inside
+  // {% vscode %}), [!NOTE]-style callouts (src/content-render/unified/alerts.ts
+  // rewrites the blockquote to a .ghd-alert div) and GraphQL reference
+  // descriptions. Without these carve-outs those lists fall through to
+  // @primer/css's plain decimal markers, so a single article ends up showing
+  // two different numbering styles. Lists BELOW top level are handled by the
+  // nesting rules at the end of this block.
+  > :global(.ghd-tool) > :global(.ghd-tool) > ol:not(:global(.no-styling)),
+  > :global(.ghd-tool) > :global(.ghd-alert) > ol:not(:global(.no-styling)),
   > :global(.ghd-tool) > ol:not(:global(.no-styling)),
+  > :global(.ghd-alert) > ol:not(:global(.no-styling)),
+  :global(.graphql-item-description) > ol:not(:global(.no-styling)),
   > ol:not(:global(.no-styling)) {
     list-style: none;
     counter-reset: markdown-ordered-list;
@@ -18,8 +33,20 @@
       counter-increment: markdown-ordered-list;
       // Reserve the chip column: 25px chip + 16px gap to the text (Figma).
       padding-left: 41px;
-      // Consistent spacing regardless of `li > p` or `li > [text]`.
-      margin-bottom: 16px;
+    }
+
+    // 32px between steps (Figma: the item frames sit exactly 32px apart) against
+    // 16px between the blocks INSIDE a step. That two-level rhythm is what makes
+    // a step read as one unit; at a flat 16px a step's own sub-blocks looked no
+    // more attached to it than the next step did.
+    //
+    // This is margin-TOP on `li + li`, not margin-bottom on `li`: the <ol> has
+    // no bottom padding or border, so a bottom margin on the last item collapses
+    // straight out of the list and silently becomes the gap to the next block.
+    // Margins still collapse through the li, so one declaration covers both
+    // `li > p` (loose lists) and bare `li > [text]` (tight lists).
+    > li + li {
+      margin-top: 32px;
     }
 
     > li::before {
@@ -38,8 +65,15 @@
       // tall, dropping its centre ~5px below the first line of text.
       min-width: 25px;
       height: 24px;
-      padding: 0 0.5rem; // 8px, per the Figma label
-      // Brand label chip: monospace medium number on a subtle fill.
+      // 4px, not the Figma label's 8px: `min-width` already pins a single-digit
+      // chip to 25px, so the side padding only ever decides how wide a
+      // MULTI-digit chip grows. At 8px a two-digit counter measured 33.6px and
+      // ate the 16px gutter down to ~7px from step 10 on (36 articles have a
+      // list that reaches 10, the longest is 35). At 4px a two-digit chip is
+      // 25.6px, so steps 1 and 10 look identical and the body text stays on one
+      // straight line. Single-digit rendering is unchanged.
+      padding: 0 0.25rem;
+      // Brand label chip: monospace medium number on a muted fill.
       font-family: var(--brand-fontStack-monospace);
       font-size: 0.875rem; // 14px
       font-weight: var(--brand-text-weight-medium, 500);
@@ -47,9 +81,15 @@
       letter-spacing: 0.15px;
       text-align: center;
       color: var(--brand-color-text-default, var(--color-fg-default));
+      // Figma fills the label with `border/muted` (#e4ebe6), not
+      // `canvas/subtle`. Canvas-subtle is one step paler in both modes and
+      // barely separates from the article canvas (#f2f5f3 on white, #0f1511 on
+      // brand's #000000), so the number read as a wash rather than a chip.
+      // Both properties fall back to the legacy @primer/css token rather than a
+      // hex, so the fallback stays mode-aware if brand's CSS fails to load.
       background-color: var(
-        --brand-color-canvas-subtle,
-        var(--color-canvas-subtle)
+        --brand-color-border-muted,
+        var(--color-border-muted)
       );
       border-radius: var(--brand-borderRadius-small, 4px);
     }
@@ -58,16 +98,67 @@
     ol {
       list-style-type: lower-alpha;
     }
+
+    // Figma draws nested bullets as filled discs; @primer/css inherits the UA's
+    // depth-based markers, which switch to a hollow circle at level two.
+    ul {
+      list-style-type: disc;
+    }
+
+    // Nested lists sit in the step's own text column. @primer/css puts 2em of
+    // padding on every ul/ol, which here stacks on top of the 41px chip column
+    // and pushed sub-items ~17px right of the design. 16px lands the nested
+    // item's text 57px from the item's left edge, with its marker flush against
+    // the parent's 41px text column. Padding only — the nested list's zero
+    // margins are what keep the 16px gap below the step's paragraph.
+    ul,
+    ol {
+      padding-left: 16px;
+    }
   }
 
   // Unordered lists: keep the native bullet but adopt brand item spacing
   // (--base-size-8 = 0.5rem gap between items) + brand body color.
+  //
+  // This selector group MUST mirror the ordered-list one above. The two share a
+  // text column, so any container the ol group reaches but this one doesn't is a
+  // container where the ol indents to 41px while its sibling ul stays at
+  // @primer/css's 2em — reproducing, inside one block, the exact 9px jog the
+  // padding-left below exists to remove. All three extra shapes have real
+  // content: a {% tool %} nested in a {% tool %} holding both list types, a
+  // bullet list inside an alert inside a tool block, and GraphQL descriptions
+  // whose top level is a <ul> rather than an <ol>.
+  > :global(.ghd-tool) > :global(.ghd-tool) > ul:not(:global(.no-styling)),
+  > :global(.ghd-tool) > :global(.ghd-alert) > ul:not(:global(.no-styling)),
   > :global(.ghd-tool) > ul:not(:global(.no-styling)),
+  > :global(.ghd-alert) > ul:not(:global(.no-styling)),
+  :global(.graphql-item-description) > ul:not(:global(.no-styling)),
   > ul:not(:global(.no-styling)) {
     color: var(--brand-color-text-default, var(--color-fg-default));
+    // Share the ordered list's 41px text column. @primer/css leaves uls at
+    // 2em/32px, so once the chip rule above moved numbered items to 41px the
+    // prose left edge jogged 9px every time an article alternated bullets and
+    // steps.
+    padding-left: 41px;
 
     > li {
       margin-bottom: 0.5rem;
     }
+
+    // An ordered list under a bullet is below top level too, so it takes the
+    // same plain letters, disc bullets and inset as one nested inside a
+    // numbered step. Without this it fell through to @primer/css's decimals.
+    ol {
+      list-style-type: lower-alpha;
+    }
+
+    ul {
+      list-style-type: disc;
+    }
+
+    ul,
+    ol {
+      padding-left: 16px;
+    }
   }
 }
diff --git a/src/frame/stylesheets/index.scss b/src/frame/stylesheets/index.scss
index 948ab8603731..f2e1ea2ed82e 100644
--- a/src/frame/stylesheets/index.scss
+++ b/src/frame/stylesheets/index.scss
@@ -101,6 +101,20 @@ html[data-color-mode] body {
   html[data-color-mode="auto"][data-dark-theme*="dark"] {
     --brand-color-canvas-default: var(--base-color-scale-black-0);
     --brand-color-text-default: var(--base-color-scale-white-0);
+    // A literal, not `var(--base-color-scale-gray-7)`: brand declares its light
+    // scale on `:root, [data-color-mode="light"]`, and `:root` IS this same
+    // <html> — so routing through the scale here just resolves the LIGHT gray-7
+    // (#58635b) straight back. The two tokens above are safe only because
+    // black-0/white-0 carry the same value in both of brand's blocks.
+    //
+    // #191f1b is brand's dark `border/muted`. Note this is a root-level token
+    // with ~30 consumers across the app, not a chip-local fix: it also flips the
+    // article header-box rule (ArticleGridLayout `.heroIntro::after`) and the
+    // drawer rules to their dark values in this fallback. The case that
+    // motivated it is the ordered-list number chip, which otherwise keeps its
+    // light fill (#e4ebe6) while the digit is already patched to white by the
+    // line above — 1.2:1, i.e. invisible.
+    --brand-color-border-muted: #191f1b;
   }
 }
 

From a3acef5a1e89964266aa14de432b6db92d017c1f Mon Sep 17 00:00:00 2001
From: Nhu Do <nhu-do@github.com>
Date: Fri, 25 Sep 2026 19:07:30 +0000
Subject: [PATCH 2/3] Update Auto docs (#63538)

---
 .../agents/about-third-party-coding-agents.md |  2 +-
 .../concepts/agents/anthropic-claude.md       |  2 +-
 .../copilot/concepts/agents/openai-codex.md   |  2 +-
 .../concepts/models/auto-model-selection.md   | 30 ++++---------------
 .../copilot/tutorials/optimize-ai-usage.md    |  4 +--
 data/tables/copilot/auto-model-selection.yml  | 18 +++++++++++
 6 files changed, 28 insertions(+), 30 deletions(-)

diff --git a/content/copilot/concepts/agents/about-third-party-coding-agents.md b/content/copilot/concepts/agents/about-third-party-coding-agents.md
index 0c371a3f594c..7a06b5525510 100644
--- a/content/copilot/concepts/agents/about-third-party-coding-agents.md
+++ b/content/copilot/concepts/agents/about-third-party-coding-agents.md
@@ -49,7 +49,7 @@ The following third-party agents are supported on {% data variables.product.gith
 
 When starting a task with a third-party agent, you can select the AI model used by the agent. You may find that different models perform better, or provide more useful responses, depending on the type of task. For help deciding which model to use, see [AUTOTITLE](/copilot/reference/ai-models/model-comparison).
 
-You can also select **Auto**, which allows {% data variables.copilot.copilot_auto_model_selection %} to choose the best available model on your behalf. See [AUTOTITLE](/copilot/concepts/models/auto-model-selection).
+You can also select **Auto**, which chooses between the supported models below. Choosing **Auto** with third-party agents does **not** leverage {% data variables.copilot.copilot_auto_model_selection %}. See [AUTOTITLE](/copilot/concepts/models/auto-model-selection).
 
 The following models are available for each agent:
 
diff --git a/content/copilot/concepts/agents/anthropic-claude.md b/content/copilot/concepts/agents/anthropic-claude.md
index ad114e862dbc..fce475c3e86f 100644
--- a/content/copilot/concepts/agents/anthropic-claude.md
+++ b/content/copilot/concepts/agents/anthropic-claude.md
@@ -27,4 +27,4 @@ When starting a task with the {% data variables.product.prodname_anthropic_claud
 * Auto
 {% data reusables.copilot.anthropic-claude-agent-models %}
 
-If you select **Auto**, {% data variables.copilot.copilot_auto_model_selection %} will select the best model based on availability and to help reduce rate limiting. For more information, see [AUTOTITLE](/copilot/concepts/models/auto-model-selection).
+If you select **Auto**, it will choose one of the available models listed above. **Auto** in {% data variables.product.prodname_anthropic_claude %} coding agent does **not** leverage {% data variables.copilot.copilot_auto_model_selection %}.
diff --git a/content/copilot/concepts/agents/openai-codex.md b/content/copilot/concepts/agents/openai-codex.md
index 493e65e7e687..cd38ab50c055 100644
--- a/content/copilot/concepts/agents/openai-codex.md
+++ b/content/copilot/concepts/agents/openai-codex.md
@@ -30,7 +30,7 @@ When starting a task with the {% data variables.product.prodname_openai_codex %}
 * Auto
 {% data reusables.copilot.openai-codex-agent-models %}
 
-If you select **Auto**, {% data variables.copilot.copilot_auto_model_selection %} will select the best model based on availability and to help reduce rate limiting. For more information, see [AUTOTITLE](/copilot/concepts/models/auto-model-selection).
+If you select **Auto**, it will choose one of the available models listed above. **Auto** in {% data variables.product.prodname_openai_codex %} coding agent does **not** leverage {% data variables.copilot.copilot_auto_model_selection %}.
 
 ## {% data variables.product.prodname_vscode_shortname %} extension
 
diff --git a/content/copilot/concepts/models/auto-model-selection.md b/content/copilot/concepts/models/auto-model-selection.md
index 296327d92883..4d08c4d61f03 100644
--- a/content/copilot/concepts/models/auto-model-selection.md
+++ b/content/copilot/concepts/models/auto-model-selection.md
@@ -19,11 +19,12 @@ More than just a model picker, {% data variables.copilot.copilot_auto_model_sele
 
 ### Auto with task optimization
 
-> [!NOTE] {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} with task optimization is generally available in {% data variables.copilot.copilot_chat_short %} on the {% data variables.product.github %} website, in {% data variables.product.prodname_vscode_shortname %}, in {% data variables.copilot.copilot_cli_short %}, and in {% data variables.copilot.github_copilot_app %}.
+> [!NOTE] {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} with task optimization is generally available in {% data variables.copilot.copilot_chat_short %} on the {% data variables.product.github %} website, in {% data variables.product.prodname_vscode_shortname %}, in {% data variables.copilot.copilot_cli_short %}, in {% data variables.copilot.github_copilot_app %}, and in JetBrains IDEs.
 
 {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} with task optimization combines two systems to provide high quality results and better reliability. One system tracks real-time system health and availability, while the other evaluates task complexity. Putting these together, {% data variables.copilot.copilot_auto_model_selection_short %} routes the task to the optimal model.
 
-Routing occurs along natural cache boundaries to avoid additional cache related costs. Switching models mid-session has shown increased cost without ample improvements in quality.
+Routing occurs along natural cache boundaries and large drifts in conversation complexity to avoid additional cache related costs without quality improvements.
+
 This helps you get more value from {% data variables.product.prodname_copilot_short %} since it matches each task to the model that can solve it most efficiently. That means reserving higher-cost reasoning models for problems that truly need it, while routing straightforward tasks to faster, lower-cost models that still deliver great results.
 
 Benefits of using {% data variables.copilot.copilot_auto_model_selection_short %} include:
@@ -87,38 +88,17 @@ When you select **Auto**, {% data variables.copilot.copilot_auto_model_selection
 
 > [!TIP]
 > You can see which model was used for each {% data variables.product.prodname_copilot_short %} response.
-> * In **{% data variables.copilot.copilot_chat_short %}**, hover over the response.
+> * In **{% data variables.copilot.copilot_chat_short %}** and **{% data variables.copilot.github_copilot_app %}**, hover over the response.
 > * In **{% data variables.copilot.copilot_cli_short %}**, the model used for each response displays in the terminal.
 > * In **{% data variables.copilot.copilot_cloud_agent %}**, the model used for each response displays at the end of the response.
-> * In **{% data variables.copilot.github_copilot_app %}**, the model used for each response is shown by the model picker next to **Auto**.
 
 ### {% data variables.copilot.copilot_chat_short %} in IDEs
 
 {% data variables.copilot.copilot_auto_model_selection_short_cap_a %}, with task optimization, is generally available in the following IDEs:
   * {% data variables.product.prodname_vscode_shortname %}
+  * JetBrains IDEs
 
 {% data variables.copilot.copilot_auto_model_selection_short_cap_a %}, optimized for model reliability and availability, is generally available in the following IDEs:
-  * JetBrains IDEs
   * Eclipse
   * Xcode
   * {% data variables.product.prodname_vs %}
-
-## {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} in third-party agents
-
-When you select **Auto** in the {% data variables.product.prodname_openai_codex %} or {% data variables.product.prodname_anthropic_claude %} coding agents, {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} chooses from the supported list of models, subject to your policies and subscription type.
-
-### {% data variables.product.prodname_openai_codex %} supported models
-
-These models are available for {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} in the {% data variables.product.prodname_openai_codex %} coding agent.
-
-{% data reusables.copilot.openai-codex-agent-models %}
-
-For more information, see [AUTOTITLE](/copilot/concepts/agents/openai-codex).
-
-### {% data variables.product.prodname_anthropic_claude %} supported models
-
-These models are available for {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} in the {% data variables.product.prodname_anthropic_claude %} coding agent.
-
-{% data reusables.copilot.anthropic-claude-agent-models %}
-
-For more information, see [AUTOTITLE](/copilot/concepts/agents/anthropic-claude).
diff --git a/content/copilot/tutorials/optimize-ai-usage.md b/content/copilot/tutorials/optimize-ai-usage.md
index f1348f34861e..8d11768d5ab7 100644
--- a/content/copilot/tutorials/optimize-ai-usage.md
+++ b/content/copilot/tutorials/optimize-ai-usage.md
@@ -43,7 +43,7 @@ See [AUTOTITLE](/copilot/reference/ai-models/supported-models#models-with-extend
 
 A small router looks at your prompt and sends it to the model that can **handle it most efficiently**, reserving expensive reasoning models for complex problems. It also avoids models that burn through a token budget quickly.
 
-{% data variables.copilot.copilot_auto_model_selection_short_cap_a %} also **protects your cache**. It only changes models at natural cache boundaries, when a new session starts or after you run `/compact`, never mid-task. To understand more about why this matters, see [4. Preserve the cache](#4-preserve-the-cache).
+{% data variables.copilot.copilot_auto_model_selection_short_cap_a %} also **protects your cache**. It changes models at natural cache boundaries, when a new session starts or after you run `/compact`. As conversations evolve, it will re-route at points where quality improvements outweigh cache loss. To understand more about why this matters, see [4. Preserve the cache](#4-preserve-the-cache).
 
 {% data variables.copilot.copilot_auto_model_selection_short_cap_a %} also routes around degraded or busy models, so you hit fewer rate limits and errors.
 
@@ -198,4 +198,4 @@ Teams that invest in these guardrails see fewer retries, faster task completion,
 Monitor and manage your spending to get the most out of your {% data variables.product.prodname_ai_credits_short %}:
 
 * **Use your dashboard and budget controls**. The "AI usage" page, under https://github.com/settings/billing, breaks down consumption across every feature and model, so you can see where your credits are actually going and adjust accordingly. See [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/monitor-ai-usage).
-* **Upgrade for a larger allowance**. If you regularly approach your monthly limit, a higher plan may be more economical than paying for additional usage, as higher plans have more {% data variables.product.prodname_ai_credit_singular %} allowance. See [AUTOTITLE](/copilot/get-started/plans#github-ai-credits-allowance-by-plan) and [AUTOTITLE](/copilot/how-tos/manage-your-account/view-and-change-your-copilot-plan).
\ No newline at end of file
+* **Upgrade for a larger allowance**. If you regularly approach your monthly limit, a higher plan may be more economical than paying for additional usage, as higher plans have more {% data variables.product.prodname_ai_credit_singular %} allowance. See [AUTOTITLE](/copilot/get-started/plans#github-ai-credits-allowance-by-plan) and [AUTOTITLE](/copilot/how-tos/manage-your-account/view-and-change-your-copilot-plan).
diff --git a/data/tables/copilot/auto-model-selection.yml b/data/tables/copilot/auto-model-selection.yml
index 67356bdc502d..878c24918651 100644
--- a/data/tables/copilot/auto-model-selection.yml
+++ b/data/tables/copilot/auto-model-selection.yml
@@ -56,6 +56,18 @@
   cli: true
   app: true
 
+- name: GPT-6 Luna
+  cloud_agent: true
+  chat: true
+  cli: true
+  app: true
+
+- name: GPT-6 Sol
+  cloud_agent: true
+  chat: true
+  cli: true
+  app: true
+
 # Anthropic
 - name: Claude Haiku 4.5
   cloud_agent: true
@@ -75,6 +87,12 @@
   cli: true
   app: true
 
+- name: Claude Opus 5.5
+  cloud_agent: true
+  chat: true
+  cli: true
+  app: true
+
 - name: Claude Sonnet 4.6
   cloud_agent: false
   chat: true

From 396f518f2256b9f6c031f025ab3fe7590d9d3234 Mon Sep 17 00:00:00 2001
From: Cory Calahan <corycalahan@github.com>
Date: Fri, 25 Sep 2026 19:15:04 +0000
Subject: [PATCH 3/3] clarify security campaign filters for agentic autofix
 (#63397)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Laura Coursen <lecoursen@github.com>
Co-authored-by: Jon Janego <jonjanego@github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jonjanego <1334913+jonjanego@users.noreply.github.com>
---
 .../creating-managing-security-campaigns.md      | 16 ++++++++++------
 .../overview-dashboard-filters.md                |  4 ++++
 2 files changed, 14 insertions(+), 6 deletions(-)

diff --git a/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/creating-managing-security-campaigns.md b/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/creating-managing-security-campaigns.md
index 83122a8b418f..4cc1aa73eb9a 100644
--- a/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/creating-managing-security-campaigns.md
+++ b/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/creating-managing-security-campaigns.md
@@ -25,7 +25,7 @@ Security campaigns are created and managed from the **{% data variables.product.
 
 You choose the alerts that you want to include in the campaign by using either:
 
-* **Campaign templates**: Campaign templates contain filters for the most common alert selections. {% ifversion security-campaigns-autofix %}For code campaigns, they also all include the requirement that {% data variables.copilot.copilot_autofix %} is supported for all the alert types included (that is, `autofix:supported`).{% endif %}
+* **Campaign templates**: Campaign templates contain filters for the most common alert selections. {% ifversion security-campaigns-autofix %}When agentic autofix is disabled, they also use `autofix:supported` to include only alerts for rules supported by {% data variables.copilot.copilot_autofix %}.{% endif %}
 * **Custom filters**: Creating a campaign using custom filters lets you define your own criteria for selecting alerts for the campaign, and lets you tailor your campaign to your organization's specific needs.
 
 {% data reusables.code-scanning.campaigns-api %}
@@ -74,7 +74,11 @@ All the template filters use `is:open` to include only alerts that need to be re
 Additional default filters for {% data variables.product.prodname_code_scanning %} alerts:
 
 * `autofilter:true` includes only alerts that appear to be in application code. {% ifversion security-campaigns-autofix %}
-* `autofix:supported` includes only alerts that are for rules that are supported for {% data variables.copilot.copilot_autofix %}.{% endif %}
+
+> [!NOTE]
+> When agentic autofix is enabled for your organization or enterprise, the `autofix` filter is unavailable, and adding `autofix:supported` does not change the results. For alerts in repositories where {% data variables.copilot.copilot_cloud_agent %} and {% data variables.copilot.copilot_autofix_short %} are available, you can use **Assign to {% data variables.product.prodname_copilot_short %}** for any {% data variables.product.prodname_code_scanning %} alert in a campaign.
+
+{% endif %}
 
 For more information about filtering alerts, see [AUTOTITLE](/code-security/tutorials/secure-your-organization/best-practice-fix-alerts-at-scale#2-select-alerts-for-your-campaign) and [AUTOTITLE](/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/filtering-alerts-in-security-overview).
 
@@ -84,11 +88,11 @@ For more information about filtering alerts, see [AUTOTITLE](/code-security/tuto
 
 {% endif %}
 
-In addition to the core filters, you will usually want to add a filter to limit results to a specific rule name, severity, or tag.
+Use `autofilter:true` with `rule:`, `tag:`, or `severity:` to scope your campaign.
 
-* `is:open autofilter:true {% ifversion security-campaigns-autofix %}autofix:supported {% endif %}rule:java/log-injection` to show only alerts for log injection in Java code. See [AUTOTITLE](/code-security/reference/code-scanning/codeql/codeql-queries).
-* `is:open autofilter:true {% ifversion security-campaigns-autofix %}autofix:supported {% endif %}tag:external/cwe/cwe-117` to show only alerts for "CWE 117: Improper Output Neutralization for Logs". This includes log injection in Java and other languages.
-* `is:open autofilter:true {% ifversion security-campaigns-autofix %}autofix:supported {% endif %}severity:critical` to show only alerts with a security severity of critical.
+* `is:open autofilter:true rule:java/log-injection` to show only alerts for log injection in Java code. See [AUTOTITLE](/code-security/reference/code-scanning/codeql/codeql-queries).
+* `is:open autofilter:true tag:external/cwe/cwe-117` to show only alerts for "CWE 117: Improper Output Neutralization for Logs". This includes log injection in Java and other languages.
+* `is:open autofilter:true severity:critical` to show only alerts with a security severity of critical.
 
 {% ifversion security-campaigns-secrets %}
 
diff --git a/content/code-security/reference/security-at-scale/overview-dashboard-filters.md b/content/code-security/reference/security-at-scale/overview-dashboard-filters.md
index 90953d7631fb..f1369ea4c12e 100644
--- a/content/code-security/reference/security-at-scale/overview-dashboard-filters.md
+++ b/content/code-security/reference/security-at-scale/overview-dashboard-filters.md
@@ -227,6 +227,10 @@ You can click any result to see full details of the relevant query and the line
 
 | Qualifier | Description |
 | -------- | -------- |
+|`autofilter`|Display only alerts that appear to be in application code (`autofilter:true`).|
+|{% ifversion code-scanning-autofix %}|
+|`autofix`|Display only alerts for rules supported by {% data variables.copilot.copilot_autofix %} (`autofix:supported`). When agentic autofix is enabled for your organization or enterprise, this filter is unavailable and does not affect results.|
+|{% endif %}|
 |`is`|Display {% data variables.product.prodname_code_scanning %} alerts that are open (`open`) or closed (`closed`).|
 |`resolution`| Display {% data variables.product.prodname_code_scanning %} alerts closed as "false positive" (`false-positive`), "fixed" (`fixed`), "used in tests" (`used-in-tests`), or "won't fix" (`wont-fix`).|
 |`rule`|Display {% data variables.product.prodname_code_scanning %} alerts identified by the specified rule.|