Skip to content

Feature: run registry with history, per-run trace, and cancel#6

Merged
ibrahimkzmv merged 1 commit into
mainfrom
feat/multi-run-sessions
May 29, 2026
Merged

Feature: run registry with history, per-run trace, and cancel#6
ibrahimkzmv merged 1 commit into
mainfrom
feat/multi-run-sessions

Conversation

@ibrahimkzmv

Copy link
Copy Markdown
Member

What

Replace the singleton run state with a RunRegistry and per-run RunSession instances. Each run has a UUID, its own trace log, timestamps, and optional cancellation. Expose list/get/trace/cancel APIs, tag trace lines with runId, and update the dashboard with run history selection and a cancel control.

Why

Forge previously tracked only one implicit “current” run and a global trace buffer, which blocked inspecting past runs, correlating SSE events after switching runs, or stopping an in-flight orchestration cleanly. A registry model keeps concurrent-run rules explicit (one active run at a time) while preserving history for the UI.

Checklist

  • npm run lint passes
  • npm test passes
  • Added/updated tests for changed behavior
  • No new runtime dependencies (or justified in the PR description)

Signed-off-by: Ibrahim Kazimov <74775400+ibrahimkzmv@users.noreply.github.com>
@ibrahimkzmv ibrahimkzmv merged commit 87353ac into main May 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant