Agent-Manager: Reviewing code while an AI agent is still rewriting it
Writing Reviewing code while an AI agent is still rewriting it A line number is a position, not an identity. Keeping review comments attached while the producer keeps editing requires more than refreshing git diff. Code review normally begins after the author stops editing.
- ▪Writing Reviewing code while an AI agent is still rewriting it A line number is a position, not an identity.
- ▪Keeping review comments attached while the producer keeps editing requires more than refreshing git diff.
- ▪Code review normally begins after the author stops editing.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,319 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 | agent-manager |
| Canonical URL | https://agent-manager.dev/writing/live-review-race/ |
| Publication time | Thu, 24 Sep 2026 15:38:26 +0000 |
| Retrieval time | 2026-09-24T15:50:26.085Z |
| Last seen | 2026-09-24T15:50:26.085Z |
| 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 | T8MH5StcGtQ- · 1 stories |
| 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
Writing Reviewing code while an AI agent is still rewriting it A line number is a position, not an identity. Keeping review comments attached while the producer keeps editing requires more than refreshing git diff. Code review normally begins after the author stops editing. A commit, patch or pull request gives the reviewer a stable object. Coding agents break that assumption. I often start reviewing while an agent is still working, leave a comment on line 84, and watch that line become 91 before I have finished the next file. The first version of my terminal review UI refreshed the diff and kept each comment's file and line number. It looked fine until an agent inserted code above a commented line. The comment stayed at 84; the code it referred to moved.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at agent-manager.
Discussion
0 commentsMore from agent-manager
