# What the client patch changes

Blisscord runs the official Discord app, pointed at Blisscord instead of Discord. On a computer that is done by a small patch; in a browser, `https://app.discord.community` serves Discord's web app with the same patch already applied. This page lists everything the patch does, so you can decide for yourself whether you are comfortable running it.

You can install the patch with a download from `https://discord.community/tools` (a double-click installer for macOS and Windows) or with one command. Everything involved is plain text you can read before running it:

- macOS and Linux patcher: `https://discord.community/dl/stable.sh`
- Windows patcher (PowerShell): `https://discord.community/dl/stable.ps1`
- The injected script: `https://discord.community/dl/inject.js`
- The installers only download the patcher above and run it: `https://discord.community/dl/Blisscord-macOS.zip` (two `.command` files) and `https://discord.community/dl/Install-Blisscord.cmd`

The injected script has one source. The web client at `app.discord.community` runs it, and a patched desktop app downloads that same file each time it starts, so all of them behave the same and a fix reaches everyone without reinstalling anything.

## In a browser

`https://app.discord.community` is Discord's web app with the injected script already applied, so nothing is installed or changed on your computer. Chrome and Edge can install it as an app with its own window: the page links a small app description (`/manifest.webmanifest`) with the name Blisscord and an icon, and nothing else is added for that. Removing the installed app is done from its own menu, as with any installed site.

## What it changes on your computer

- **One Discord install.** The patcher asks which Discord channel to convert (Stable, PTB or Canary) and touches only that one. Your other Discord installs are left alone, so you can keep using real Discord side by side.
- **One file is replaced, two are added, all in one folder.** Inside that install, `discord_desktop_core/index.js` is replaced by a short wrapper. Next to it the patcher saves the original file as `index.blissorig.js` (the wrapper loads it after setting itself up), and a copy of the injected script as `index.blissbaked.js`. While Discord runs, the wrapper keeps the last copy of the script it downloaded next to them as `index.blissinject.js`. No other Discord file is changed.
- **Optional: a background process that puts the patch back after Discord updates.** When Discord updates itself it replaces `index.js` with its own copy, which removes Blisscord. The patcher asks whether you want a small background process on your computer that notices this and patches that one Discord install again, so you never have to run the patcher again. It is only created if you say yes; say no and the patch is a one time patch you re-run after Discord updates. You can turn it on or off later in Discord, under Settings > Blisscord App > Discord updates (desktop only; Discord confirms before changing anything), or with the patcher. It is:
  - macOS: a launchd agent, `~/Library/LaunchAgents/community.discord.blisscord.repatch.<channel>.plist`. It runs when Discord's module folder changes and every five minutes. macOS may show a "Background Items Added" notice for it.
  - Windows: a hidden PowerShell watcher started at sign-in from the registry value `HKCU\Software\Microsoft\Windows\CurrentVersion\Run\BlisscordRepatch-<channel>`. It waits for `index.js` files to change under that Discord folder and also checks every five minutes.
  - Linux: systemd user units `blisscord-repatch-<channel>.path`, `.service` and `.timer` in `~/.config/systemd/user`.

  The agent runs a saved copy of the patcher, kept with the last copy of the script in `~/Library/Application Support/Blisscord` (macOS), `%LOCALAPPDATA%\Blisscord` (Windows) or `~/.local/share/blisscord` (Linux). It only acts when that install's `index.js` is Discord's own file again. It never touches another Discord install, never replaces the developer capture tap, and needs no administrator rights. If Discord had already started on the update before the agent got to it, that one session talks to real Discord; quit and reopen Discord and it is on Blisscord again. To answer the question in advance, pass `--agent` or `--no-agent` (macOS, Linux) or `-Agent` or `-NoAgent` (Windows); when the patcher cannot ask (no terminal) it does not create the process. `agent-on` and `agent-off` (`-Mode agent-on`, `-Mode agent-off`) add or remove only the background process and leave Discord's files alone.
- **Undoing it is one step.** Unpatching removes the agent first, puts the original file back and deletes the files listed above:
  - macOS: double-click `Uninstall Blisscord.command` from the same zip, or run `curl -fsSL https://discord.community/dl/stable.sh | bash -s unpatch`
  - Windows: run `https://discord.community/dl/Uninstall-Blisscord.cmd`, or in PowerShell `& ([scriptblock]::Create((irm https://discord.community/dl/stable.ps1))) -Mode unpatch`
  - Linux: `curl -fsSL https://discord.community/dl/stable.sh | bash -s unpatch`

  Use `status` in place of `unpatch` to see whether an install is patched and whether the agent is on.

Nothing else on your computer is changed, and no settings outside that Discord install are touched apart from the agent above.

The installers are not signed, so the first time you open one your system warns you. On macOS 15 and later, open System Settings, Privacy & Security, and click Open Anyway; on earlier versions, Control-click the file and choose Open. On Windows, SmartScreen shows "Windows protected your PC": click More info, then Run anyway.

## What the wrapper does when Discord starts

