FEAT: Add remove_seeds_from_memory_async to memory

.azuredevops/end-to-end-tests.yml

@@ -1,14 +1,14 @@
 # Runs end-to-end scenario tests using pyrit_scan CLI
 
-trigger: none  # Disable automatic CI triggers
+trigger: none
 
 schedules:
-- cron: "0 7 * * *"  # 7 AM UTC = 11 PM PST (UTC-8) / Midnight PDT (UTC-7)
-  displayName: Nightly E2E Tests at 11 PM PST
+- cron: "0 7 * * *"  # 7 AM UTC = 11 PM PST (UTC-8)
+  displayName: E2E Tests Daily at 07:00 AM UTC (11:00 PM PST)
   branches:
     include:
-    - main
-  always: true  # Run even if there are no code changes
+      - main
+  always: true
 
 jobs:
 - template: test-job-template.yml

.azuredevops/integration-tests.yml

@@ -1,12 +1,15 @@
 
 # Builds the pyrit environment and runs integration tests
 
-trigger:
+trigger: none
+
+schedules:
+- cron: "0 */3 * * *"  # Every 3 hours
+  displayName: Integration Tests Every 3 Hours
   branches:
     include:
       - main
-
-# There are additional PR triggers for this that are configurable in ADO.
+  always: true
 
 jobs:
 - template: test-job-template.yml

.azuredevops/partner-integration-tests.yml

@@ -1,14 +1,15 @@
 # Builds the pyrit environment and runs partner integration tests. Partner integration tests are to ensure that we
 # are not breaking any contract between PyRIT and its partners.
-trigger: none  # Disable automatic CI triggers
+
+trigger: none
 
 schedules:
-- cron: "0 6 * * *"  # 6 AM UTC = 10 PM PST (UTC-8) / 11PM PDT (UTC-6)
-  displayName: Nightly Partner Integration Tests at 10 PM PST
+- cron: "0 6 * * *"  # 6 AM UTC = 10 PM PST (UTC-8)
+  displayName: Partner Integration Tests Daily at 06:00 AM UTC (10:00 PM PST)
   branches:
     include:
-    - main
-  always: true  # Run even if there are no code changes
+      - main
+  always: true
 
 jobs:
 - template: test-job-template.yml

.azuredevops/test-job-template.yml

@@ -79,7 +79,7 @@ jobs:
 
       echo "Microsoft ODBC Driver 18 installed successfully."
     displayName: 'Install ODBC Driver 18 for SQL Server'
-  - bash: uv sync --extra dev --extra all
+  - bash: uv sync --extra all
     name: install_PyRIT
   - bash: df -all -h
     name: disk_space_check

.devcontainer/Dockerfile

@@ -1,5 +1,5 @@
 # syntax=docker/dockerfile:1
-FROM mcr.microsoft.com/devcontainers/python:3.11-bookworm
+FROM mcr.microsoft.com/devcontainers/python:3.14-bookworm
 
 # Makes installation faster
 ENV UV_COMPILE_BYTECODE=1

.devcontainer/devcontainer.json

@@ -16,9 +16,6 @@
         "python.analysis.extraPaths": [
           "/workspace"
         ],
-        "python.linting.mypyArgs": [
-          "--cache-dir=.mypy_cache"
-        ],
         "python.analysis.typeCheckingMode": "basic",
         "python.analysis.diagnosticMode": "openFilesOnly",
         "python.analysis.autoSearchPaths": false,
@@ -50,9 +47,9 @@
           "**/.pytest_cache/**": true,
           "**/build/**": true,
           "**/dist/**": true,
-          "**/pyrit/auxiliary_attacks/gcg/attack/**": true,
+          "**/pyrit/executor/promptgen/gcg/attack/**": true,
           "**/doc/**": true,
-          "**/.mypy_cache/**": true,
+          "**/.ty_cache/**": true,
           "**/frontend/node_modules/**": true,
           "**/frontend/dist/**": true,
           "**/dbdata/**": true

.devcontainer/devcontainer_setup.sh

@@ -1,31 +1,7 @@
 #!/bin/bash
 set -e
 
-MYPY_CACHE="/workspace/.mypy_cache"
 VIRTUAL_ENV="/opt/venv"
