docs: document replies --json schema + multi-round review loop topology#51
Conversation
…estrating-agent-relay Address agent feedback on the orchestrating-agent-relay skill: - Document the verified replies --json schema (id/from/to/text/createdAt/ direction); call out createdAt (not ts) and the hard-coded inbound direction, verified against relay CLI source - Note the no-conversation empty state is a plain string, not [] - Add Multi-Round Review Loops section: workers must not self-remove until told, respawn-with-full-context fallback, silent-death detection - Expand Common Mistakes table and orchestrator Protocol accordingly - Bump orchestrating-agent-relay 2.0.0 -> 2.1.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
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 (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 |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
1 participant
Summary
Addresses agent feedback from running a real review→fix→re-review loop with the
orchestrating-agent-relayskill. (/review-loopwas already merged separately in #49 — this branch is rebased on currentmainand contains only these doc changes.)Changes
replies --jsonschema is now documented and source-verified againstrelay/src/cli/commands/messaging.ts(therepliescommand):id,from,to,text,createdAt,direction(+ optionalunread/unread_state)createdAt, nottsreplies --json,directionis always the hard-coded literal"inbound"(never"incoming"/"from"/"outbound");"outbound"only appears inhistory --to <agent> --jsonNo DM conversation with <Name>., not[]— with a copy-paste guardwho --jsonliveness + wall-clock fallback, since DM monitors only fire on DMs)orchestrating-agent-relay2.0.0 → 2.1.0🤖 Generated with Claude Code