RepoJournal
AI Red Teaming AI Red Teaming
34 wires and counting

$ follow AI Red Teaming

Keep up with AI Red Teaming in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-11-04
stories 61

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

PyRIT's GUI gets workflow defaults, quiet auto-refresh and in-repo scorers move to the expectation-aware hook

By RepoJournal · Filed · About AI Red Teaming · Composed from the cited sources · methodology

PyRIT's operator-facing GUI shipped four changes in one batch: last-used defaults for targets and scorers, a workflow-first Home, contextual help, and once-a-minute silent refresh, alongside a breaking move of in-repo scorers onto the expectation-aware piece hook.

4 - FEAT: Last-used Defaults microsoft/PyRIT

by richlundeen

New chats, scans and suite launches now reuse your last-used objective target and optional chat scorer (including Off), with supported Registry defaults taking precedence and explicit choices still first. The objective-target Registry default is removed, so anything relying on it must set a target explicitly.

9 - FEAT: Automatic Refresh microsoft/PyRIT

by richlundeen

The Reload and Refresh controls are gone from Home, registries, histories, Analytics, catalogs, saved presets/suites and configuration views, replaced by a read of visible views once per minute that keeps filters, selection and unsaved edits. Background failures surface as error text only, so you no longer get a manual retry button.

[BREAKING] MAINT Move in-repo scorers onto the expectation-aware piece hook (phase 12, part 2) microsoft/PyRIT

by WatchTree-19

Marked breaking: in-repo scorers now go through the expectation-aware piece hook (phase 12, part 2). If you vendor or subclass those scorers rather than calling them through the public path, check your scorer wiring against the new hook before upgrading.

7 - FEAT: Workflow-focused Home microsoft/PyRIT

by richlundeen

Home now leads with Attacks and Scans with direct entry actions and separate history links, and the large Labels and Default objective target cards are replaced by workflow content with Registry setup demoted to secondary. Recent attack and scan links get compact All/Attacks/Scans filters.

8 - FEAT: Contextual Help microsoft/PyRIT

by richlundeen

Contextual help arrives across chat, scanner and Registry views as native Fluent information icons plus term-text hover, without duplicate simultaneous help surfaces, and target labels and empty-state navigation are corrected. Elsewhere, promptfoo's npm_and_yarn group bump took glob from 13.0.6 to 14.0.2 alongside minimatch and follow-redirects.

Quick answers

What shipped in AI Red Teaming on November 4, 2026?
PyRIT's operator-facing GUI shipped four changes in one batch: last-used defaults for targets and scorers, a workflow-first Home, contextual help, and once-a-minute silent refresh, alongside a breaking move of in-repo scorers onto the expectation-aware piece hook. In total, 30 commits and 31 pull requests landed.
Who contributed to AI Red Teaming on November 4, 2026?
3 developers shipped this update, including dependabot, richlundeen, and WatchTree-19.
What were the notable AI Red Teaming updates?
4 - FEAT: Last-used Defaults, 9 - FEAT: Automatic Refresh, and [BREAKING] MAINT Move in-repo scorers onto the expectation-aware piece hook (phase 12, part 2).