A channel is a persistent chat thread inside the workspace. Every message you send and every reply the agent streams back live on a specific channel. The channel you choose determines what context the agent has, and what kinds of actions it is willing to take.
The Four Channel Types
| Channel | What the agent knows | What it is for |
|---|
| Task | The open task: title, status, template fields, linked documents, and extracted data. | Working a single task end-to-end. Asking the agent to help complete or review this task. |
| Project | The project as a whole: bound resources, recent activity, your role on the project. | Cross-task project work: authoring shared resources, binding resources, exploring activity plans. |
| Project Admin | Project configuration: companion settings, project bindings, permissions, audit. | Administrative operations on a project — usually restricted to project admins. |
| Workspace Global | The workspace shell: which project you have open, your recent navigation. | Lightweight, navigation-style help that is not tied to a specific resource. |
How To Switch Channels
The channel selector sits at the top of the chat pane. Click it to choose a different channel. Each task you open gets its own channel; the project and admin channels are persistent.
The history of each channel is preserved independently. Switching to a task channel and back to the project channel does not lose your project-level conversation.
Open the task you want to talk about before you start asking the agent about it. Opening the task sets the channel context — the agent gets the task’s title, status, and linked documents automatically.
What The Agent Knows In Each Channel
The same agent, with the same skills, behaves differently depending on the channel because the context differs.
- In a task channel, the agent receives the task as part of every turn. “Help me complete this” is unambiguous — this is the task in scope.
- In the project channel, the agent has the whole project’s resource roster. “Add a taxon to the Invoice taxonomy” resolves to a project-level taxonomy, not a task-scoped one.
- In the project admin channel, the agent can discuss and (with the right skill) change project-level configuration.
- In the workspace global channel, the agent has the least context. It is good for “take me to the project with vendor X” style requests; it is not the right place to ask for resource edits.
When To Switch Mid-Conversation
There are two common patterns where switching channels is the right move:
- Drilling into a task. You start in the project channel exploring activity plan steps, decide one specific task needs attention, open the task, and continue the conversation in the task channel where the agent has full task context.
- Promoting a project-wide change. You started in a task channel and realize the change you want is not task-specific — it belongs at the project level. Switch to the project channel so the change is scoped correctly.
Channels Are Auditable
Every message, every agent reply, and every action the agent takes is recorded on the channel. You can scroll back to see exactly what was said and what changed. This is the source of truth for “what did the agent do?” — see Troubleshooting for how to use the channel history when something goes wrong. 