FEAT: SeedSimulatedConversation to generate simulated conversations in attacks#1304
Merged
rlundeen2 merged 34 commits intomicrosoft:mainfrom Jan 8, 2026
Conversation
ValbuenaVC
reviewed
Jan 6, 2026
4737f02 to
17541d8
Compare
ValbuenaVC
approved these changes
Jan 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refactor Seed Models, allowing Seeds to configure simulating conversation in Attacks.
SeedGroupandSeedAttackGroupinto distinct files, whereSeedAttackGroupis a subclass - specifically aSeedGroupwith exactly one objective. I imagine in the future there will be more groups (e.g.SeedBenchmarkGroup).SeedSimulatedConversationto be able to configure simulating conversations in datasets. In the future I expect there will be more seed types (e.g.SeedExpectedResponsethat might have an expected return value and required for benchmarks)Multiple small refactors to clearly separate responsibilities along the way. In the future
To document, I added examples in
2_seed_programmingthat shows how Seeds translate to attack parameters, and included the newSeedSimulatedConversationDB Migration Notes
The following failed before migration:
pytest .\tests\integration\memory\test_azure_sql_memory_integration.py::test_get_seeds_with_metadata_filterMigration in test and prod:
ALTER TABLE [SeedPromptEntries] ADD [seed_type] NVARCHAR(50) NULL;Then the test passes