-# Create the mypy cache directory if it doesn't exist
-if [ ! -d "$MYPY_CACHE" ]; then
-    echo "Creating mypy cache directory..."
-    sudo mkdir -p $MYPY_CACHE
-    sudo chown vscode:vscode $MYPY_CACHE
-    sudo chmod 755 $MYPY_CACHE
-else
-    # Check ownership
-    OWNER=$(stat -c '%U:%G' $MYPY_CACHE)
-
-    if [ "$OWNER" != "vscode:vscode" ]; then
-        echo "Fixing mypy cache directory ownership..."
-        sudo chown -R vscode:vscode $MYPY_CACHE
-    fi
-
-    # Check permissions
-    PERMS=$(stat -c '%a' $MYPY_CACHE)
-
-    if [ "$PERMS" != "755" ]; then
-        echo "Fixing mypy cache directory permissions..."
-        sudo chmod -R 755 $MYPY_CACHE
-    fi
-fi
 
 # cleanup old extensions
 sudo rm -rf /vscode/vscode-server/extensionsCache/github.copilot-*
@@ -46,7 +22,7 @@ if [ ! -f "$HASH_FILE" ] || [ "$(cat $HASH_FILE)" != "$CURRENT_HASH" ]; then
 
     # Install dependencies
     uv pip install ipykernel
-    uv pip install -e ".[dev,all]"
+    uv sync --extra all
     # Register the kernel with Jupyter
     python -m ipykernel install --user --name=pyrit-dev --display-name="Python (pyrit-dev)"
 

.devcontainer/docker-compose.yml

@@ -13,7 +13,7 @@ services:
       - pip-cache:/home/vscode/.cache/pip:cached
       - uv-cache:/home/vscode/.cache/uv:cached
       - precommit-cache:/home/vscode/.cache/pre-commit:cached
-      - mypy-cache:/workspace/.mypy_cache:cached
+      - ty-cache:/workspace/.ty_cache:cached
       - pylance-cache:/home/vscode/.cache/pylance:cached
       - node-modules:/workspace/frontend/node_modules:cached
       - ~/.pyrit:/home/vscode/.pyrit:cached
@@ -27,6 +27,6 @@ volumes:
   pip-cache:
   uv-cache:
   precommit-cache:
-  mypy-cache:
+  ty-cache:
   pylance-cache:
   node-modules:

.dockerignore

@@ -14,7 +14,7 @@ build/
 **/*.py[cod]
 **/*$py.class
 **/.pytest_cache/
-**/.mypy_cache/
+**/.ty_cache/
 
 # Environment files with secrets
 .env

.env_example

@@ -30,7 +30,7 @@
 
 PLATFORM_OPENAI_CHAT_ENDPOINT="https://api.openai.com/v1"
 PLATFORM_OPENAI_CHAT_KEY="sk-xxxxx"
-PLATFORM_OPENAI_CHAT_GPT4O_MODEL="gpt-4o"
+PLATFORM_OPENAI_CHAT_MODEL="gpt-4o"
 
 # Note: For Azure OpenAI endpoints, use the new format with /openai/v1 and specify the model separately
 # Example: https://xxxx.openai.azure.com/openai/v1
@@ -42,6 +42,15 @@ AZURE_OPENAI_GPT4O_MODEL="deployment-name"
 # identifiers will default to the value of the standard MODEL environment variable.
 AZURE_OPENAI_GPT4O_UNDERLYING_MODEL="gpt-4o"
 
+# Optional second GPT-4o endpoint (that can be used for round-robin distribution).
+# TargetInitializer creates RoundRobinTargets that automatically group together
+# targets with identical underlying model names and behavioral params, allowing
+# for distribution of requests across them for rate-limit relief.
+AZURE_OPENAI_GPT4O_ENDPOINT2="https://xxxx.openai.azure.com/openai/v1"
+AZURE_OPENAI_GPT4O_KEY2="xxxxx"
+AZURE_OPENAI_GPT4O_MODEL2="deployment-name"
+AZURE_OPENAI_GPT4O_UNDERLYING_MODEL2="gpt-4o"
+
 AZURE_OPENAI_INTEGRATION_TEST_ENDPOINT="https://xxxxx.openai.azure.com/openai/v1"
 AZURE_OPENAI_INTEGRATION_TEST_KEY="xxxxx"
 AZURE_OPENAI_INTEGRATION_TEST_MODEL="deployment-name"
