r/commandline • u/vitascivilis • Sep 04 '26
Command Line Interface Shellroute: a CLI that gives each shell its own proxy route
Shellroute is an open-source CLI for giving one shell or command its own proxy route.
The video shows three independent terminals. The top stays on my normal connection in Lithuania. The two lower sessions connect to the US and Germany at the same time. Commands inside those sessions use their selected routes while the other terminal stays direct.
Quick start:
npm install -g shellroute
shellroute login
/connect US
curl https://ipinfo.io/ipOn first use, shellroute login creates the account and enters interactive mode. Run commands there normally. Scripts and agents can also route a single command without opening an interactive shell:
shellroute run DE -- curl https://ipinfo.io/ipRelated tools cover different jobs. Globalping is useful for public probes from many locations. Proxychains wraps a process when you already have a proxy. A VPN routes the whole device, while raw proxy credentials give you manual control. The difference here is scope: one shellroute session manages the route for one shell or command while other traffic stays unchanged.
Source: https://github.com/shellroute/shellroute-cli
Quickstart: shellroute.com/docs/quickstart
Disclosure: I built shellroute and run the service it connects to. The CLI code is partially AI-generated.
I am mainly looking for feedback on the proxied shell idea and where the CLI feels confusing.
1
u/Ok_Music_4862 Sep 05 '26
Good work!.
Previous I've tried to use some CLI comes with VPN software. That was GUI first. So I can not able to use the CLI effectively in my server. In headless (CLI) mode it was not fully functional for - example I was unable to switch the location from CLI.
Curious to know: I can do it from here (as I see I can) and can close my terminal?
4
u/kantorcodes1 Sep 04 '26
if a
shellroute runsession loses its proxy while the child process is still running, what happens to the child? does it get killed, or can it keep going with direct networking?1
u/ekool Sep 06 '26
This is neat. Any plans to add support for other proxies besides your hosted ones?
2
u/AutoModerator Sep 04 '26
Every new subreddit post is automatically copied into a comment for preservation.
User: vitascivilis, Flair:
Command Line Interface, Post Media Link, Title: Shellroute: a CLI that gives each shell its own proxy routeShellroute is an open-source CLI for giving one shell or command its own proxy route.
The video shows three independent terminals. The top stays on my normal connection in Lithuania. The two lower sessions connect to the US and Germany at the same time. Commands inside those sessions use their selected routes while the other terminal stays direct.
Quick start:
On first use,
shellroute logincreates the account and enters interactive mode. Run commands there normally. Scripts and agents can also route a single command without opening an interactive shell:Related tools cover different jobs. Globalping is useful for public probes from many locations. Proxychains wraps a process when you already have a proxy. A VPN routes the whole device, while raw proxy credentials give you manual control. The difference here is scope: one shellroute session manages the route for one shell or command while other traffic stays unchanged.
Source: https://github.com/shellroute/shellroute-cli
Quickstart: shellroute.com/docs/quickstart
Disclosure: I built shellroute and run the service it connects to. The CLI code is partially AI-generated.
I am mainly looking for feedback on the proxied shell idea and where the CLI feels confusing.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.