One Thread, Many Agents: How Channels Work

A channel is a persistent group chat in Insulin where several people and several agents work in one shared thread, and everyone sees the same messages. The interesting part is not the chat. It is that one agent coordinates the others, and the rules about who may act are different from a one-to-one conversation.

---

Most AI tools are built around one person talking to one assistant. That works until the work does not belong to one person — a launch, an incident, a month-end close — and you end up with four people each asking their own agent a slightly different version of the same question, then reconciling the answers by hand.

A channel is the other shape: one thread, several people, several agents, one shared history. This post covers what a channel is made of, who is allowed to do what inside it, how the agents divide work between them, and the three things a channel deliberately does not do.

What a channel is

A channel is a persistent group chat where multiple people and multiple agents collaborate in one thread. Insulin’s documentation puts the distinction from a one-to-one conversation simply: “everyone in the channel sees the same messages.”

That shared history is the point. In a solo conversation the context lives with one person, and anyone who joins later gets a summary at best. In a channel the reasoning, the retrieved sources and the agent’s output are all in the same place as the human discussion about them.

Personal or Organization: the choice you make first

A channel is owned either by you or by the organization, and the choice decides which agents can join.

• Personal channels are private to you, and “only your own user-level agents can be added.”
• Organization channels belong to the organization and can be shared; “only org-level agents can be added as members.” Creating one requires organization administrator access.

One practical warning from the documentation, because it is the kind of thing you find out the annoying way: “Changing the ownership type clears any agents and people you already picked.” Decide the ownership before you assemble the membership, not after.

Who is in the room, and what they can do

A channel holds up to 20 agent members and up to 20 user members. User members are an organization-channel feature — a personal channel has no other people in it by definition.

People in an organization channel carry one of five roles:

Role	What it grants
Owner	Full control — manage members, edit channel settings, delete the channel, and transfer ownership
Admin	Manage members and edit channel settings
Editor	Send messages and interact with agents
User	Send messages and interact with agents
Viewer	Read messages only — cannot send messages or trigger agent actions

Viewer is the role worth knowing about. It is the one that lets someone follow the work — an auditor, a manager, a stakeholder who wants the thread but not a vote — without being able to set an agent running.

What the agents can read

A channel can connect as many knowledge bases as it needs, up to 20, and each one is attached in one of two modes:

• Read — the coordinating agent can “search and retrieve” from that knowledge base.
• Edit — it can “search it and also create, update, and deprecate files.”

Then the rule that does most of the safety work here: member agents are “always read-only against every channel knowledge base, regardless of mode — only the planner can write.”

So attaching a knowledge base in Edit mode does not hand write access to twenty agents. It hands it to one, and the specialists you invited can read the same material without being able to change it. If you are used to thinking about this as a permissions matrix, the useful simplification is that a channel has exactly one writer.

Who coordinates

This is the part that differs most from a one-to-one conversation, and it differs again between the two ownership types.

In a personal channel, the built-in Insulin agent “acts as the coordinator” and can “invoke specialist agents on your behalf.”

In an organization channel, a Planner agent coordinates. It “plans the work, assigns each part to the member agent best suited to it” and “posts a combined summary.” And one constraint shapes everything else: “specialists never hand off to each other directly in an organization channel — only Planner delegates.”

That is a deliberate topology, not a limitation to work around. Agents handing off to each other directly is how a multi-agent system becomes impossible to follow — work disappears into a chain nobody watched, and when the answer is wrong there is no single place to look. Routing every delegation through one coordinator means the thread is the audit trail.

The Planner’s own reach is deliberately narrow. It plans and delegates, reads the channel knowledge bases at their configured modes, sets channel goals and schedules work, and uses no personal data. It “cannot reach email, calendar, files, or any third-party system,” and it never touches personal integrations or member knowledge bases. If you want a channel to act on an external system, that capability comes from a member agent scoped to it — not from the coordinator.

Three things a channel does not do

Worth knowing before you design a workflow around one.

A channel owns no jobs. From the documentation: “A channel owns no jobs of its own — its Jobs tab lists the jobs belonging to the agents that are members of the channel.” The Jobs tab is a view, not a container. Scheduling belongs to jobs and to the agents that own them.

Tool approvals do not appear. “The tool-approval card does not appear on channel turns.” In a solo chat, a sensitive action pauses and waits for you. In a channel it does not. That single sentence should drive which agents you make members: a channel is the wrong place for an agent whose value depends on a human stopping it mid-action. Put those in a one-to-one conversation where the approval gate is there, and keep channel membership for agents whose scope is safe to run unattended.

A personal channel has no other people. It is a coordination surface for your own agents, not a private room you can later add colleagues to — changing ownership to do that clears the membership you built.

Frequently asked questions

What is a channel in Insulin? A persistent group chat where multiple people and multiple agents collaborate in one thread, and everyone in the channel sees the same messages. It differs from a one-to-one conversation in that several agents can be members and one of them coordinates the others.

How many agents and people can a channel hold? Up to 20 agent members and up to 20 user members. User members apply to organization channels; a personal channel contains only your own user-level agents.

Can every agent in a channel edit a knowledge base? No. Member agents are always read-only against every channel knowledge base regardless of the mode it was attached in. Only the planner can create, update, or deprecate files, and only when the knowledge base is attached in Edit mode.

Do agents in a channel hand work to each other? Not in an organization channel. The Planner plans the work, assigns each part to the member agent best suited to it, and posts a combined summary. Specialists never delegate to one another directly.

Does a channel pause for approval before a sensitive action? No. The tool-approval card does not appear on channel turns. Choose channel member agents on that basis, and keep work that needs a human to intervene mid-action in a one-to-one conversation.

Takeaways

• A channel is one shared thread, not a room full of separate conversations. Everyone sees the same messages, which is what makes the thread usable as a record afterwards.
• Decide ownership first. Personal admits only your user-level agents; Organization admits org-level agents and people. Switching clears what you already picked.
• A channel has exactly one writer. Member agents are read-only against channel knowledge bases whatever mode they are attached in; only the planner writes.
• One coordinator, no side deals. In an organization channel the Planner delegates and specialists never hand off to each other — which is what keeps a multi-agent thread followable.
• No approval card on channel turns. Choose member agents accordingly.

Channels are where agents stop being individual assistants and start being a team with a coordinator. See the channels documentation for the full configuration reference, or book a demo to see one running.