Conversation
When you dispatch multiple agents and step away, the first question on return is "what happened?" — `pu recap` answers it instantly by combining agent status with git diff stats into a single structured view. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
⌛ 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. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ 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 |
Summary
pu recap— a new CLI command that answers "what happened while I was away?" by combining agent status with git diff stats into a single structured viewRequest::Recap/Response::RecapResultwithRecapWorktreeEntryandRecapAgentEntrydata structuresExample output
Test plan
cargo test— 0 failures)cargo clippy— 0 warnings)pu recapwith active workspace agentspu recap --jsonproduces valid JSON🤖 Generated with Claude Code