Skip to content

feat: persistent run history per agent#14

Merged
proofmancer merged 1 commit into
mainfrom
feat/run-history
May 24, 2026
Merged

feat: persistent run history per agent#14
proofmancer merged 1 commit into
mainfrom
feat/run-history

Conversation

@proofmancer
Copy link
Copy Markdown
Owner

Closes #4.

Summary

  • New RunHistory client component. Fetches GET /api/agents/[id]/run (existing endpoint), renders the 25 most recent runs as a collapsed list. Click a row to expand the recorded JSONL output inline.
  • Each row shows: prompt preview (~80 chars), relative time, duration, and status / exit code chip (green pass, red fail, amber running).
  • AgentPanel mounts RunHistory below the live output box and bumps a version counter when a run ends, so the list refreshes without a full page reload.
  • Tiny in-file formatters for relative time (3m ago) and duration (12.4s, 1m 04s). No new dep.

Build fix bundled

Same SQLITE_BUSY in next build's parallel page-data-collection workers as #13: busy_timeout = 5000 + idempotent migration guard. May conflict on src/lib/db.ts with #13 once one of them lands; trivial rebase.

Test plan

  • Run an agent twice. Refresh. Both runs appear in History with timestamps and durations.
  • Click a row, the full JSONL output for that run expands.
  • Agent with zero runs shows "no runs yet."
  • After a live run finishes, History updates automatically.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 24, 2026

Warning

Review limit reached

@proofmancer, we couldn't start this review because you've used your available PR reviews for now.

Your plan includes 1 review of capacity. Refill in 2 minutes and 22 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 39fc6a0a-3f7c-4d7d-b52d-a33755cbcd40

📥 Commits

Reviewing files that changed from the base of the PR and between 88cb8a7 and 19308fb.

📒 Files selected for processing (2)
  • src/components/AgentPanel.tsx
  • src/components/RunHistory.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/run-history

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@proofmancer proofmancer mentioned this pull request May 24, 2026
4 tasks
@proofmancer proofmancer merged commit ffc3029 into main May 24, 2026
2 checks passed
@proofmancer proofmancer deleted the feat/run-history branch May 24, 2026 23:17
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.

v0.2: persistent run history per agent

1 participant