Skip to content

feat: add runs dashboard list and detail views#14

Merged
nova-rey merged 1 commit intomainfrom
codex/implement-phase-3-runs-dashboard-feature
Nov 2, 2025
Merged

feat: add runs dashboard list and detail views#14
nova-rey merged 1 commit intomainfrom
codex/implement-phase-3-runs-dashboard-feature

Conversation

@nova-rey
Copy link
Owner

@nova-rey nova-rey commented Nov 2, 2025

Summary

  • add runs list and detail routes with launch/refresh controls and status badges
  • introduce runs API module with mock data artifacts to support offline mode
  • document the phase 3 baseline and cover the list view with a smoke test

Testing

  • npm run build
  • npm run test
  • npm run build:bundle

https://chatgpt.com/codex/tasks/task_e_6907d529d3848328b1748d5e87aa9a22

@nova-rey nova-rey merged commit 99b5576 into main Nov 2, 2025
1 check passed
@nova-rey nova-rey deleted the codex/implement-phase-3-runs-dashboard-feature branch November 2, 2025 22:14
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +32 to +34
export async function launchRun(payload: Record<string, unknown> = {}): Promise<RunDetail> {
if (isMockEnabled()) return (await axios.get("/mock-data/run_detail.json")).data;
const response = await axios.post(`${baseUrl()}/runs`, payload, authHeaders());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Launch button posts to wrong runs endpoint

The new launchRun helper posts to ${baseUrl()}/runs, while the existing API client’s startRun function targets /runs/start. If the backend has not changed, the Start Run button in RunsList will hit a non-existent route and silently log an error without launching anything. Please align the endpoint with /runs/start (or update the backend) so the launch control actually creates a run.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant