Compatibility and beta limitations

These docs describe FluxPlugs 0.5.0-beta.1, the current beta implementation.

Supported targets

FluxPlugs supports structurally compatible Windows and Linux Fluxer Electron installations. The injector checks the installed application, its executable, and the way it starts. Compatibility is not guaranteed merely because a Fluxer version number matches.

Use Scan for installs and inspect the selected installation’s diagnostics. If your installation is unsupported, the scan says why. Do not bypass the check or replace application files manually.

Scan for installs looks in these places:

• Windows: the stable and Canary installs under %LOCALAPPDATA% (fluxer_desktop, fluxer_desktop_canary, and the older fluxer_app).
• Linux packages (deb, rpm, Arch): /opt/Fluxer, /opt/fluxer and /opt/fluxer-canary. These folders usually belong to root, so the scan reports them as read-only unless your account can write to them.
• Flatpak and AppImage: Fluxer’s files are read-only in these formats, so they are listed but can’t be injected. Use a deb, rpm, Arch or tar.gz install instead.

For an install somewhere else, add its folder to the custom install roots.

The project’s generated fake-Fluxer application is a testing fixture laid out like a Fluxer release, not a real chat client.

Beta limitations

• Beta downloads are unsigned and x64 only. You can also build from source.
• Check for updates displays a work-in-progress notice; it does not download or check releases.
• macOS, mobile, and browser Fluxer targets are unsupported.
• Plugins cannot use unrestricted networking, the local bridge, or display capture. A plugin with the network permission reaches only the HTTPS servers listed in its manifest.
• Supported image loading, file-context lookup, and external browser links are narrow, separately controlled features.
• Plugins built for an incompatible SDK cannot run until updated.

After a Fluxer update

Fluxer’s updater replaces its application files, which removes FluxPlugs. Your plugins and their settings are kept. Open the injector, scan again, and use Check status: the status reads Re-inject needed when a clean, newer Fluxer build replaced the injected one. Review and inject again to restore FluxPlugs. See the update guide for details.

Treat beta behavior as subject to change. Report reproducible compatibility problems with diagnostics and versions through GitHub issues.