Set Up Slack Channel changedapi/beta/organization/claude_tag/slack_channels/create
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
127
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 127, old and new numbered
/
from line 127
127127
128128 - `"webhooks-2026-10-07"`
129129
130 - `"admin-user-sign-out-2026-10-08"`
131
130132 - `"message-threads-2026-08-12"`
131133
132134 - `"analytics-usage-cost-2026-08-24"`
from line 199
197199
198200 minLength: 1, maxLength: 128
199201
202 - `reply_mode: optional BetaClaudeTagReplyMode or null`
203
204 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`.
205
206 - `BetaClaudeTagReplyModeAutomatic object`
207
208 Claude reads along and joins in when it can help, and pauses on its own in quiet or busy channels.
209
210 - `type: "automatic"`
211
212 - `BetaClaudeTagReplyModeMentionOnly object`
213
214 Claude replies only when it is @-mentioned.
215
216 - `type: "mention_only"`
217
218 - `BetaClaudeTagReplyModeAlwaysAwake object`
219
220 Like `automatic`, but Claude never pauses on its own. Available where it is enabled for the channel.
221
222 - `type: "always_awake"`
223
224 - `BetaClaudeTagReplyModeThread object`
225
226 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.
227
228 - `type: "thread"`
229
200230## Returns
201231
202232- `BetaClaudeTagSlackChannel object`
from line 287
257287
258288 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.
259289
290 - `reply_mode: BetaClaudeTagReplyMode or null`
291
292 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.
293
294 - `BetaClaudeTagReplyModeAutomatic object`
295
296 Claude reads along and joins in when it can help, and pauses on its own in quiet or busy channels.
297
298 - `type: "automatic"`
299
300 - `BetaClaudeTagReplyModeMentionOnly object`
301
302 Claude replies only when it is @-mentioned.
303
304 - `type: "mention_only"`
305
306 - `BetaClaudeTagReplyModeAlwaysAwake object`
307
308 Like `automatic`, but Claude never pauses on its own. Available where it is enabled for the channel.
309
310 - `type: "always_awake"`
311
312 - `BetaClaudeTagReplyModeThread object`
313
314 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.
315
316 - `type: "thread"`
317
260318 - `slack: BetaClaudeTagSlackChannelIdentifiers`
261319
262320 Slack's own identifiers for the channel.
from line 431
373431
374432 The settings level `model` comes from.
375433
434 - `reply_mode: BetaClaudeTagSettingSource or null`
435
436 The settings level `reply_mode` comes from: the channel when it stores one. With `include_inherited=true` and no stored mode it is `default`.
437
376438 - `updated_at: string`
377439
378440 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 470
408470 "type": "allow"
409471 },
410472 "instructions": "instructions",
411 "model": "model"
473 "model": "model",
474 "reply_mode": {
475 "type": "automatic"
476 }
412477 },
413478 "slack": {
414479 "channel_id": "xx",
from line 499
434499 }
435500 ],
436501 "model": {
502 "slack_channel_id": "slack_channel_id",
503 "type": "slack_channel"
504 },
505 "reply_mode": {
437506 "slack_channel_id": "slack_channel_id",
438507 "type": "slack_channel"
439508 }
No line in this hunk matches that.