You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The added automation integration does not work anymore #5072
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Platform
Desktop - macOS
Describe the bug
The feature mentioned in #4134 has been used normally since it went online.
It has recently become unavailable. When using custom integration to call URL Scheme, I get an error:
It looks like it was added to the whitelist, I don’t know why.
The reason why I mentioned that feature before was to make up for the lack of built-in integration. Now that I have added a whitelist, the various integrations I added before cannot be used, and many of them are niche applications.
If it is caused by the whitelist, it is recommended to remove the whitelist. Custom integrations are all added by users themselves, and parameters are defined by users themselves. Users who add them have expectations for the results, and there are no security risks.
Entry ID
No response
Relevant Information
No response
Reproduction Video
No response
Environment
No response
Validations
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
This issue is valid
Contributions
I am willing to submit a PR to fix this issue
I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
User-defined URL schemes are supported again. Built-in schemes continue to open directly, known dangerous schemes remain blocked, and any other valid custom scheme is opened only after confirmation in a native dialog. Canceling the dialog prevents the scheme from being handed to the OS.
Validation completed successfully:
Turbo format, typecheck, and lint: 22/22 tasks (0 errors)
Turbo tests: 9/9 tasks
Electron main-process tests: 65 passed
The fix will be included in a future desktop release.
Fixed in 7c220c6 and released in desktop v1.13.0: custom URL schemes work again, and schemes that aren't built in open after a native confirmation dialog.
Activity
github-actions commentedon Aug 11, 2026
Platform
Desktop - macOS
Describe the bug
The feature mentioned in #4134 has been used normally since it went online.
It has recently become unavailable. When using custom integration to call URL Scheme, I get an error:
It looks like it was added to the whitelist, I don’t know why.
The reason why I mentioned that feature before was to make up for the lack of built-in integration. Now that I have added a whitelist, the various integrations I added before cannot be used, and many of them are niche applications.
If it is caused by the whitelist, it is recommended to remove the whitelist. Custom integrations are all added by users themselves, and parameters are defined by users themselves. Users who add them have expectations for the results, and there are no security risks.
Entry ID
No response
Relevant Information
No response
Reproduction Video
No response
Environment
No response
Validations
Contributions
[-]添加的自动化集成都用不了了[/-][+]The added automation integration does not work anymore[/+]DIYgod commentedon Aug 15, 2026
Fixed on
devin 7c220c69a.User-defined URL schemes are supported again. Built-in schemes continue to open directly, known dangerous schemes remain blocked, and any other valid custom scheme is opened only after confirmation in a native dialog. Canceling the dialog prevents the scheme from being handed to the OS.
Validation completed successfully:
The fix will be included in a future desktop release.
DIYgod commentedon Sep 26, 2026
Fixed in 7c220c6 and released in desktop v1.13.0: custom URL schemes work again, and schemes that aren't built in open after a native confirmation dialog.