Configuration
Most functions of Chute are controlled by the configuration file. Chute iOS and Chute Mac can share configuration files via iCloud Drive. You may edit the configuration file with your text editor, Chute iOS app, or Chute Dashboard.
Configuration Sections
The configuration file is organized into named sections:
| Section | Purpose |
|---|---|
[General] |
Global settings (logging, IPv6, DNS, proxy ports, etc.) |
[Proxy] |
Outbound proxy policy definitions |
[Proxy Group] |
Policy group definitions (select, url-test, fallback, load-balance, ssid) |
[Rule] |
Traffic matching and routing rules |
[Host] |
Local DNS host-to-IP mappings |
[DNS] |
DNS settings, accepting both [General] DNS keys and [Host]-style per-domain overrides |
[URL Rewrite] |
URL rewrite rules |
[Header Rewrite] |
HTTP header rewrite rules |
[Body Rewrite] |
HTTP body search-and-replace rules |
[Map Local] |
Mock response rules |
[MITM] |
HTTPS decryption settings |
[Script] |
JavaScript script definitions |
[SSID Setting] |
Wi-Fi SSID suspend rules |
[Replica] |
Traffic recording filters |
[Module] |
External module files |
[WireGuard <name>] |
WireGuard tunnel configurations (an instance name is required, e.g. [WireGuard HomeServer]) |
[AmneziaWG <name>] |
AmneziaWG tunnel configurations, WireGuard-compatible with obfuscation parameters (an instance name is required, e.g. [AmneziaWG HomeServer]) |
[Tailscale] |
Global Tailscale configuration (globally unique) |
[Proxy Provider] |
External proxy list sources |
[Rule Provider] |
External rule set sources |
Notice: The sections
[Panel],[Ponte]and[MTProto]are recognized so that a Surge configuration does not error, and their lines are preserved verbatim when the configuration is saved, but they have no effect in Chute.
DNS Section
The DNS-related [General] keys may equivalently be written under a top-level [DNS] section. Lines in that section are handled per key:
| Line | Handling |
|---|---|
dns-server, doh (alias doh-server), dot, doq, doh3, hijack-dns, always-real-ip |
Exactly as in [General]; the key is stored as if it had been written there |
| Any other line | Parsed with the [Host] per-domain syntax, e.g. *.example.com = server:1.1.1.1 |
| A key that is neither | Ignored with a notice in the log; the line itself is kept |
[DNS]
doh = https://dns.google/dns-query
hijack-dns = 8.8.8.8:53
*.example.com = server:1.1.1.1
Note: Because both line forms are accepted here, a
[DNS]section may mix DNS server settings with per-domain overrides. Do not repeat the same setting in[General]and[DNS]: a seconddohline, for example, is reported as a duplicate DoH configuration.
Comment
Chute configuration file supports comment line, starts with '#', ';' and '//'. Inline comments are also supported: use '//', or '#' / ';' preceded by whitespace. Comments and blank lines are preserved when the configuration is saved.