You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two UX gaps spotted while testing the sidecar in Claude Desktop.
1. Post-save banner read "Restart the add-on for changes to take
effect" regardless of how the user actually runs ha-mcp. Claude
Desktop / Docker / standalone users were told to do something that
doesn't exist in their install. The banner text now reads from
/api/settings/info and rewrites itself per mode:
* is_addon → "Click 'Restart Add-on'" (the button is right there)
* is_sidecar → "Fully quit and reopen your MCP client (Claude
Desktop: tray icon → Quit, then relaunch; Claude Code: close
the terminal session)"
* otherwise → "Restart your ha-mcp process (Docker container,
systemd service, or however you launch it)"
2. The sidecar's "Stop settings server" button was an accent-blue
primary button sitting near the page's routine toggles. A
misclick silently writes ~/.ha-mcp/settings_ui_disabled, which
then prevents the sidecar from respawning on *every* subsequent
Claude Desktop / ha-mcp launch — the only recovery is manual
filesystem cleanup. Two mitigations:
* Renamed to "Permanently disable settings server" and given a
new .danger-btn class (red border + danger-red text on a
transparent fill) so the destructive semantic is visible
without reading the label.
* confirm() now leads with the permanence and spells out the
two-step recovery (delete the marker file AND unset
HA_MCP_DISABLE_SETTINGS_UI). The old wording read like a soft
"stop for now, autostart later" — the new wording reads like
a commitment.
The new \n sequences in the confirm() prompt go through the JS
syntax regression test added in 249bcd1
(test_rendered_script_parses_as_javascript) so any future raw-newline
slip-up still fails fast.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
title="Stops this settings UI sidecar process and writes a disable sentinel so it won't respawn on next ha-mcp start. Delete ~/.ha-mcp/settings_ui_disabled to re-enable."
526
-
>Stop settings server</button>
533
+
<button class="danger-btn" id="stopSidecarBtn"
534
+
title="Permanently disables the settings UI: stops this server AND writes ~/.ha-mcp/settings_ui_disabled so it does not respawn on future ha-mcp launches. Delete that file to re-enable."
0 commit comments