Linear Ecosystem

Linear is the work-management route when the task involves issues, projects, roadmaps, triage, team workflows, or issue-to-implementation handoff. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27

When To Use This

Use Linear when work needs structured issue state, project context, team ownership, or task handoff. Use GitHub when the unit of work is a repository PR, check, branch, or release. Source: Skill Resolver, 2026-06-27

Decision Matrix

Core Model

Linear owns work planning and team workflow. It should not replace code-review evidence or repository state. Treat it as the planning ledger that points to implementation proof. Source: Skill Resolver, 2026-06-27

Agent-Assisted Updates

Linear's 2026-06-18 changelog introduced Write with Agent for project and initiative updates. The agent reviews changes since the last update, checks messages in the linked Slack channel, writes a draft, then expects the human to refine and publish. The reviewed video thumbnail shows this as an inline comment/update composer state, not a separate chat product. Source: Linear changelog, 2026-06-18; local artifact wiki/assets/x-bookmarks/2067644255321911467/image-01.jpg, reviewed 2026-06-30

This is the right product shape for many internal agents: draft from the work ledger, include adjacent communication context, and keep a final human verify/post step. Route through Human-in-the-Loop Control when an agent's output represents an organization to other humans. Source: Agent Product Surface; Linear changelog, 2026-06-18

The same changelog also names Vercel Eve as a Linear-connected agent framework: custom agents can investigate incidents, monitor SLAs, analyze customer feedback, and be delegated to or mentioned in Linear. This strengthens Vercel Eve as a work-management integration surface, not only a standalone agent directory model. Source: Linear changelog, 2026-06-18

OAuth Manifests

Linear also added OAuth application manifests: URL parameters and JSON manifest files can pre-fill Linear OAuth app creation. Treat this as an integration setup pattern: source-owned manifests make app registration reviewable and reproducible instead of forcing agents to click through admin forms. Source: Linear changelog, 2026-06-18

Routing Summary

Preferred order: Linear MCP for issue/project data, linear for repeatable workflow automation, then GitHub/PR tools for implementation evidence. Source: Skill Resolver, 2026-06-27

Failure Modes

• Creating issue churn without owner, priority, or acceptance criteria.
• Treating Linear status as proof that code shipped.
• Mutating projects without confirming workspace/team.
• Losing the PR/check link.

Verification Path

Read the target team/project first. For writes, return the issue ID, URL, changed fields, and any linked PR or follow-up artifact. Source: Skill Resolver, 2026-06-27

---

Timeline

• 2026-06-27 | Canonical ecosystem page created so Linear has a product-level route alongside the executable skill. Source: User request, 2026-06-27; Ecosystem Capability Coverage
• 2026-06-30 | Deep-reviewed Linear's agent-assisted project updates bookmark: added Write with Agent, Vercel Eve integration proof, and OAuth application manifest setup pattern. Source: X/@linear, 2026-06-18; Source: Linear changelog, 2026-06-18
• 2026-11-02 | The two links to the Linear skill now point at linear. After the linear redirect was removed, they had led back to this page. Source: wiki overhaul Phase 5 review, 2026-11-02