A new proactivity key was added to the cloud session flag-mapping table, treated as a supported passthrough option alongside systemPrompt and thinking rather than being unsupported.
Names in the bundleproactivity
Documented inclaude-code/claude-tag
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up proactivity, on Restrict where Claude Tag operates.
Of the [commands](/docs/claude-tag/users/commands), your organization's members can run only `!help`, `!mute`, `!unmute`, and `!restart` in a Slack Connect channel. `!fork` and [routines](/docs/claude-tag/users/proactivity) aren't availabl…claude-tag/admins/restrict-access see the edit
Added since
A small documentation edit on Customize Claude Tag touched a line naming proactivity after this was published.
The Configure page also shows the channel's resolved access. Its **Tools and access** tab lists the channel's resolved connections and any allowed domains. Members can see those lists but not change them there. The same tab's **Plugins** c…claude-tag/admins/customize see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Customize Claude Tag touched a line naming proactivity after this was published.