Additional throne:// deeplinks
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- desktop, networking
Research direction
Start by locating how the app handles tunnel start and stop actions and routing mode changes, then check how it registers and dispatches platform URL schemes. Define how the proposed actions and target parameters map to those entry points, including behavior when a profile cannot be found. Done when the listed tunnel and routing actions can be triggered through throne:// links across supported platforms.
Written by the indexing model from the issue text.
Description
Feature Request: Deep link / URL scheme support for core actions
Summary
Add custom URL scheme/deep link support (e.g., throne://...) to allow external automation tools (such as Shortcuts, Tasker, shell scripts, or stream decks) to trigger core tunnel and routing actions without opening the main UI.
Proposed Actions & Parameters
- Tunnel Control
- start / stop / toggle
- Target selection parameters:
- target=last_used (default)
- target=lowest_ping (automatically selects the lowest-latency config)
- target=<profile_id_or_name>
- Routing Mode Control
- mode=tun / mode=proxy
- action=on / action=off / action=toggle
Example Schema Ideas
- throne://tunnel/toggle?target=last_used
- throne://tunnel/start?target=lowest_ping
- throne://mode/tun?state=toggle
- throne://mode/proxy?state=on
Use Case
Enables headless control, automation workflows, lock screen widgets, and quick hardware shortcuts (e.g., hotkeys or Macro Pads) for switching nodes and toggling routing modes on the fly.
- Dominant language
- C++
- Stars
- 7.5k
- Forks
- 447
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 20
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 throneproj/Throne
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
throneproj/Throne#2046 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
throneproj/Throne#2043 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
throneproj/Throne#2035 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
throneproj/Throne#2001 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
throneproj/Throne#2049 ·
Maintainers usually reply within 2 days
All issues in throneproj/Throne
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
sandialabs/Fenix#172 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
scp-fs2open/fs2open.github.com#7953 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SteveMacenski/slam_toolbox#907 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day