Work from your own channel changedclaude-tag/users/use-cases/your-own-channel
Nearest release: v2.1.243, published under an hour after 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+8added
Lines−0removed
From line
66
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits7to this page, all time
The whole hunk
from line 66, old and new numbered
/
from line 66
6666
6767The summary gives Marta the state of the work in one message, with the full history above it. From there the thread is hers to continue, without re-mentioning @Claude or starting over.
6868
69If the work belongs in a team channel rather than yours, fork the thread there instead of inviting Marta in. Claude starts a new thread in the channel you name with your thread as background, and leaves a link in your channel so you can follow along.
70
71```text wrap theme={null}
72@Claude !fork #export-team summarize the export-flow bug for the team: what's been tried, what's decided, and what's still open.
73```
74
75The target must be a public channel that both you and Claude are in, and your own channel must be public for the fork to run. See [Fork a thread](/docs/claude-tag/users/commands#fork-a-thread).
76
6977### Chase your open follow-ups
7078
7179Claude can track the work you've committed to but might have forgotten about. When you agree to do something in another channel, forward that message to this channel, or post a short note here describing the commitment. When the work is somewhere Claude can check through this channel's connections, like a pull request review you owe, include the link.
No line in this hunk matches that.