{"version":"2.1.300","anchor":"organization-settings-unanswered-hold-command-plugins-mark","canonical_anchor":"organization-settings-unanswered-hold-command-plugins-mark","heading":"Plugins, hooks modules and \/goal wait until your organization's settings are read","tier":"notice","area":"Plugins","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/organization-settings-unanswered-hold-command-plugins-mark","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Plugins, hooks modules and \/goal wait until your organization's settings are read\n\nCommand plugins, marketplaces, hooks modules and \/goal are held until organization settings are read; an unreadable policy now ends with a clear message\n\n**Unclear.** Which kinds of sessions wait for organization settings in this way is not clear.\n\n**What**\n\nIf you belong to an organization, its settings can decide whether hooks (your own commands that run at set points) and plugins (add-ons) are allowed. Claude Code now tracks whether those organization settings have been read yet, and holds back features that depend on them until it knows:\n\n- Command plugins and marketplaces: plugins that come from commands, and plugin marketplaces (places plugins are installed from), are held while the organization's settings are unanswered. The marketplace check reports `organization_unanswered`. Before, only `disableCommandPluginSources` and `allowManagedHooksOnly` in the policy were checked.\n\n- `\/goal`: it can't run yet, with the message that your organization's settings haven't been read so it isn't known whether hooks are allowed.\n\n- Hooks modules: the check that decides whether hooks and hooks modules (mods) may load now takes an `organization` value, alongside `builtinsOnly` and `personsHeld`. The default is `unasked`.\n\n- Reload: once the answer arrives, plugins are reloaded. A full plugin refresh (`refreshActivePlugins`) now first waits on this hold (`organizationAsk.heldReresolve`) when an answer is pending.\n\n- Unreadable policy: if the policy cannot be read, the session now stops with 'Your organization's policy could not be read, so this session cannot run a turn.' instead of a generic message, and you are told installed mods are not running. The wait now ends as a limit, a dead end or a release.\n\n**Why**\n\nIn managed or hosted sessions, plugin commands, mods and `\/goal` stay off until the organization's policy is known, instead of running before it loads. This can change what is available right after startup, and an unreachable policy now gives a specific reason.\n\n- Area: Plugins\n- Names: `\/goal`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}