What Shipped: July 2026
A short account of what changed in the product last month, and why. Most of it went into one thing: making the step where you connect an exchange less likely to go wrong, because that is where new users get stuck.
Key Takeaways
- Connecting Bybit is now one click. Bybit creates the API key itself and delivers it to Freya, so you never copy a secret or whitelist an IP address.
- If a key is missing a permission it needs, the connection screen now tells you which one instead of failing with a generic error.
- A key with no trading permission is detected immediately and named as read-only, rather than appearing to connect and then failing later.
- Charts now mark each take-profit level separately, so a partially closed position shows every leg instead of one blended exit.
- BitMEX was removed from the exchange list because BitMEX is shutting down entirely on 23 September 2026.
Connecting Bybit is now one click
Freya is a registered Bybit broker, and that status now does something visible for you. On Bybit you can approve Freya on Bybit's own screen and the exchange creates the API key itself, sends it straight to Freya, and binds it to our servers.
What that removes: copying a secret key that is shown once, pasting an IP address into an allowlist, and choosing permissions by hand. Those three steps are where most failed connections came from. One approval now sets up both Spot and Futures.
The manual route still exists and is unchanged. It remains the only route on Binance and OKX. Full walkthrough: Fast Connection to Bybit.
The connection screen now tells you what is actually wrong
Previously, a key that was missing a permission produced a generic failure. You knew it did not work; you did not know why, so the usual next step was to delete the key and try again, often with the same result.
The connection flow now verifies the permissions a key carries and reports the specific gap. If reading is disabled, it says so. If futures permission is missing, it says that instead. The message names the thing you need to change on the exchange, so the fix is one visit to the exchange rather than a guessing loop.
A related case got its own handling: a key created without any trading permission at all. That kind of key looks valid to a permission check and then fails at the first order, which is a confusing way to discover the problem. It is now identified as read-only at the moment you connect, with a message that says exactly that.
If you hit an error message you do not recognise, Can't Connect? Exchange API Key Errors Explained lists them.
Multiple take-profit levels are now visible individually on charts
If a bot closes a position in stages, that used to appear on the chart as a single exit. The individual take-profit legs were being executed correctly, but you could not see them separately, which made a staged exit hard to read after the fact.
Each leg is now marked on its own. A position that closed across three take-profit levels shows three markers, each with the amount that leg realised.
BitMEX was removed
BitMEX was listed as an upcoming exchange. It has been removed, and the reason is straightforward: BitMEX is shutting down entirely on 23 September 2026. Leaving it on the list would have promised an integration that can never exist.
The supported exchanges remain Binance, OKX and Bybit.
A new Engineering Notes section
The Academy now has an Engineering Notes section, separate from the user guides. It is written for developers and covers how the platform is built: what broke, what we changed, and what the trade-offs were.
It is English-only and it is not required reading for using Freya. If you are curious how the machinery works, the first piece is What I Underestimated Building a No-Code Trading Bot Platform.