feat: persistent run history per agent#14
Conversation
|
Warning Review limit reached
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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
fc39978 to
19308fb
Compare
Closes #4.
Summary
RunHistoryclient component. FetchesGET /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.AgentPanelmountsRunHistorybelow the live output box and bumps aversioncounter when a run ends, so the list refreshes without a full page reload.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 onsrc/lib/db.tswith #13 once one of them lands; trivial rebase.Test plan