feat: stream run trace and agent output to the dashboard#4
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
1 participant
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
Streams orchestrator trace and agent output into Forge: OMA Core
onTrace/onAgentStream(and progress events) are formatted into a bounded in-memory log, published astrace_lineSSE events, and exposed viaGET /api/runs/trace. The web app subscribes and renders the log in the details panel LIVE_AGENT_OUTPUT section.Why
v0.1 includes inspecting traces and outputs during a run. The dashboard already showed task status from
run_snapshotevents; this adds the execution log (task lifecycle, LLM/tool spans, streaming text deltas) so developers can debug runs without leaving the UI.Checklist
npm run lintpassesnpm testpasses