Unclear It is not clear how many of these settings the Claude Code command line reads, as opposed to the desktop app.
What
Administrators can set managed settings for everyone in their organization. The list of settings for Cowork and third-party deployments now includes:
sharingEndpoint: where "Publish to organization" sends shared itemsscheduledTasksEnabled: when off, sessions start without the/loopcommand, its scheduling tools and its wake-up timerkeepAwakeEnabled: whether keep-awake is allowedallowedPluginMcpServers: which MCP servers (connections to outside tools and data) plugins may usemcpScheduledTaskApprovalLifetimeDays: how many days an approval for an MCP server in a scheduled task lasts
The description of userPluginMarketplacesEnabled has been rewritten. The Salesforce plugin marketplace entry is no longer limited to internal use and now points at its claude-prod version.
Why
Admins get more control over scheduled tasks, MCP approvals and which servers plugins can reach.
/loop
Claude Code changelog modified, high confidence
* Fixed a background session's `/loop` silently stopping when the session's process restarted (for example after a crash), because its pending wakeup was lostsee the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear how many of these settings the Claude Code command line reads, as opposed to the desktop app.
Anthropic's documentation agrees
/loop on Claude Code changelog
Anthropic's release notes agree
Reverted the 2.1.290 fix for cloud sessions staying asleep after a container restart lost a pending /loop wakeup or scheduled task; Claude…