[#9] Restart Claude Desktop convenience button #9

Closed
opened 2026-07-02 00:50:58 -04:00 by the_og · 1 comment
Owner

Problem

Nearly every MCP troubleshooting thread ends in "you have to fully quit Claude, not just close the window — check the tray/Activity Monitor." This is a step users reliably get wrong after making a valid config change, because:

  • Claude has a tray icon that keeps it alive after closing the window.
  • There is no in-app "restart to apply changes" prompt.

Proposed solution

After a successful save, offer a Restart Claude Desktop button:

  • macOS: pkill -x "Claude" then open -a Claude
  • Windows: kill the Claude process, then relaunch via the Start menu path
  • Linux: pkill claude && claude (or equivalent)

Scope to Claude Desktop only — Claude Code does not have this problem.

Acceptance criteria

  • Button appears in the post-save confirmation toast/dialog.
  • On click, Claude Desktop fully quits and relaunches.
  • Config change is live without any manual steps.
  • Platform-specific logic is abstracted behind a single restart_claude_desktop() function in bcc_core.py.
  • Does not appear when the active profile is Claude Code.

Relevant code

  • New — hook into the save-confirmation flow in bcc.py (~line 1432 area, near the existing backup-note toast)
  • bcc_core.py — new restart_claude_desktop() function
## Problem Nearly every MCP troubleshooting thread ends in "you have to *fully* quit Claude, not just close the window — check the tray/Activity Monitor." This is a step users reliably get wrong after making a valid config change, because: - Claude has a tray icon that keeps it alive after closing the window. - There is no in-app "restart to apply changes" prompt. ## Proposed solution After a successful save, offer a **Restart Claude Desktop** button: - macOS: `pkill -x "Claude"` then `open -a Claude` - Windows: kill the Claude process, then relaunch via the Start menu path - Linux: `pkill claude && claude` (or equivalent) Scope to **Claude Desktop only** — Claude Code does not have this problem. ## Acceptance criteria - Button appears in the post-save confirmation toast/dialog. - On click, Claude Desktop fully quits and relaunches. - Config change is live without any manual steps. - Platform-specific logic is abstracted behind a single `restart_claude_desktop()` function in `bcc_core.py`. - Does not appear when the active profile is Claude Code. ## Relevant code - New — hook into the save-confirmation flow in `bcc.py` (~line 1432 area, near the existing backup-note toast) - `bcc_core.py` — new `restart_claude_desktop()` function
the_og added the P1 label 2026-07-02 00:50:58 -04:00
Author
Owner

We need to make sure that blanket killing claude* does not kill unwanted processes, such as claude code or design (if running)

We need to make sure that blanket killing claude* does not kill unwanted processes, such as claude code or design (if running)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: the_og/better-claude-config#9