Documentation & Wiki

No. Hyaecord is an original client with its own shell, GUI, and internals. Its plugin system is a separate, sandboxed API ergonomically modeled on Vencord's definePlugin shape — familiar to write for, but not a byte-compatible runner for existing Equicord/Vencord plugin files, which patch Discord's real webpack bundle that this client's original GUI doesn't have. A plugin that only needs message-level hooks ports easily; one that reaches into Discord's real component tree can't run here at all. See the Plugin Guidelines for the current scope.

Client modifications are against Discord's Terms of Service, so there is inherent risk. In practice Discord has historically not banned users solely for using client mods, but if losing your account would be a serious problem, you should avoid client mods entirely — Hyaecord included.

Linux is the primary v1 target; Windows is planned as a secondary target. macOS is not planned.

Yes — a real, independent Stoat.chat integration (its own REST/gateway client, not a Discord lookalike): servers, DMs, friends, live messaging, edit/delete, reactions, replies, mentions, typing indicators, search, and joining/creating/leaving servers via invite all work today. Connect it from Settings → Accounts alongside (or instead of) Discord, and optionally merge both into one server rail. Fluxer support is planned but not started. See the features section and the project's own build log for the exact, itemized history.

Hyaecord sends one small anonymous ping a day — a random ID, app version, OS, and desktop environment — so the project knows roughly how many people use it. It is never linked to your Discord account and contains no messages or personal data, and you can switch it off any time in Settings (off means off). Anything else that transmits data is opt-in and explained in plain language first. This website sets no cookies and runs no analytics — see the privacy policy.

Yes, always — the code is under the Hyaecord Public License (GPL-3.0-derived): free to fork and modify, provided the fork stays open-source and non-commercial. You must also rebrand your fork (different name, logo, and app ID) before distributing it publicly, per the trademark policy. Rebranded, compliant forks need no permission at all.

Use GitHub private security advisories — see security.txt.