feat(agent-runtime): keep search index fresh across file writes and workspace changes#444
Conversation
…orkspace changes - Add post-write index sync (sync_written_path) after successful file_write - Add content_sha256 as trust boundary in plan_candidates() for freshness - Add regression tests for stale index detection (changed/deleted/renamed paths) - Add hash guard test for same-size/same-mtime rewrite detection - Add integration test proving own writes are searchable without manual rebuild - Update workspace-index spec with REQ-WIDX-011 (freshness guard) and REQ-WIDX-012 (v1 docs) - Archive SDD change 2026-04-05-search-index-freshness Closes #358
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 15 seconds. ⌛ 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (15)
✨ 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 |
✅ Contributor ReportUser: @yacosta738
Contributor Report evaluates based on public GitHub activity. Analysis period: 2025-04-05 to 2026-04-05 |
|



Closes #358