Unblock Slack and get back into your workspace

Your browser never talks to Slack. It talks to TrickyBird, which fetches the page over its own connection and rewrites the HTML, CSS, and JavaScript on the way through, so every link, image, and request inside the page points back at TrickyBird’s address instead of out at Slack. A small script stays behind in the tab to catch whatever the client asks for later, which on Slack is nearly everything. That is why a filter on the network has nothing of Slack’s to match on: what leaves your browser is addressed to TrickyBird. It is also why there is nothing for you to set up, no proxy field to fill in inside a settings menu you may not be allowed to open.

Getting into a workspace is not 1 page but a walk across hosts. It starts at slack.com, hands you over to app.slack.com, and finishes on your workspace’s own host (the one with your team’s name in it). A session that begins on one Slack host and has to finish on another is the case that breaks a proxy quietly, because the host taking the handoff is stricter about where the request appears to have come from than the one that sent you. It has to arrive through TrickyBird’s address like everything else. When it arrives intact, the walk ends at your workspace’s sign-in instead of an error page.

After that, Slack is less a page than an app holding a connection open for as long as the tab is on screen, and TrickyBird tunnels that connection through the proxy the same way it carries the page itself. Telegram, WhatsApp and Discord keep their own live connections open the same way.

Yes, and it is Slack’s own way in, not anything TrickyBird arranges: you give the address on the account, Slack sends a code to that mailbox, you type the code back, and Slack decides whether to let you through. It went through the proxy on 5 August 2026. TrickyBird adds no sign-in of its own and does not get around Slack’s.

The client loaded after the code: the workspace’s channel list down the side, direct messages under it, the message box at the bottom. We wrote in a channel and Slack confirmed it. Then we reloaded the page from scratch, and the message was still in the channel. That reload is the part that matters. Any client can put your own words on screen before anything has left the tab; finding them again after a full reload means Slack wrote them down.

That was one run, on one test workspace. We have not used it long enough to tell you how a work account you depend on behaves over weeks, and no automated check will ever stand behind this part, because the sign-in code arrives by email and our checks cannot read a mailbox.

The same as always. Slack sees a connection arriving from TrickyBird rather than from your own address, so the route does change. Signing in is a separate matter. The moment you do, Slack knows which account is talking, and your workspace’s own admin tools show your activity exactly as they otherwise would. A proxy changes the route a request takes, not who you are once you have named yourself.

On our side, cookies from the site you open are held in a store keyed to your session and to that site, and each entry lives about an hour from the last time it changed. To run the service and curb abuse, the edge keeps a shortened form of your IP address, the hostname of the site you connected to, and basic response details, kept for at most 48 hours, with no TrickyBird account for any of it to attach to. Our security page sets that out in full.

One habit is worth forming before a work account goes through any of this: open 1 sensitive site per session. Everything you open in the same session is served through the same TrickyBird address, so your browser treats it all as a single site underneath, and the separation between them is for tidiness, not a security wall. A fresh session, or a new private window, keeps a work Slack apart from whatever else you have open.

Whose network is it? That decides it, and it is a rules question rather than a legal one. If the network belongs to an employer or a campus, its acceptable-use policy is the rule that applies, not the law: breaking it is not a crime, but the consequences are real and they are enforceable, because it is their network and their equipment. Read it before you decide. Knowing the rule is not the same as being told to break it, and the choice stays yours to make with your eyes open.

A second line is Slack’s own. Where Slack itself limits who it can serve, that is Slack’s restriction rather than a network block, and TrickyBird is not a way around it. Our Acceptable Use Policy says where we stand, and the guide on proxies and the law covers the rest.