gentle-engram v0.1.6 updates startup behavior so Pi-launched/configured Engram processes with token+server settings automatically enable Engram core cloud autosync, reducing manual sync configuration for deployments.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Added automatic cloud autosync activation during startup for Pi-launched/configured Engram processes when token and server are present, while preserving explicit ENGRAM_CLOUD_AUTOSYNC overrides and policy enforcement in Engram core/server.
Pi operators and teams running configured Engram processes will get cloud autosync enabled by default when credentials are present, so synchronized cloud state is more likely to be active immediately after launch instead of requiring manual toggling, which helps prevent drift or missed updates; watch whether intentionally disabled autosync environments and legacy MCP launcher paths still behave as expected. The implementation keeps ENGRAM_CLOUD_AUTOSYNC as a hard override and keeps project enrollment/pause enforcement in policy, and it migrates only known legacy generated Pi MCP launchers to avoid altering custom MCP configurations, so migration safety should be the next operational check.
Pi operators and teams running configured Engram processes will get cloud autosync enabled by default when credentials are present, so synchronized cloud state is more likely to be active immediately after launch instead of requiring manual toggling, which helps prevent drift or missed updates; watch whether intentionally disabled autosync environments and legacy MCP launcher paths still behave as expected. The implementation keeps ENGRAM_CLOUD_AUTOSYNC as a hard override and keeps project enrollment/pause enforcement in policy, and it migrates only known legacy generated Pi MCP launchers to avoid altering custom MCP configurations, so migration safety should be the next operational check.