Hive_review: Multi-agent AI code-review loop
One or more reviewer agents review the current diff. Reviewer feedback is sent back to the implementor. The loop repeats until all reviewers return HIVE_REVIEW_STATUS: PASS.
- ▪One or more reviewer agents review the current diff.
- ▪Reviewer feedback is sent back to the implementor.
- ▪The loop repeats until all reviewers return HIVE_REVIEW_STATUS: PASS.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,301 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/metacircu1ar/hive_review |
| Publication time | Fri, 24 Jul 2026 08:25:17 +0000 |
| Retrieval time | 2026-07-24T08:52:33.921Z |
| Last seen | 2026-07-24T08:52:33.921Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Fz3yFGYDTptL |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
hive_review ./hive_review \ # Git worktree to review; subdirs normalize to the Git root. --repo-dir /path/to/repo \ # Prompts, responses, ids, logs, transcripts, and status live under --session-dir. --session-dir sessions/my-review \ # One implementor model config from model_config.json. --implementor 'GPT-5.5-xhigh-login' \ # One or more reviewer model configs, comma-separated. --reviewers 'GPT-5.4-xhigh-login,Claude-Opus-4.8-max-login' \ # Pause after --max-rounds review/fix rounds; interactive mode can continue. --max-rounds 5 \ # Optional; omit --prompt to review the current diff. --prompt "Fix the failing parser tests" hive_review automates a multi-agent review loop: An implementor agent writes or fixes code. One or more reviewer agents review the current diff.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.