Download the Bridge
Step 4 of the setup, first part. One file ends up on your machine. It fetches its own credentials when you pair it, so there is no token to copy and no configuration file to move. The video for step 4 covers this page and the next one.
This step happens in Settings → Broker on t1.ordertune.com.
→ Open the Broker tab directly (opens in a new tab)
If you land on a different screen, you are signed out — sign in and the link takes you there.
Accept the Bridge Terms of Service
The Broker tab shows a box with the Bridge Terms of Service (opens in a new tab) and a checkbox. Read it and tick the box.
This is not a formality you can skip and come back to. Without it, releasing a
signal stops with bridge_tos_not_accepted — the software runs on your machine
and sends orders to your account, and that needs your explicit agreement rather
than a silent one.
Download the program
The Broker tab has a switch above the download button. Pick your system there — it decides which file the button offers.
Click Download ordertune-bridge-ibkr.exe. About 32 MB, and that one file is the whole program.
Your browser may warn that an executable is unusual. It is not signed, and Windows will have something to say about that when you start it — Start it and pair it shows exactly which dialog and which button.
Download it onto the machine that runs Trader Workstation — not onto the machine you are reading this on, if those are two different computers. The Bridge has to reach Trader Workstation over a local connection, and "local" means the same machine.
What you no longer need
Until September 2026 this step also produced a second file, bridge.env, with
an access token you had to keep and carry to the right folder. That is gone.
The Bridge now writes that file itself when you pair it, on the next page. The token never passes through your hands, which also means there is nothing to lose and nothing to store.
If the machine that runs the Bridge has no browser — a headless server, or one you only reach over a terminal — the answer depends on your system.
On Windows the Bridge opens its setup window in a browser, so pairing cannot happen there. The Broker tab still offers the old route under No browser on that machine? Get a bridge.env file instead.
On Linux this is the normal case, not the exception. Pairing happens in
the terminal with --pair, and the installer does it for you. There is
nothing to download and nothing to carry across.
Next: Start it and pair it.