@@ -75,17 +84,36 @@ AZURE_OPENAI_GPT4O_UNSAFE_CHAT_MODEL2="deployment-name"
 AZURE_OPENAI_GPT4O_UNSAFE_CHAT_UNDERLYING_MODEL2=""
 
 # Adversarial chat target (used by scenario attack techniques, e.g. role-play, TAP)
+# Default endpoint goes here; specialized ones below
 ADVERSARIAL_CHAT_ENDPOINT="https://xxxxx.openai.azure.com/openai/v1"
 ADVERSARIAL_CHAT_KEY="xxxxx"
 ADVERSARIAL_CHAT_MODEL="deployment-name"
 
+ADVERSARIAL_CHAT_SINGLETURN_ENDPOINT="https://xxxxxx.westus3.inference.ml.azure.com/score"
+ADVERSARIAL_CHAT_SINGLETURN_KEY="xxxxx"
+ADVERSARIAL_CHAT_SINGLETURN_MODEL="deployment-name"
+
+ADVERSARIAL_CHAT_MULTITURN_ENDPOINT="https://xxxxxx.westus3.inference.ml.azure.com/score"
+ADVERSARIAL_CHAT_MULTITURN_KEY="xxxxx"
+ADVERSARIAL_CHAT_MULTITURN_MODEL="deployment-name"
+
+ADVERSARIAL_CHAT_REASONING_ENDPOINT="https://xxxxxx.westus3.inference.ml.azure.com/score"
+ADVERSARIAL_CHAT_REASONING_KEY="xxxxx"
+ADVERSARIAL_CHAT_REASONING_MODEL="deployment-name"
+
+
+# Objective Scorer chat target (used in scorers in scenarios)
+OBJECTIVE_SCORER_CHAT_ENDPOINT="https://xxxxx.openai.azure.com/openai/v1"
+OBJECTIVE_SCORER_CHAT_KEY="xxxxx"
+OBJECTIVE_SCORER_CHAT_MODEL="deployment-name"
+
 AZURE_FOUNDRY_DEEPSEEK_ENDPOINT="https://xxxxx.eastus2.models.ai.azure.com"
 AZURE_FOUNDRY_DEEPSEEK_KEY="xxxxx"
 AZURE_FOUNDRY_DEEPSEEK_MODEL=""
 
 AZURE_FOUNDRY_PHI4_ENDPOINT="https://xxxxx.models.ai.azure.com"
 AZURE_CHAT_PHI4_KEY="xxxxx"
-AZURE_FOUNDRY_PHI4_MODEL=""
+AZURE_CHAT_PHI4_MODEL=""
 
 AZURE_FOUNDRY_MISTRAL_LARGE_ENDPOINT="https://xxxxx.services.ai.azure.com/openai/v1/"
 AZURE_FOUNDRY_MISTRAL_LARGE_KEY="xxxxx"
@@ -113,7 +141,7 @@ DEFAULT_OPENAI_FRONTEND_MODEL = "gpt-4o"
 
 OPENAI_CHAT_ENDPOINT=${PLATFORM_OPENAI_CHAT_ENDPOINT}
 OPENAI_CHAT_KEY=${PLATFORM_OPENAI_CHAT_KEY}
-OPENAI_CHAT_MODEL=${PLATFORM_OPENAI_CHAT_GPT4O_MODEL}
+OPENAI_CHAT_MODEL=${PLATFORM_OPENAI_CHAT_MODEL}
 # The following line can be populated if using an Azure OpenAI deployment
 # where the deployment name differs from the actual underlying model
 OPENAI_CHAT_UNDERLYING_MODEL=""
@@ -267,6 +295,7 @@ AZURE_CONTENT_SAFETY_API_KEY="xxxxx"
 AZURE_CONTENT_SAFETY_API_ENDPOINT="https://xxxxx.cognitiveservices.azure.com/"
 
 HUGGINGFACE_TOKEN="hf_xxxxxxx"
