Module policy 

Which installs publish their presence. A normal signed-in desktop does, unless the user turns off “Publish this computer to my devices” (cloud:publishpresence, setting_on). A task dev build, a headless srv, an isolated home and a test harness don’t by default: each would leave an entry in the account’s list of computers that is not a computer anyone uses. FORCE_ENV turns publishing on for one of those, for testing presence itself; the setting still wins over it.

Structs

Install 🔒

The facts about this install that decide whether it publishes by default, read once at start.

Constants

FORCE_ENV 🔒

1 publishes from an install that is off by default (a dev build under test). Not a setting: nobody should come across it by accident.

TEST_HARNESS_ENV 🔒

Set by a test harness that starts srv. AGENTMUX_DISABLE_CLOUD_SUBSCRIBER (the srv integration tests) counts too.

Functions

setting_on 🔒

“Publish this computer to my devices” as settings.json has it. Absent means on. The key is written out at the read so the settings-defaults check (settings-defaults.test.ts) finds this default.