Update Slack Channel changedapi/beta/organization/claude_tag/slack_channels/update
Nearest release: v2.1.322, published 2 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+70added
Lines−1removed
From line
133
where the diff opens
First seen
30 Oct 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 133, old and new numbered
/
from line 133
133133
134134 - `"webhooks-2026-10-07"`
135135
136 - `"admin-user-sign-out-2026-10-08"`
137
136138 - `"message-threads-2026-08-12"`
137139
138140 - `"analytics-usage-cost-2026-08-24"`
from line 189
187189
188190 minLength: 1, maxLength: 128
189191
192 - `reply_mode: optional BetaClaudeTagReplyMode or null`
193
194 How Claude takes part in the channel: `automatic`, `mention_only`, `always_awake` or `thread`. Only a channel takes one: an update of a workspace that sends a value is refused, and one that sends null changes nothing. Null never clears it: sent to a channel that stores none it changes nothing, and sent to a channel that stores one it is refused, because a stored reply mode can be changed but never cleared; a caller that wants Claude's default behavior sends `automatic`.
195
196 - `BetaClaudeTagReplyModeAutomatic object`
197
198 Claude reads along and joins in when it can help, and pauses on its own in quiet or busy channels.
199
200 - `type: "automatic"`
201
202 - `BetaClaudeTagReplyModeMentionOnly object`
203
204 Claude replies only when it is @-mentioned.
205
206 - `type: "mention_only"`
207
208 - `BetaClaudeTagReplyModeAlwaysAwake object`
209
210 Like `automatic`, but Claude never pauses on its own. Available where it is enabled for the channel.
211
212 - `type: "always_awake"`
213
214 - `BetaClaudeTagReplyModeThread object`
215
216 Every new top-level message in the channel gets its own reply from Claude, in a thread under it. Available where it is enabled for the channel, and only once Claude has been used in the channel.
217
218 - `type: "thread"`
219
190220## Returns
191221
192222- `BetaClaudeTagSlackChannel object`
from line 277
247277
248278 The model Claude uses: a model identifier or the name of a model line. The nearest settings level that sets it decides. When none does, Claude uses the product's default model.
249279
280 - `reply_mode: BetaClaudeTagReplyMode or null`
281
282 How Claude takes part in the channel. Only a channel stores one, and no settings level passes one on, so it is always null on a workspace. Null on a channel means the channel stores none yet: Claude then follows the reply mode chosen in Slack, if one was, else `automatic`. A stored reply mode can be changed but never cleared.
283
284 - `BetaClaudeTagReplyModeAutomatic object`
285
286 Claude reads along and joins in when it can help, and pauses on its own in quiet or busy channels.
287
288 - `type: "automatic"`
289
290 - `BetaClaudeTagReplyModeMentionOnly object`
291
292 Claude replies only when it is @-mentioned.
293
294 - `type: "mention_only"`
295
296 - `BetaClaudeTagReplyModeAlwaysAwake object`
297
298 Like `automatic`, but Claude never pauses on its own. Available where it is enabled for the channel.
299
300 - `type: "always_awake"`
301
302 - `BetaClaudeTagReplyModeThread object`
303
304 Every new top-level message in the channel gets its own reply from Claude, in a thread under it. Available where it is enabled for the channel, and only once Claude has been used in the channel.
305
306 - `type: "thread"`
307
250308 - `slack: BetaClaudeTagSlackChannelIdentifiers`
251309
252310 Slack's own identifiers for the channel.
from line 421
363421
364422 The settings level `model` comes from.
365423
424 - `reply_mode: BetaClaudeTagSettingSource or null`
425
426 The settings level `reply_mode` comes from: the channel when it stores one. With `include_inherited=true` and no stored mode it is `default`.
427
366428 - `updated_at: string`
367429
368430 Time Claude Tag's record of the channel last changed. It moves on every change to a setting, and can also move when something no response holds changes, so a later value says to read the channel again, not that a setting changed. Attaching or detaching a Bundle does not by itself move it.
from line 457
395457 "type": "allow"
396458 },
397459 "instructions": "instructions",
398 "model": "model"
460 "model": "model",
461 "reply_mode": {
462 "type": "automatic"
463 }
399464 },
400465 "slack": {
401466 "channel_id": "xx",
from line 486
421486 }
422487 ],
423488 "model": {
489 "slack_channel_id": "slack_channel_id",
490 "type": "slack_channel"
491 },
492 "reply_mode": {
424493 "slack_channel_id": "slack_channel_id",
425494 "type": "slack_channel"
426495 }
No line in this hunk matches that.