goose

mirror of https://github.com/block/goose.git synced 2026-07-17 12:56:20 +02:00

Files

T

History

morgmart 290870ad2a fix: fast-fail on_load_session when thread ID is missing or wrong

When the UI sends a legacy session ID (e.g. "20260415_1") instead of a
thread UUID, on_load_session previously hung indefinitely because
get_thread returned an error that was silently swallowed or never
reached the client. This caused a 30-second frontend timeout and a
blank conversation view.

Now the handler checks whether the requested ID corresponds to a known
session in the sessions table, and returns an immediate, diagnostic
error explaining what went wrong:
- "Session X has linked thread Y, but was sent as the session_id
  instead of the thread UUID" — tells the engineer the UI needs to
  send the thread UUID instead.
- "Session X exists but has no linked thread" — the session was not
  fully created via ACP (thread creation failed or was skipped).
- "Session not found" — the ID doesn't match anything.

Also bumps tauri-plugin-dialog to "2" to fix a version mismatch
warning with @tauri-apps/plugin-dialog v2.7.

Signed-off-by: morgmart <98432065+morgmart@users.noreply.github.com>

2026-04-14 19:59:11 -07:00

.changeset

ci: switch npm publish to OIDC trusted publishing (#8454 )

2026-04-10 20:30:45 +00:00

acp

feature: provider & model config (#8515 )

2026-04-14 10:55:21 -04:00

desktop

chore(release): bump version to 1.31.0 (minor) (#8527 )

2026-04-14 14:48:16 +00:00

goose2

fix: fast-fail on_load_session when thread ID is missing or wrong