docs: promote pages-usage guidance to main#382
Conversation
step 6 said recall injects claims and page titles but stopped there — a user who compiled pages and saw them in `vouch review` had no way to know how (or whether) claude consumes them. add the retrieval paths: recall carries titles, kb_search matches page bodies, kb_read_page returns the markdown plus cited claims, kb_context bundles items for a task, and /vouch-recall pulls a topic in explicitly. also state the easy-to-miss rule that pending pages are invisible to retrieval until approved — the gate applies to reads of proposals too.
docs(readme): spell out how approved pages reach a claude session
|
Warning Review limit reached
Next review available in: 10 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. ✨ 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 |
github-actions
Bot
added
docs
step 6 named the SessionStart hook but not the mechanism or what the injection actually looks like. spell out the hook contract (stdout of a SessionStart hook becomes opening-turn context) and include the real <vouch-approved-knowledge> digest from a live run — the same output the demo video closes on — plus the guarantees: only approved artifacts are emitted (archived/superseded/pending excluded) and the digest is size-guarded by recall.max_chars.
docs(readme): show how a session detects approved knowledge
1 participant
promotes #381 and #383 to main: step 6 of the readme walkthrough now explains how approved pages reach a claude session (recall titles, kb_search/kb_read_page/kb_context, /vouch-recall), shows the actual digest a SessionStart hook injects (the output the demo video closes on), and states that pending pages stay invisible to retrieval until approved. docs-only.