5.7x
faster, measured end to end on one line (1.5 to 8.5 MB/s)
91%
of the line's capacity, sustained through a 275 MB IDE download
0
configuration to maintain once it is installed
How it works three routes, one proxy.
jtaccel is a local proxy Toolbox downloads through. What happens to each request is decided by what it is.
Toolbox connects to the local proxy
jtaccel listens on 127.0.0.1:8899 and takes Toolbox's CONNECT. From there it routes three ways, by what the destination is.
Auth is blind-spliced, never decrypted
Login and OAuth hosts are relayed as raw TCP. jtaccel does not parse them and cannot read them; your JetBrains session passes through untouched.
Large downloads split into sixteen
Rangeable responses of 32 MiB and up become sixteen parallel ranged GETs of 1 MiB each, straight to the CDN that was already serving them.
Reassembly is byte-exact
Segments return in order and are reassembled into the original stream, so Toolbox's own SHA-256 verification still passes. Speed never costs integrity.
Why it is safe to leave installed and trivial to take out.
Credentials are never read
Authentication traffic is spliced at the TCP layer rather than decrypted, so there is no key handling and no certificate parsing on the path.
Toolbox keeps verifying
The reassembled file is identical to the one Toolbox asked for. Its checksum check runs afterwards, exactly as before.
Reversible
Turn it off and Toolbox downloads the way it always did. Nothing about the IDE is patched or modified.
One tool, three systems
Windows, macOS and Linux, from one install script and one codebase.
curl -fsSL https://github.com/abd3lraouf-studios/jetbrains-toolbox-accelerator/releases/latest/download/install.sh | shmacOS and Linux. Windows steps are in the README.
Questions
Does it modify JetBrains Toolbox?
No. Toolbox is never patched, injected into or configured differently from the outside. jtaccel is a proxy it downloads through, and turning it off returns you to the stock downloader.
Is the download still verified?
Yes, by Toolbox itself. Segments are reassembled into a byte-for-byte identical stream, so the SHA-256 check Toolbox already performs still passes.
What happens to my JetBrains login?
Nothing. Authentication and OAuth hosts are relayed as raw TCP and never decrypted, so your session reaches JetBrains exactly as it would without jtaccel in the middle.
Why is it faster?
Toolbox's downloader uses one connection, and one connection does not fill the line. Sixteen parallel ranged requests against the same CDN do. The measurement, method and charts are in the README.
Sixteen streams, and the waiting is mostly over.
Toolbox downloads pulled in parallel and checked byte-exact against the original, so nothing is traded for the speed. One command on Windows, macOS and Linux.
Get it on GitHubFree · MIT · Windows, macOS and Linux
jtaccel