+HUGGINGFACE_ENDPOINT="https://router.huggingface.co/v1"
 
 GOOGLE_GEMINI_ENDPOINT = "https://generativelanguage.googleapis.com/v1beta/openai"
 GOOGLE_GEMINI_API_KEY = "xxxxx"

.github/ISSUE_TEMPLATE/praise.md

@@ -0,0 +1,21 @@
+---
+name: Praise
+about: Tell us something you love about PyRIT or the Co-PyRIT GUI
+title: ''
+labels: 'praise'
+assignees: ''
+
+---
+
+<!--
+Thanks for taking the time to share something positive! Pure praise issues
+are auto-acknowledged and closed by our triage bot so the team can see them
+quickly without cluttering the open-issue backlog.
+
+If you'd also like to report a bug or request a feature, please open a
+separate issue using the corresponding template.
+-->
+
+#### What do you love?
+<!-- Tell us what's working well, what you find useful, or any moment that made
+your day easier. -->

.github/copilot-instructions.md

@@ -4,19 +4,16 @@ PyRIT (Python Risk Identification Tool for generative AI) is an open-source fram
 
 ## Architecture
 
-PyRIT uses a modular "Lego brick" design. The main extensibility points are:
+PyRIT uses a modular pluggable-brick design.
 
-- **Prompt Converters** (`pyrit/prompt_converter/`) — Transform prompts (70+ implementations). Base: `PromptConverter`.
-- **Scorers** (`pyrit/score/`) — Evaluate responses. Base: `Scorer`.
-- **Prompt Targets** (`pyrit/prompt_target/`) — Send prompts to LLMs/APIs. Base: `PromptTarget`.
-- **Executors / Scenarios** (`pyrit/executor/`, `pyrit/scenario/`) — Orchestrate multi-turn attacks.
-- **Memory** (`pyrit/memory/`) — `CentralMemory` for prompt/response persistence.
+**[`doc/code/framework.md`](../doc/code/framework.md) is the canonical reference for how these pieces fit together.** It defines each component's responsibilities — what it owns and, critically, what it *does not* own — and how scenarios, attack techniques, executors, and the core/shared layers relate. Read it before adding or reviewing components so new code lands in the right place.
 
 ## Code Review Guidelines
 
 When performing a code review, be selective. Only leave comments for issues that genuinely matter:
 
-- Bugs, logic errors, or security concerns
+- Bugs, correctness, logic errors, or security concerns
+- **Component responsibilities** — Each component should do its job and *only* its job, per [`doc/code/framework.md`](../doc/code/framework.md). Flag responsibility bleed: e.g. an executor assembling prepended/system prompts or role-play framing (that's an attack technique), a converter or target making branching decisions (that's an attack/scorer), a scorer acting on its own result (the attack branches), or business logic living in memory/output. If logic belongs in a different brick, say so.
 - Unclear code that would benefit from refactoring for readability
 - Violations of the critical coding conventions above (async suffix, keyword-only args, type annotations)
 
@@ -32,8 +29,10 @@ Aim for fewer, higher-signal comments. A review with 2-3 important comments is b
 
 BEFORE editing or code-reviewing any file, you MUST read the `.github/instructions/` files whose `applyTo` patterns match the files you are about to edit. For example:
 - Editing/code-reviewing `pyrit/**/*.py` → read `style-guide.instructions.md` and `user-custom.instructions.md`
+- Editing/code-reviewing database models, Alembic migrations, or memory migration tests → also read `database.instructions.md`
 - Editing/code-reviewing `pyrit/scenario/**` → also read `scenarios.instructions.md`
-- Editing/code-reviewing `pyrit/prompt_converter/**` → also read `converters.instructions.md`
+- Editing/code-reviewing `pyrit/setup/initializers/techniques/**` → also read `setup-techniques.instructions.md`
+- Editing/code-reviewing `pyrit/converter/**` → also read `converters.instructions.md`
 - Editing/code-reviewing `tests/**` → also read `test.instructions.md`
 - Editing/code-reviewing `doc/**/*.py` or `doc/**/*.ipynb` → also read `docs.instructions.md`
 - Editing/code-reviewing `frontend/**/*.{ts,tsx}` → also read `frontend-style-guide.instructions.md`