Skip to main content

isolated_settings_enabled

agentmux_common::data_paths

Function isolated_settings_enabled 

Source 
pub fn isolated_settings_enabled() -> bool
Expand description

Isolated per-channel settings.json. Same shape and same reasoning as isolated_auth_enabled — see docs/specs/SPEC_SETTINGS_ISOLATED_BY_CHANNEL_2026_08_19.md.

Resolution order:

  1. AGENTMUX_ISOLATED_SETTINGS=1 / =0 — explicit override, always wins.
  2. Otherwise, defaults to isolated for every channel except "stable". stable is the real release channel — the daily-driver install(s) this machine’s actual work depends on — and keeps the old always-global behavior, so nobody’s real window theme/pinned widgets/voice API key gets silently blanked by a channel-name coincidence. Every task dev branch and every task package local build now starts with a genuinely default settings.json — the motivating case was network:lan_discovery silently carrying true into a brand-new build from a decision made in an unrelated channel weeks earlier.
  3. If AGENTMUX_CHANNEL isn’t set yet, stays global — conservative default when channel context is unknown, not a guess.

Deliberately a SEPARATE flag from AGENTMUX_ISOLATED_AUTH, not a shared AGENTMUX_ISOLATED umbrella — see the spec’s Open Questions §1 for why.