Managed Configuration

Chute can update a config file from an URL automatically. If the config starts with

#!MANAGED-CONFIG http://test.com/chute.conf interval=60 strict=true

The running tunnel checks and applies updates automatically at the configured interval, the first time one interval after it starts. Chute iOS, Chute tvOS and Chute Android refresh managed configurations from the app as well — on iOS and tvOS when the app is opened, on Android at launch and every six hours; an Android refresh rewrites the file and takes effect the next time the VPN starts. Chute Mac has no app-side refresh: there, only the engine's timer updates them, and only while it is running. Such an update replaces the configuration in the running engine and never rewrites the file, so after a restart Chute Mac runs the file as it is on disk again until the next check, one interval later.

Note: The new config in remote should also contain #!MANAGED-CONFIG line. Otherwise the running engine loads it as a regular configuration and stops checking for updates. This concerns the engine's own updates only: the app-side refresh keeps a managed header whatever the server sends — Chute iOS and Chute tvOS write a new one with the address the download came from and the interval, leaving strict out, and Chute Android keeps the file's own header line. If the address starts serving a Clash or sing-box profile instead, neither the engine nor the app-side refresh adopts it: the running engine keeps the configuration it has, logs that the subscription now serves a profile that needs converting and tries again at the next check, and the app-side refresh of Chute iOS, Chute tvOS and Chute Android leaves the file as it is. Import the address again to have the profile converted.

Parameters

interval: Optional, s (Default: 86400s).

The update interval in seconds. The 86400s default applies to the running tunnel's periodic update; the app-side refresh skips configurations that do not explicitly set interval=.

strict: true or false (Default: false).

Reserved. Currently strict only affects update logging: when an update fails, the previous configuration remains in use in both modes.