feat(proactive-runtime): M1-M2 agent tokens + rotation hardening#38
Conversation
Cross-repo M1 implementation. See companion PRs and docs/proactive-runtime/spec.md (in cloud).
…-provider buildSummary, Airtable lazy fetch) Cross-repo proactive-runtime milestone commit.
…-provider buildSummary, Airtable lazy fetch) Cross-repo proactive-runtime milestone commit.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, 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 the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (31)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Part of the Proactive Agent Runtime spec (#513 in cloud). M1 (agent token issuance) + M2 (rotation hardening). M5 will land path-scoped tokens; commits will append to this same branch.
In this PR
Test plan
gateway/src/relayauth-client.tsexpectationsNotes
🤖 Generated with Claude Code