- **Points Discord's network requests at Blisscord.** Requests the app makes to `discord.com/api`, `cdn.discordapp.com` and `media.discordapp.net` are redirected to `discord.community`, `cdn.discord.community` and `media.discord.community`.
- **Removes Discord's Content Security Policy header** from the pages the app loads. That header lists which servers the app may talk to, and it only names Discord's, so without removing it the app could not reach Blisscord at all.
- **Loads the current injected script.** It adds the last saved copy of the script (below) to Discord's window as it opens, so the app never starts unpatched and never waits for the network. At the same time it asks `https://discord.community/dl/inject.js` whether there is a newer one. It asks only that address, over HTTPS with the certificate checked, follows no redirects, and uses what comes back only if its fingerprint matches the one the server sends with it. A newer script that arrives while the window is still loading is used straight away (the window reloads once); otherwise it is used from the next start. If Blisscord cannot be reached, Discord starts normally with the saved copy.
- **Checks once whether the wrapper itself is current.** About eight seconds after Discord starts, the wrapper asks `discord.community` whether it is up to date. All it sends is a 12-character fingerprint of the wrapper, one of the script it is running, and the name of your operating system (for example `darwin` or `win32`) so the reply can name the right command. No account details, no token. If the wrapper is out of date it shows a dialog asking you to run the installer again, with a button that copies the command; if Blisscord is unreachable it does nothing.

## What the injected script does

The injected script runs inside the Discord app, on your computer or in your browser. It does these things and nothing else:

