The first agent in Linear
that isn’t a coder.
CellCog lives inside Linear as your team’s multimodal teammate — research, reports, presentations, images, video, and dashboards — delivered as native Linear agent activities.
Free to install · 5-second setup · Task credit from CellCog account · View pricing →
Research our top 5 competitors and write a comparison PDF
Need a deep-dive competitive analysis with positioning map and pricing matrix. Attach the output to this ticket when done.
Click here to assign this issue to an agent
CellCog’s progress will stream here once you assign the task.
The flow is just Linear.
No new interface to learn. No context switching. Delegation happens inside the tool your team already uses.
Assign
Assign any Linear issue to @CellCog, or @mention it in a comment. No special syntax. No separate interface.
Watch
CellCog thinks out loud. Follow along in Linear’s agent session panel. Ask follow-up questions in comments. CellCog asks clarifying questions when it needs them.
Ship
When CellCog completes, you get a response activity with clickable artifacts — documents, videos, apps, dashboards — all viewable by your Linear teammates with their Linear email.
Built on Linear’s agent platform —
not next to it.
Not a wrapper around Linear’s API. A proper integration with Linear’s actual primitives.
mutation AgentActivityCreate($input: AgentActivityCreateInput!) {
agentActivityCreate(input: $input) {
activity { id type }
}
}Native Linear AgentSession — not webhook polling
CellCog publishes to Linear’s agentActivityCreate mutation as it works. Thoughts stream ephemerally. The final answer batches into a single response activity. When CellCog needs input, it emits an elicitation — and Linear’s session state moves to awaiting_input automatically.
query IssueContext($id: String!) {
issue(id: $id) {
comments(first: 50) { nodes { body user { name } } }
attachments { nodes { url title } }
subIssues { nodes { identifier title } }
}
}Two-way context via Linear’s GraphQL API
CellCog isn’t frozen on the initial prompt. When it needs more context — sub-issues, comments, attached files, related tickets — it queries Linear’s schema on-demand. Introspection-first, read-only, AST-validated. About half of non-trivial tasks need this, and it works invisibly to the user.
Sender identity across multi-user Linear threads
One Linear workspace has many humans. We resolve who sent each specific message through a 6-path fallback — webhook payload first, Linear GraphQL as authoritative backup — so CellCog addresses each sender by name even when ten teammates share the same thread.
Team-based artifact access via Linear workspace membership
When CellCog generates a PDF or a dashboard, your Linear workspace members open it with their Linear email. Sync is real-time via Linear’s User webhooks — no manual sharing, no per-file permissions, no stale member lists.
Secure by construction
OAuth 2.0 tokens encrypted at rest with Fernet. Webhook payloads HMAC-verified. All user-authored content sanitized against prompt injection at three layers — tool responses, sender fields, attachment metadata. Revoke from CellCog or from Linear’s application settings; we honor both.
Built for teams, not just you.
Security, access, and billing designed for how Linear workspaces actually work.
Workspace-level install
One admin installs. The whole Linear workspace can delegate tasks. No per-user signup friction for your teammates.
Transparent billing
Tasks consume credits from the installer’s CellCog account. All workspace members share the same credit pool. See usage in the CellCog billing dashboard. View plans →
Revoke anytime
Disconnect from your CellCog profile settings, or directly from Linear’s Application Settings. Active sessions are errored cleanly. Both sides stay in sync.
Questions people actually ask.
CellCog lives in the tools your team already uses.
One CellCog account, many surfaces. Add a Linear workspace, a Cursor plugin, a Claude Code install, or an API key to your custom agent.
