Hi, I see the latest version of JetBrains Toolbox has introduced the jetbrainsd daemon. It handles jetbrains:// URIs.
I’m just wondering what are the use case for jetbrains:// URIs.
Ho, and 35MB in memory just for an URL handler, seriously… 
Thx
One of the use cases I can think of is installing the plugin from the Marketplace. Right now, a specific plugin’s website requests localhost on a range of ports to discover which IDEs are currently open, filters those that support the plugin’s installation, and provides you with the Install in IDE button. This button runs another request on that port to initiate the plugin installation.
Recently, Chrome started showing a security notification that the website is trying to communicate with localhost, which raises additional concerns.
Using the jetbrains:// protocol will shorten that path, reduce port scanning, increase security, and delegate action to Toolbox, which knows what is available and currently running.
It would be cool to allow plugin developers to leverage this URI handler, too.
I can think of a handful of use cases, but one that jumps to mind is being able to deep-link into the settings of a specific plugin (or plug-in setting). And if said plug-in wasn’t installed in the users IDE, then default to the plugin search result in the IDE.
+1. And make it (the tool and the api) open, if this is not the case already. It would be great.
It is in plans, plugins will be supported, although the tool itself is closed source so far and not meant to be used by non-JetBrains IDEs
Awesome to hear! If there’s a YT to track the functionality for plug-in developers, please share - that’d be great!
