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/ip On 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/ip 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.   submitted by   /u/vitascivilis [link]   [comments]