Feature: start team run via API and stream live task state to dashboard#3
Merged
Merged
Conversation
Signed-off-by: Ibrahim Kazimov <74775400+ibrahimkzmv@users.noreply.github.com>
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.
What
Adds an end-to-end path from OMA Core to the Forge UI: start a demo team run via the API, keep an in-memory run snapshot on the server, broadcast
run_snapshotevents over SSE, and drive the existing team-run dashboard from live state instead of static demo data.Server
POST /api/runs— startoma.runTeamon the registeredforge-demoteam (202; 409 if a run is already in progress)GET /api/runs/current— current run snapshot (status,goal,tasks)CurrentRunstate updated fromonPlanReady,onProgress, and finalTeamRunResultrun_snapshotevents on the existing/api/eventsSSE streamWeb
useForgeRun— loads current snapshot and health, subscribes to SSE, exposes Run demoWhy
v0.1 needs running workflows and real-time visualization. The dashboard UI was already in place with static demo data; this wires it to OMA Core through the existing health/SSE scaffold so Forge can show a live DAG during execution.
Out of scope for this PR: workflow file loading, trace/
onTraceinspection, run history, and cancellation.Checklist
npm run lintpassesnpm testpasses