Assign any Linear issue to @CellCog and get research, documents, images, and video delivered back as an agent session in the issue thread.
One admin connects, the whole team delegates.
When several team members comment on one issue, CellCog resolves who sent each message and addresses that person in its responses.
| Category | Examples |
|---|---|
| Research | Market analysis, competitive intelligence, technical research with citations |
| Documents | PDF reports, slide decks, spreadsheets, contracts |
| Visual | Images, infographics, diagrams, brand assets |
| Audio & Video | Voiceovers, music, marketing videos, explainers |
| Interactive | HTML dashboards, data visualizations, prototypes |
Artifacts are delivered as links in the issue thread and are accessible to members of the connected workspace.
cellcog.ai/linear is the integration overview, with an interactive simulator that shows how a Linear issue turns into a CellCog response. Log in (or sign up), click Connect Linear Workspace, and authorize CellCog in Linear.
Click Connect another workspace on the Linear page under Delegations. Linear's OAuth screen lets you pick the workspace. Each workspace is its own connection.
Open Connectors, then Delegations, then Linear. The header shows your connection status and the number of tasks delegated so far. Each connected workspace lists:
What happens:
The CellCog user who connected the workspace pays. Their credits are consumed for all activity in that workspace; there is no per-user billing. Tasks consume credits the same way as regular CellCog chats.
If someone else later reconnects the same workspace, the workspace is re-linked to that person, and their CellCog account is billed from then on.
| Permission | Purpose |
|---|---|
| Agent session access | Receive delegation webhooks when a user mentions @CellCog or assigns an issue; post back thoughts, questions, and final responses |
| Workspace metadata | Organization name, teams granted, and workspace member emails (for artifact access control) |
| Issue read + transition | Fetch issue context and move issues to Started on pickup |
Delegation and MCP are two different things:
To set up the MCP route: open Connectors, then Tools, then MCP servers. Add Linear's MCP endpoint URL, pick Sign in (OAuth) as the authentication, and complete the sign-in popup. Its tools then appear in any chat where Tools is enabled, behind your approval threshold like every other tool. See the Connectors Guide for the MCP servers page.
Use delegation when your team lives in Linear and wants results in the issue. Use the MCP route when the work starts in CellCog and Linear is one of the systems the agent should act on.
From CellCog: Connectors, then Delegations, then Linear, then Disconnect
From Linear: Linear Security Settings, then remove CellCog
For complete revocation, disconnect from both sides.
The CellCog user who connected the workspace. Their credits are consumed for all workspace activity.
Yes. Each workspace is its own connection. All of them bill to the CellCog account that connected them.
No. Connect once, and the whole workspace can delegate.
New tasks cannot start until credits are added.
No. It reads the issues it is assigned to or @-mentioned in.
Sessions that were marked errored on disconnect do not resume. The reconnected workspace is linked to whoever reconnects it, and their account is billed.
They appear as regular chats in the connecting user's CellCog account.
Every workspace bills to the CellCog account that connected it, and one CellCog account is one organization, one company. Running a second company means a second CellCog account with an email on that company's domain; connect the second company's Linear workspace from there.
Delegation when the work starts in Linear and should end in the issue. MCP when the work starts in a CellCog chat and Linear is one of the tools the agent should use. Both can be set up at the same time.