Add live Scenario progress - #2374
Open
Roman Lutz (romanlutz) wants to merge 9 commits into
Open
Conversation
This was referenced Aug 12, 2026
Roman Lutz (romanlutz)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
from
August 21, 2026 04:17
58c5c56 to
4337415
Compare
Roman Lutz (romanlutz)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
from
August 21, 2026 07:52
4337415 to
80a40b7
Compare
Roman Lutz (romanlutz)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
from
August 25, 2026 00:56
80a40b7 to
7fddb1d
Compare
Roman Lutz (romanlutz)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
from
August 25, 2026 03:45
7fddb1d to
e43a331
Compare
Roman Lutz (romanlutz)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
from
August 25, 2026 06:24
e43a331 to
9d55233
Compare
Richard Lundeen (rlundeen2)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
3 times, most recently
from
September 1, 2026 21:00
2fd41d4 to
b6ea257
Compare
Base automatically changed from
copilot/romanlutz-scenario-pr-02-catalog-upstream
to
main
September 1, 2026 21:34
Richard Lundeen (rlundeen2)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
from
September 1, 2026 21:34
b6ea257 to
cda766e
Compare
Behnam (behnam-o)
left a comment
Behnam (behnam-o)
left a comment
Contributor
There was a problem hiding this comment.
This PR should be scoped to the frontend live-progress experience; no changes under /pyrit are needed here. The progress and cancellation backend APIs come from earlier stack layers, ScenarioRunPlanGroupKind is only consumed by #2378, and the dataset-size override contract is first consumed by #2377. Moving those backend changes to their corresponding follow-up PRs would keep this layer focused and independently reviewable.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5d02c2d5-b499-4f78-a04d-03bffa750817
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5ece2d4e-f111-4a4a-80ba-39a59edd1298
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5ece2d4e-f111-4a4a-80ba-39a59edd1298
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5ece2d4e-f111-4a4a-80ba-39a59edd1298
Drive the attack-technique display projection from the typed identifier markers instead of hand-maintained child-name sets, so a target in a newly declared slot cannot leak operational params such as endpoint. Build the FloatScaleThresholdScorer rationale conditionally rather than patching the dangling heading in the frontend. Group attempts by atomic group id and truncate per group, surface attempts that match no planned unit, share the retry-pressure definition between the CLI and GUI rollups, and split ScenarioRunPage into reusable pieces. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c1f04cc2-edd2-4f51-82a4-7e2fde405b4f
Richard Lundeen (rlundeen2)
force-pushed
the
copilot/romanlutz-scenario-pr-03-live-upstream
branch
from
September 2, 2026 20:48
43fecf3 to
6b7e9ae
Compare
Richard Lundeen (rlundeen2)
marked this pull request as ready for review
September 2, 2026 20:51
The CLI progress bar switch from technique counts to execution-unit counts does not depend on the dashboard work and is user-visible on its own, so it is reviewed separately. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c1f04cc2-edd2-4f51-82a4-7e2fde405b4f
…nario-pr-03-live-upstream # Conflicts: # pyrit/score/true_false/float_scale_threshold_scorer.py
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c1f04cc2-edd2-4f51-82a4-7e2fde405b4f
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.
Summary
Adds the live run dashboard with incremental polling, active/completed/pending attack groups, outcome accounting, elapsed time, ETA, cancellation, and result navigation. Progress cursors are isolated per run so route changes cannot reuse another run's opaque cursor.
What this layer adds
Preview
Stack
This is 3 of 7 in native GitHub Stack #2390 and depends on #2373.
See the full implementation, screenshots, walkthrough, validation, and operational notes.
Validation