{"version":"2.1.304","anchor":"new-org-config-gate-event-managed-agents-secure-skill-and-t","canonical_anchor":"new-org-config-gate-event-managed-agents-secure-skill-and-t","heading":"Groundwork for an organisation setup step and a managed-agents entry","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/new-org-config-gate-event-managed-agents-secure-skill-and-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Groundwork for an organisation setup step and a managed-agents entry\n\nClaude Code adds an organisation setup name, a managed-agents-secure entry and a new switch that is off unless turned on remotely\n\n**Unclear.** What any of the three controls is not stated.\n\n**What**\n\nThree small additions:\n\n- a new name, `org_config_gate`, used in setup and analytics\n\n- a `managed-agents-secure` entry in a built-in list\n\n- a new switch, `tengu_jiggly_blossom`, placed next to the naming for container tools; it is off unless switched on remotely\n\n**Why**\n\nThese look like pieces of features still being built.\n\n- Flag `tengu_jiggly_blossom`: Not enough to say (read for one account on one subscription tier against v2.1.304; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}