- **Endpoints.** Sets the app's own configuration so the API, the gateway (the live connection), the CDN, the media proxy, QR code sign-in, and invite, gift and server template links all use Blisscord's hosts instead of Discord's. Your sign-in and your messages therefore go to Blisscord, not to Discord.
- **Gateway connection.** If anything in the app still tries to open Discord's gateway address, the script points it at Blisscord's instead. It also clears an old cached gateway address the app may have saved from real Discord.
- **Error reports.** When the app hits an error (an error message in its console, an uncaught exception, or a screen that fails to draw), the script sends the error text to `discord.community` so we can find and fix the bug. Each report is at most 3,800 characters. It is sent with your session, so we can tell which account and which client build saw it, and Blisscord staff can read it. Discord's own error reporting is switched off on the web client, so these reports go to Blisscord rather than to Discord.
- **A few small fixes to the app, so features work here.** The script makes targeted edits to specific parts of Discord's app code while it loads. Each one is listed here:
  - **Server badges.** Blisscord has server badges Discord does not (for example "Blisscord Official"). The script fetches the public list of those badges from `discord.community/api/v9/guild-badges`, without your account or cookies, and teaches the server header to draw them.
  - **AI tag.** Discord's app still contains a green "AI" tag but no longer uses it. The script switches it back on for accounts that Blisscord staff have marked as AI, with a checkmark for verified ones. It shows beside the name in messages, the member list and profiles, where an app's "APP" tag would go.
  - **AI session lines.** In an AI server, the AI bot's tool calls, file reads and edits and session notices are posted as Blisscord's own message types, which Discord's app does not know. The script draws them as compact system lines with a small icon (for example ✏️ for an edit, ⚙️ for a command), the way Discord draws "pinned a message". A person named in a line (for example "Settled by @name") is shown as a mention with their name, read from what the app already knows. A line that belongs to a helper agent starts with that agent's tag (see the next item). Without the script these lines are not shown.
  - **Agent tags.** In an AI server, a message written by one of the AI's helper agents starts with a small line naming the agent. The script takes that line off the message and shows the name as a tag beside the bot's name instead, the way Discord shows "SERVER" on an announcement, for example "AGENT 2". Only a bot's messages get a tag this way. Without the script you see the small line.
  - **What the AI is doing.** In an AI server the bot's typing line says what it is doing, with a small icon, for example "✏️ Clanker is editing server.go", instead of "Clanker is typing". The text comes from Blisscord with the typing signal; the script keeps it (Discord's app would drop it) and shows it while only that one member is typing.
  - **Official messages are opt-in.** In verified servers Discord's app marks every message as "official" when the sender is allowed to post official messages, which on Blisscord would be every message by a server's owner or admins. The script stops that, so a message only becomes official when someone picks "Mark as Official" in its menu.
  - **Invite code on sign-up.** Blisscord accounts need an invite while sign-up is invite only, and Discord's sign-up form has nowhere to put one. The script adds an "Invite code" box at the top of that form and sends what you type with the sign-up, as Discord sends an invite when you sign up from an invite link. You can paste the code or the whole link, and an invite link fills the box for you. To know whether to show the box, the script asks `discord.community/api/v9/instance/registration`, without your account or cookies; when Blisscord staff open sign-up to everyone, or close it, the box is not shown. A code that came in the link is still sent then, so whoever invited you is credited.
  - **Blisscord in Settings.** User Settings gets a Blisscord section, built from the same parts as the rest of Settings. In the desktop app, Blisscord App also shows whether the background process above is on, with a button to turn it on or off; Discord asks you to confirm, then runs the patcher from `discord.community` to add or remove only that process. The web app does not show it. Invites lists your invite links (make one, copy it, revoke it) and the people who joined with them, with the orbs each one earned you. Blisscord App links to the install steps for your other devices, this page, the getting started guide and the developer portal. The data comes from `discord.community/api/v9/users/@me/registration-invites`, with your session.
  - **Blisscord in Server Settings.** Server Settings gets a Blisscord section, built from the same parts as the rest of Server Settings and shown only to members who can manage the server (the server's right-click menu gets one Blisscord entry under Server Settings). Features says, in plain words, what Blisscord has switched on for the server (voice channels, the partner badge, the verified checkmark and the rest), where its three applications stand, and lists every feature flag it carries. Voice, Partner Program and Verification are the applications for those three: a short form for each, which only the owner and administrators can send, or, when the server has it, what it gives you (for partners and verified servers, the badge and the profile badge that comes with it). Application History lists every application the server has sent, with the answers, the decision and any note from the reviewer. The data comes from `discord.community/api/v9/guilds/<server>/blisscord` and `.../blisscord/requests`, and an application is sent to `discord.community/api/v9/guilds/<server>/requests`, all with your session.
  - **Links to a Settings page.** A link to the app can name a Settings page with `?bliss_settings=` in its address, for example `https://app.discord.community/channels/@me?bliss_settings=invites`, which `discord.community/invites` sends you to. Once you are signed in and the app has loaded, the script opens Settings at that page (only Blisscord > Invites so far) and takes the parameter out of the address, so a reload does not open it again. Nothing is sent anywhere.
  - **Invite people from Add Friend.** The Add Friend page gets an "Invite people to Blisscord" card beside "Explore Discoverable Servers", and the Add Friend menu a matching row; both open Settings at Invites. Discord's own "Copy friend link" keeps working: on Blisscord the link it copies is one of your invite links, and whoever signs up with it becomes your friend.
  - **No QR code sign-in.** Discord's login screen offers to sign in by scanning a QR code with the Discord phone app. The phone app talks to Discord, not Blisscord, so scanning it cannot sign you in here; the script removes the QR code and the connection behind it, and the login screen shows just the email and password form.
  - **Blisscord loading screen.** While the app loads, Discord shows its spinning logo. The script shows the Blisscord logo there instead, so you can tell straight away that this Discord app is on Blisscord. If you see Discord's own spinning logo, the app is not on Blisscord (for example after a Discord update); run the installer again. The small window that checks for Discord updates before the app opens belongs to Discord's installer, which the script does not reach, so it still shows Discord's logo.
  - **Blisscord on the sign-in screen.** The login, sign-up and "Choose an account" screens look as they do in Discord, with a small Blisscord logo and the word Blisscord under the form, so you can tell at a glance that this app is on Blisscord. A patched app normally signs you straight in, so if it ever shows Discord's login screen without that mark, it is no longer on Blisscord (for example after a Discord update); run the installer again.
  - **Update notice.** When the injected script changes, the next time you open the app a small pop-up, "Blisscord was updated to the latest version.", shows for a few seconds, drawn as Discord draws its own. It is shown once per version: the server writes a short fingerprint of the script into it as it sends it, the app remembers on that device the last fingerprint it ran, and the very first one a device runs is only remembered, so a new install shows nothing. The fingerprint is all it keeps, and nothing is sent anywhere.
  - **Invite banner.** A one line banner at the top of the app invites you to bring friends to Blisscord, in Discord's own notice style, with an "Invite friends" button that opens Settings at Invites. Any notice Discord itself wants to show takes priority. Once you close it or use the button it does not come back on that device.
  - **Voice.** Discord's app refuses voice calls without its newer end-to-end encryption (DAVE), which Blisscord's voice server does not offer yet. The script lets the app join anyway. Voice is still encrypted in transit.
  - **Uploads in the desktop app.** Some uploads in the desktop app go through its own built-in network code, which the redirect above cannot see. The script sends those as a normal upload to Blisscord instead.
  - **Crash details.** When a screen fails to draw, the script adds which screen it was to the error report above.

If one of these edits does not fit a new Discord version, the script skips it and reports that it was skipped, rather than breaking the app.

## What it does not do

- The script sends nothing to anyone but Blisscord's own hosts. It does not read, copy or send your messages, your token or your password anywhere else.
- It does not record your keystrokes, take screenshots, or look at anything outside the Discord app.
- It does not add tracking or advertising.
- It does not change anything on Discord's servers or in your real Discord account. A converted install talks only to Blisscord, which is a separate service with separate accounts.

The app itself is still Discord's. The desktop app downloads its code and its updates from Discord as usual, and may still contact Discord for things the patch does not redirect, such as its updater; your Blisscord sign-in and messages are not among them. The web client at `app.discord.community` serves a copy of Discord's web app files from Blisscord, so using it in a browser does not need Discord.

## Checking for yourself

- Read the scripts at the links above. The injected script is `https://discord.community/dl/inject.js`, the same file the web client runs.
- The wrapper's fingerprint is the first 12 characters of the SHA-256 of its own `index.js`, and the script's is the same for `inject.js`, so you can compute both yourself. The out-of-date dialog shows the wrapper you are running and the current one.
- `status` reports whether an install is patched and whether the agent is on. `unpatch` removes both completely.

When the script changes, this page changes with it.
