Feature request: Option to start application minimized to system tray
@RubenKelevra is already working on this.
Since Aug 25, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- desktop
Research direction
The issue does not name implementation files, tests, or entry points. Start by tracing startup behavior, the Preferences UI, and system tray/menubar handling across supported platforms. Done means a Preferences toggle starts the application silently with the tray icon visible when enabled, while the default preserves the current window-opening behavior.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
IPFS Desktop acts primarily as a background node/daemon for the decentralized web. However, having the main window pop up and steal focus every time the system starts (or the user logs in) interrupts the user workflow and feels intrusive for a background service.
Describe the solution you'd like
The Request: Add an option to launch IPFS Desktop minimized to the system tray/menubar.
Suggested behavior:
Add a toggle in Preferences: "Start application minimized to tray".
- When enabled: The app starts silently in the background (tray icon appears) without opening the main window.
- When disabled (default): The current behavior is maintained.
Why this is important:
- Better UX: Allows IPFS to run seamlessly in the background without manual intervention.
- Workflow: Users don't have to manually close the window at every startup.
- Expectation: Standard behavior for background services/daemons (like Dropbox, Steam, or VPN clients).
Alternatives considered
- Manually closing the window at every startup.
- Dominant language
- JavaScript
- Stars
- 6.6k
- Forks
- 908
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ipfs/ipfs-desktop
-
kind/bug need/triage
Difficulty 4/5 3-5 days Newbie friendliness 52/100
ipfs/ipfs-desktop#3218 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
ipfs/ipfs-desktop#3215 · 1 comment · 1 reaction ·
-
kind/bug need/triage
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ipfs/ipfs-desktop#3206 ·
-
need/analysis need/community-input P3 topic/linux
Difficulty 5/5 Over a week Newbie friendliness 35/100
ipfs/ipfs-desktop#3042 · 2 comments · 1 reaction ·
-
exp/intermediate P3 status/blocked
Difficulty 5/5 Over a week Newbie friendliness 35/100
ipfs/ipfs-desktop#3040 · 3 comments ·
All issues in ipfs/ipfs-desktop
Similar issues
-
chore cloudflare-workers consistency d1 difficulty: easy documentation dx enhancement good first issue help wanted hygiene javascript maintenance priority: P3 seo
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MattiaPARRINELLO/backstage#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·