Channels

Channels organize the work inside a Space.

Use them for projects, topics, customers, recurring workflows, or Slack conversations. Every channel shares the Space’s computer, connections, memory, access, and AI defaults. Files, apps, documents, and skills can be kept at the Space level or filed into a specific channel.

That means you can create a new channel without reconnecting an integration or starting the context from scratch. Add the Library items that belong to the channel when you want its conversations to use a focused set of material.

Every Space also has Threads, the default place for conversations that are not assigned to a named channel.

Create a channel

1. Expand the Space in the sidebar.
2. Select Create channel.
3. Give the channel a short, recognizable name.
4. Start a thread there, or route a source or automation to it.

A simple department setup

A Marketing Space might use:

Channel	What goes there
brand	Design, positioning, voice, and creative review
campaigns	Launch plans, ads, briefs, and results
reporting	Recurring analysis from commerce and marketing data
content	Drafts, editorial work, and publishing

All four channels can use the same Shopify connection, Claude or Codex runtime, and Space memory. Skills and other Library items can be filed into each channel to keep its working context focused.

Organize Library items

Open the Space’s Library to add a document, upload, app, video, or attached skill to a channel. Choose Add to new channel to create the channel and file the item in one step.

An item with no channel is at the Space level, so conversations in Threads and named channels can discover it. A conversation in a named channel can also discover items filed in that channel.

Threads or a named channel?

Use Threads for quick questions and one-off work that does not need a permanent category.

Create a channel when:

• The same kind of work happens repeatedly.
• A project or topic needs a clear home.
• An automation, inbox, webhook, feed, or connected source needs a stable destination.
• A Slack channel should map into the Space.
• People need to scan related conversations together.

Move a channel to another Space

You can move a named channel without merging the whole Space. You must be a member of both the original and destination Spaces, and both must be in the same workspace. The default Threads area cannot be moved this way; use Merge Spaces to combine entire Spaces.

1. Expand the original Space in the sidebar.
2. Open the channel’s More options menu and choose Move to Space.
3. Select the Destination Space.
4. Review who can access the destination Space and which connections and instructions it provides, then choose Move.

If the destination already has an active channel with the same name, rename one of the channels before trying again. If a destination is missing, check that you have joined it.

What follows the channel

The channel’s threads and replies move with it. Links to Library items, scheduled automation destinations, and RSS feeds also move, with these exceptions:

• If the destination already has a placement for the same Library item or automation, it keeps that existing placement.
• A feed already followed by the destination keeps its existing setup.
• Channel skills move unless the destination already has the same skill or skill name; in that case, the conflicting skill stays at the original Space level.

Individual Library items keep their own sharing rules.

The destination Space’s access rules and Space context now apply. Review access before moving sensitive work, and check that the connections needed for future work are available in the destination.

Connected sources stay behind

Integration-backed connected sources and webhooks stay in the original Space. Their channel destination resets to that Space’s Threads area, so new incoming items will not follow the moved channel. Space-level connections also stay in the original Space.

After moving, review the original Space’s sources and webhook destinations. If incoming work should land in the destination Space, set up the source there and choose the moved channel. Check for duplicate delivery before leaving both sources active. RSS feeds are an exception: feeds assigned to the channel move with it.

Connect Slack channels

A Type channel and Slack channel are separate places, but you can map them together. New Slack messages can flow into the Type channel, and AI responses can flow back to Slack.

This is a practical way to bring a team into Type. People can keep working from Slack while the full conversation, Space context, connections, skills, and memory stay available in Type.

See Slack for setup and response controls.

Route incoming work

Automations and connected sources can post into a named channel or into Threads. For example:

• Support email can land in customer-issues.
• GitHub activity can land in engineering-updates.
• A weekly automation can publish into reports.

Before removing a channel, move or reroute the automations and sources that still depend on it.