3 people 8c92c7d423 Fix settings host sections showing "host not found" when the local daemon is stopped (#1749) ...

The local daemon's serverId persists while the daemon is stopped, so it isn't
among the connected hosts. The settings host-section resolver fell back to it
without checking it was connected, resolving the section to an unknown id and
rendering "host not found".

Extract the fallback into resolveActiveHostServerId, which only uses a serverId
when it names a currently connected host (covering both the picker selection and
the local daemon), and add regression tests.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-21 04:48:34 +08:00

..

app

Fix settings host sections showing "host not found" when the local daemon is stopped (#1749)

2026-07-21 04:48:34 +08:00

cli

Make workspace, agent, and schedule automation consistent (#2186)

2026-07-18 14:04:48 +02:00

client

Edit workspace files directly on web (#2270)

2026-07-21 04:41:19 +08:00

desktop

chore(release): cut 0.2.0-beta.1

2026-07-17 15:10:06 +02:00

expo-two-way-audio

chore(release): cut 0.2.0-beta.1

2026-07-17 15:10:06 +02:00

highlight

Edit workspace files directly on web (#2270)

2026-07-21 04:41:19 +08:00

protocol

Edit workspace files directly on web (#2270)

2026-07-21 04:41:19 +08:00

relay

chore(release): cut 0.2.0-beta.1

2026-07-17 15:10:06 +02:00

server

Edit workspace files directly on web (#2270)

2026-07-21 04:41:19 +08:00

website

feat(website): show real app in homepage hero

2026-07-18 17:43:38 +02:00