claude-code - 💡(How to fix) Fix [FEATURE] Option to start minimized to system tray on Windows startup (restore previous behavior) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56436Fetched 2026-05-06 06:28:05
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×2closed ×1unlabeled ×1

Fix Action

Fix / Workaround

I tried several workarounds without success:

  1. Task Manager Startup disable — The only working workaround is to fully disable Claude Desktop from starting up via Task Manager → Startup tab. This prevents the window from opening, but also means the app doesn't run in the background at all — losing the system tray presence entirely.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

In a previous version of Claude Desktop for Windows, there was an option to control whether the main application window opens automatically on startup, or whether the app simply starts in the background (system tray only). This option appears to have been removed in a recent update. Currently, when Claude Desktop launches at Windows startup, the main window always opens automatically, which is disruptive for users who prefer the app to run silently in the background until needed.

Proposed Solution

Restore the previous toggle that allowed users to choose between opening the window on startup OR starting minimized to the system tray only. This is a standard UX pattern used by many Windows apps like Discord and Slack.

Alternative Solutions

I tried several workarounds without success:

  1. VBScript at startup — Created a .vbs script using WshShell.Run with SW_HIDE (0) and SW_SHOWMINNOACTIVE (7) flags, placed in the Windows Startup folder (shell:startup). The script launches the app but Claude Desktop still opens its main window regardless of the window style flag passed.

  2. Electron --hidden flag — Tried passing --hidden as a CLI argument to claude.exe via the VBScript. The flag had no effect — the window still appeared on startup.

  3. Shortcut with "Minimized" window style — Created a Windows shortcut pointing to claude.exe with the "Run: Minimized" property set. Claude Desktop ignored this and opened its window normally.

  4. Task Manager Startup disable — The only working workaround is to fully disable Claude Desktop from starting up via Task Manager → Startup tab. This prevents the window from opening, but also means the app doesn't run in the background at all — losing the system tray presence entirely.

Note: The "Run on Startup" toggle in Settings is also currently bugged on Windows — it resets itself back to ON after being turned off (see related issue #48078).

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

I start my PC in the morning. Claude Desktop launches automatically but I don't need it right away — I just want it ready in the system tray for when I need it. Instead, the window opens on top of everything and I have to close it manually every time.

Additional Context

No response

extent analysis

TL;DR

The most likely fix is to restore the previous toggle option in Claude Desktop's settings to allow users to choose between opening the window on startup or starting minimized to the system tray only.

Guidance

  • Investigate the code changes made in the recent update to identify why the option to control the startup behavior was removed.
  • Review the implementation of the --hidden flag in Electron to understand why it had no effect when passed as a CLI argument.
  • Consider adding a new setting or configuration option to allow users to control the startup behavior, similar to the previous toggle.
  • Look into fixing the related issue #48078, where the "Run on Startup" toggle in Settings resets itself back to ON after being turned off.

Example

No code snippet is provided as the issue does not contain sufficient technical details.

Notes

The issue lacks information about the specific code changes made in the recent update, making it difficult to provide a more detailed solution.

Recommendation

Apply a workaround by fixing the related issue #48078 and exploring alternative solutions, such as using a different approach to launch the application in the background.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING