Configuration

A Prizrak-Core config is a YAML file (config.yaml in the working directory). Its format is the mihomo format: Prizrak-Core reads every mihomo config unchanged.

👻 marks what exists only in Prizrak-Core. A 👻 next to a page, a section or an option means that mihomo does not have it: a config that uses it needs Prizrak-Core (or Prizrak-Box), and plain mihomo ignores the key or refuses the config.

Main differences from mihomo

Feature	mihomo	Prizrak-Core
smart group: ML-based node selection	—	✅
ping-config: url-test / fallback / load-balance / smart count a node alive only when it really downloads data	—	✅
uTLS: prizrak-utls: Chrome 155 / Firefox 148 / Safari 26.3 fingerprints	metacubex/utls v1.8.8	✅
mux.cool: Xray Mux and XUDP	—	✅ client and server
REALITY with ML-DSA-65, in sync with current Xray	—	✅
finalmask: Xray-core traffic masks (fragment, header-custom, sudoku, xmc, noise, udphop, xdns, xicmp) for vless and trojan	—	✅ client and server
mKCP for VLESS, as in Xray-core since finalmask (xdns DNS tunnels included)	VMess only	✅ client
XHTTP and HTTP/2: the h2-flow governor, one HTTP/2 connection at a time, 32 KiB send buffer	—	✅ client and server
freedom: DIRECT with TLS fragmentation and socket options (Xray-core freedom)	—	✅
udp-443: send QUIC (UDP/443) through a node or a whole provider into REJECT	—	✅
fallback-urls: backup addresses for http proxy and rule providers	—	✅

To deliver these options to clients of a Remnawave panel, see Remnawave integration.

Sections

Complete example docs/config.yaml in the Prizrak-Core repository: every option with a comment.

General Ports, mode, logging, controller, profile, geodata.

DNS Nameservers, fake-ip, policies, hosts.

Inbound Ports, TUN and listeners.

Proxies Outbound protocols, TLS and transports.

Proxy groups select, url-test, fallback, load-balance and 👻 smart.

Routing rules Rule types and logic.

Providers Proxy and rule providers.