# Support Custom Protocol to Open Fibery Links in Desktop App

**URL:** <https://community.fibery.io/t/support-custom-protocol-to-open-fibery-links-in-desktop-app/9089>\
**Category:** Ideas & Features\
**Created:** [June 27, 2025, 7:53pm UTC](https://community.fibery.io/t/support-custom-protocol-to-open-fibery-links-in-desktop-app/9089 "2025-06-27T19:53:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\
**Post date:** [June 27, 2025, 7:53pm UTC](https://community.fibery.io/t/support-custom-protocol-to-open-fibery-links-in-desktop-app/9089/1 "2025-06-27T19:53:31Z")

</div>

I’m a big fan of the desktop app — I use it every day and really appreciate the focus and speed it provides over the browser version. That said, I often receive links to Fibery entities in Slack, email, or other tools (e.g. `https://example.fibery.io/Entity/View/123...`), and clicking them always opens in my web browser, even if the desktop app is already running.

This breaks flow a bit, since I’d much rather jump into the desktop app where I already have context open.

Please consider adding support for a custom protocol handler like:  
fibery://example/Entity/View/12345

This way, the desktop app could register itself with the OS to handle `fibery://` links — similar to how Notion, Obsidian, Linear, and others allow links to open directly in the desktop environment.

Thanks for all your hard work — love what you’re building.

---

<div class="post-metadata">

**Author:** ![Christopher\_Davy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/christopher_davy/32/12332_2.png) [@Christopher\_Davy](https://community.fibery.io/u/Christopher_Davy)\
**Post date:** [May 14, 2026, 4:58pm UTC](https://community.fibery.io/t/support-custom-protocol-to-open-fibery-links-in-desktop-app/9089/2 "2026-05-14T16:58:23Z")

</div>

I agree. This has been a major barrier to adoption of the desktop app in our organisation – colleagues are constantly getting pulled out of it when links are shared elsewhere. As a consequence, many are now defaulting to the browser version.

---

<div class="post-metadata">

**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\
**Post date:** [May 14, 2026, 5:12pm UTC](https://community.fibery.io/t/support-custom-protocol-to-open-fibery-links-in-desktop-app/9089/3 "2026-05-14T17:12:58Z")

</div>

Agree – it’s still a major pain point for our fairly small organization. If you have any votes to spare, I’d appreciate an up vote on the issue as it may help us both out!