...

AI Booster Configuration Guide

Where each setting lives, what actually differs between mobile and desktop builds, the import formats accepted, and why an export is not a safe thing to share.


Configuration Guide

Configuration falls into three layers, and it is worth knowing which one you are in before you start changing things.

📋 Subscriptions

Where your nodes come from, and how they refresh

View

🔧 Proxy settings

Service mode, ports, TUN — the settings that decide what gets routed

View

⚙️ Advanced

DNS, multiplexing, TLS shaping, kill switch, WARP

View

Most people never need the third. The defaults are conservative on purpose.

What differs between platforms

The same settings are not present everywhere, and this is the single most common source of "the documentation says there's an option and I can't find it".

SettingMobile (iOS / Android)Desktop (Windows / macOS / Linux)
Launch at startupYes
Start hiddenYes
Connect on launchYes
Quick Settings tileAndroid only
System proxy integrationYes

Startup behaviour is a desktop concept: mobile operating systems decide for themselves when an app runs. If a page here describes an option your build does not show, the build is right.

Appearance and language

Theme has four modes, not three:

Mode
SystemFollows the operating system
Light
Dark
BlackTrue black rather than dark grey — noticeably better on OLED screens, and a separate choice from Dark

Language can follow the system or be set explicitly. Setting it explicitly is worth doing if your device language and your preferred reading language differ.

Importing a configuration

Four routes in, all reaching the same place.

RouteAccepts
Paste a linkA node link or a subscription URL
Import a fileA configuration file from disk
Read the clipboardDetects a supported link already copied
Scan a QR codeCamera-equipped builds

Individual node links use the scheme to say which protocol they are:

vless:// · vmess:// · trojan:// · ss:// · hysteria2:// (also hy2://, hy://) · tuic:// · wg:// · ssh:// · warp://

A WireGuard configuration pasted as text is recognised by its [Interface] header.

An http:// or https:// URL is treated as a subscription rather than a node: it is fetched, and can be refreshed later to pick up changes. This is the difference that matters — a pasted node is frozen at the moment you pasted it, a subscription is not. See subscriptions.

A subscription URL is a credential. Anyone holding it can use your service, so treat it like a password — and prefer regenerating it over sharing it.

Exporting and importing settings

Where the build offers it, settings can be exported to a file or the clipboard and imported back later. The exact menu wording differs by platform and version.

An export is plain text, not an encrypted backup. A full export can contain credentials held by the client — WARP device keys and tokens, and the addresses of services your profile uses. Treat an export file the way you would treat a password: do not post it in a support thread, chat, or issue report.

This is worth being blunt about because the natural time to share an export is exactly when you are asking a stranger for help.

Exporting

Builds that support export may offer an anonymised variant, which removes account-linked secrets such as WARP device credentials and the per-application list before writing the file. Use the anonymised form whenever you need to share settings with someone else for troubleshooting.

If your build does not offer an anonymised export, review the file and remove credentials yourself before sharing it.

Importing

An import merges the file's values onto your current settings and then normalises them, so values written by an older version are migrated where the client knows how. Because it overwrites the settings it contains, export a known-good copy first so you can roll back.

Importing does not verify that the endpoints, resolvers, or rules named in the file are trustworthy. Only import files from a source you trust — a configuration file can point your traffic anywhere.