Skip to content

fix: load complete run log history - #43

Merged
eetoc merged 3 commits into
mainfrom
fix/run-log-history
Aug 21, 2026
Merged

fix: load complete run log history#43
eetoc merged 3 commits into
mainfrom
fix/run-log-history

Conversation

@eetoc

@eetoc eetoc commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Request run logs from offset zero before following live output.
  • Scope the log stream to the run's project.
  • Make full-history request semantics explicit.
  • Include legacy Sandbox history cells in the Run Logs view.
  • Render legacy entries alongside V2 runs in chronological order.
  • Keep the Run Logs tab available when only legacy history exists.

Root cause

Event details with no V2 Run received historical output through ListSandboxHistory, but the Run Logs view only rendered Event timeline entries. The returned cells[].output was used for conversation data and omitted from the log viewer.

Testing

  • AGENT_COMPOSE_BASE=/agent-compose/ npm run check:ui
  • Verified the prefixed assets and Event trace API in the deployment environment.
  • /usr/local/go/bin/go test -count=1 ./pkg/agentcompose/api ./pkg/runs (backend compatibility verification)

@eetoc
eetoc merged commit 9f1c71f into main Aug 21, 2026
1 check passed
@eetoc
eetoc deleted the fix/run-log-history branch August 21, 2026 10:13
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