Who contributed to AI Red Teaming on October 4, 2026?

3 developers shipped this update, including mldangelo, mldangelo-oai, and dependabot.

What were the notable AI Red Teaming updates?

fix(providers): launch npm-installed Codex app-server on Windows, fix(config): preserve imported test file path resolution, and fix: preserve log context and validate media paths.

Oct 4, 2026

$ the-wire · showcase

Codex provider works on Windows, PyRIT pulls mcp 2.2.0

By RepoJournal · Filed 17:28 UTC on October 9, 2026 · About AI Red Teaming · Composed from the cited sources · methodology

3 people shipped this

mldangelo @mldangelo 2 cited

dependabot @dependabot 2 cited

mldangelo-oai @mldangelo-oai 1 cited

promptfoo's Codex provider now launches on Windows and restores imported test-file path resolution from 0.123.1, while PyRIT's frontend and mcp dependency bumps carry defaults that changed in the SDK.

fix(providers): launch npm-installed Codex app-server on Windows promptfoo/promptfoo

by mldangelo

Windows cannot spawn npm's codex.cmd launcher directly, so promptfoo now starts npm-installed Codex through its JavaScript entrypoint via Node, no shell required, covering both global and project-local installs. Explicit codex_path_override values pass through untouched, so custom launch commands are unaffected.

fix(config): preserve imported test file path resolution promptfoo/promptfoo

by mldangelo

Imported YAML tests, plus JSON and JSONL tests loaded through arrays or globs, resolve bare vars files and supported JavaScript and Python provider references from their source directory again, matching release 0.123.1 behavior. Saved evaluations keep provider origins on reload, so configs migrated during the regression should run as before.

fix: preserve log context and validate media paths promptfoo/promptfoo

by mldangelo-oai

Winston transports had been dropping sanitized context fields, and legacy media operations validated only lexical paths; context and caller location are preserved now, and path components are checked against the canonical storage root with no-follow reads where the platform supports them. Configured storage-root symlinks still work, descendant symlinks are rejected.

MAINT: Bump mcp from 1.30.0 to 2.2.0 microsoft/PyRIT

by dependabot

PyRIT moves mcp from 1.30.0 to 2.2.0, and the SDK's release notes warn that several defaults changed, so servers and clients on 2.x should read the migration notes before you point PyRIT at an MCP target. Anyone running existing MCP-based attack flows should pin or retest rather than assume identical behavior.

MAINT: Bump the minor-and-patch group in /frontend with 9 updates microsoft/PyRIT

by dependabot

PyRIT's frontend picks up nine minor and patch dependency updates in one grouped bump. Routine maintenance, no operator-facing change.

Action items

→ Review the changed defaults in mcp 2.2.0 before running PyRIT 2.x MCP clients or servers microsoft/PyRIT [plan]