Skip to content
Changelog

Report a bug

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.

  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 Marketing Space might use:

ChannelWhat goes there
brandDesign, positioning, voice, and creative review
campaignsLaunch plans, ads, briefs, and results
reportingRecurring analysis from commerce and marketing data
contentDrafts, 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.

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. A thread started from Threads can discover all relevant Space items. A conversation in a named channel discovers the items filed in that 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.

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.

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.