Files
goose/ui
Taylor Ho def6cca68a fix: sync message IDs between frontend and backend for edit/retry truncation
P0 fix: the frontend generated client-side UUIDs for messages while the
backend independently generated tmsg_{uuid} IDs. When edit/retry sent
the client UUID as truncate_before_message_id, the backend lookup found
nothing and never truncated.

Fix:
- Frontend sends messageId on PromptRequest (ACP unstable_message_id)
- Server uses args.message_id as the thread message ID instead of
  generating a new one, so both sides share the same ID
- Replay chunks now carry message_id so loaded sessions also have
  correct IDs for future edit/retry operations

Signed-off-by: Taylor Ho <taylorkmho@gmail.com>
2026-04-16 15:26:06 -10:00
..
…