- Ya
- 2 Septemba 2026, 02:16 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 1d03c2b
A member filed this against the Send To AI dialog: the description "often resets back to the original description while you are editing it". It reset the instruction, the title, the ticked screenshots and the three dropdowns too — all of it, mid-sentence, with nothing on screen to say why. The dialog seeded its fields from the `bug` PROP and listed that prop in the effect's dependencies, so it re-seeded whenever a new object arrived rather than when a new report did. Behind it the drawer was handing down a fresh object constantly: its `load` is a useCallback over `onViewed`, the tab builds that from `useNavCounts()`, and the nav's value is reallocated on ordinary traffic — a chat message landing anywhere, the badge's minute tick, the bug-queue broadcast. Each of those re-read the whole report from the server and replaced the object the dialog was watching. Minutes of composing a hand-off, gone, at a rate set by how busy the console was. That is the "often". Fixed at all three links. The tab holds `navCounts.refresh`, which the provider allocates once, instead of the whole live-numbers value. The drawer keeps `onViewed` in a ref so `load` changes only when the report does — which also stops a request per chat message. And the dialog seeds on the report's id rather than on the object carrying it, so a different report and a fresh opening both still re-seed and a re-fetch of the same report no longer does. Two smaller things fall out of that. The preflight's server-side instruction is now applied only while the box still holds what was seeded, so an operator who starts writing before the probe answers is not typed over. And the dispatch intersects the ticked screenshots with what is still on the report, because the selection is no longer re-seeded to whatever is currently attached. The title field the report asked for already shipped in 165e9885 and is live; the report was filed about an hour before it went out.