One engineering team built a script to post daily Linear activity summaries to Slack at 9 AM. Their standups went from status recitation to blocker discussion - about eight minutes saved per standup, roughly 30 hours a month across the team. The script did one thing: read what each person had moved, completed, or commented on and post it before the call. No manual update, no copy-paste.
That team built something that the native Linear Slack integration still does not ship out of the box. Which raises the actual question: what does the integration do, and where does the real friction live?
What the Linear Slack integration actually does
The integration makes it easy to create, update, and view Linear issues from Slack. That sentence is accurate and also slightly misleading. What it really does is four distinct things, and most teams only use two of them.
A Slack channel can subscribe to Linear events scoped by team, project, label, or status, and receives a formatted message every time a matching event fires. The /linear slash command lets a Slack user create a Linear issue from inside a Slack thread, with the thread linked back to the issue. Message shortcuts let you turn any Slack message into a Linear issue in two clicks. URL unfurling renders Linear issue and project links inline with status, assignee, and the latest update.
The integration earns its keep when teams use the slash command and message shortcuts for capture, not just notifications. Most teams that find it disappointing are running it as a one-way notification firehose and missing the parts that actually save time.
The other thing worth knowing about notifications: each status change is a separate notification. During active cycles, channels get flooded with individual transitions. If you subscribe a channel to a whole team, that is what you get. Resist the temptation to subscribe a channel to a whole team. Scope by project or label instead, so the channel only sees events it can act on.
The wall most teams hit: who can actually create issues
Only users with Linear accounts can create issues in Slack using the Linear integration. Slack Guests cannot install or approve apps in Slack, so they'll be unable to use the Linear integration even if they have a Linear account.
This matters more than it sounds. On most product teams, the people filing bug reports and feature requests in Slack - support, sales, customer success, design contractors - do not have Linear seats. They report something in a channel, an engineer sees it and may or may not turn it into a ticket, and the Slack thread eventually dies with no record in Linear.
Linear Asks addresses this directly: it helps organizations manage internal requests that would otherwise be scattered across chat, email, and ad hoc forms. Once enabled, people can submit an Ask through Slack, email, or web forms.
Asks is available on both Business and Enterprise plans, with additional features for Enterprise workspaces through Advanced Linear Asks.
Linear Asks with Slack lets teams turn Slack conversations into issues in Linear without leaving the thread where the request started.
Once created, the Ask includes the Slack thread as context so the original conversation is easy to reference later. If you add more information to the Slack thread after the Ask is created, it will get updated in the Linear issue automatically.
The pricing angle here shifted significantly. Linear cut its Business tier pricing by 68% in seven months - from $50/user/month in July 2025 to $16/user/month in February 2026. That is one of the most aggressive price cuts tracked across SaaS tools. Asks requires Business. At $50/seat it was a harder ask. At $16/seat for a 10-person engineering team, that is $160/month total - the same ballpark as a Jira Premium subscription.
Linear Agent in Slack: what changed in March 2026
Linear Agent launched in public beta for all teams in March 2026. Agent and Skills are included on all Linear plans. Automations and Code Intelligence are available on Business and Enterprise.
The relevant surface for Slack users: mention @Linear in discussions on Slack to take actions in Linear based on your conversation's context. Use natural language to specify the details or simply let the agent infer what's needed.
In Slack, you can send: "@Linear Make issues based on the discussion here and assign them to me." The agent reads the thread, drafts issues, and creates them. It can also answer questions about your workspace - what's in the current cycle, who owns a system, what recently shipped.
Non-technical teammates can ask questions they'd normally have to track down an engineer to answer - how a feature works, who owns a system, what recently changed - and get a reliable response.
There is also an MCP path for teams already using Slackbot with MCP connectors. You can connect Linear's MCP server to Slackbot so it can access your Linear data when you ask it questions in Slack. A Slack admin adds Linear as a custom MCP server in Slackbot's connector settings.
Slackbot can call tools to read and update Linear on your behalf: list_issues and get_issue find issues filtered by team, assignee, project, label, status, priority, or cycle; save_issue creates a new issue or updates an existing one.
Beagle in action#product-feedback, 2:47pmThe gap the integration leaves open
The native integration handles notification routing and manual capture cleanly. That visibility is useful, but it still behaves more like a notification layer than a full Slack-based queue, triage, or support workflow. The native integration is a good fit when issue creation from Slack is occasional and manual, Linear Slack notifications are enough to keep teams aligned, and you do not need automation or workflow enforcement.
What the native setup does not do, even with Asks enabled:
Aggregated digests. No daily "here is what moved in your cycle" post. You build this with webhooks or a Slack app.
Cross-team dependency surfacing. Dependencies between teams are not surfaced. If your issue blocks another team's work, the native integration does not alert them.
Smart issue routing. No automatic severity assessment, duplicate detection, or suggested assignee based on expertise. Linear's triage AI does this inside the Linear interface on Business plans, but it does not fire automatically from a Slack message.
Reply tracking. The Slack thread syncs to a Linear issue comment thread, but there is no SLA tracking or response-time analytics on inbound requests.
The honest shape of the integration is: Linear owns the issue graph, Slack is the intake surface and notification rail. Anything that requires judgment about what the Slack message means - priority, ownership, severity, duplicate detection - still needs a human or an agent in the loop.
A teammate like Beagle can sit in those channels where engineering work gets discussed but never quite captured - turning the message that would have aged out of Slack into a tracked, prioritized issue, with a source link, before the engineer closes the tab.
Linear Slack integration: common questions
Does the Linear Slack integration work without a Linear account?
Linear Asks gives organizations a way to manage workplace requests where anyone can create an Ask and send their request to the relevant Linear team - even if they don't have a Linear account - via Slack or email. This requires Business or Enterprise plan. On the Basic plan, only team members with Linear accounts can create issues from Slack.
How do I stop Linear notifications from flooding my Slack channel?
Scope your subscriptions tightly. Linear lets you subscribe to issue created, status changed, comment added, and other events. For most channels, the right starting subscription is "issues created" and "status changed to In Review or Done." Subscribing to a full team fires on every event across every project - avoid it.
What can @Linear do in Slack?
You can use @Linear to summarize a conversation in a new document, sync Slack threads for immediate updates where replies and screenshots cross-post to the linked Linear issue, and share project updates automatically across Slack channels. With Linear Agent in beta, you can also ask it to create issues from a thread, answer questions about your workspace, and run saved skill workflows.
Is Linear Agent in Slack free?
During the beta period, all features are available at no additional cost. At general availability, chat functionality in-app, in comments, Slack, and Microsoft Teams is expected to remain included in the base seat price. High-volume compute capabilities like Automations and Code Intelligence may move to usage-based pricing beyond a certain threshold.
When does the Linear Slack integration not scale?
Many teams outgrow the native Linear Slack integration once Slack becomes the primary channel for requests, bugs, and questions. The breaking points are usually: non-Linear users needing to file requests at volume, teams needing aggregated cycle digests rather than per-event notifications, or cross-team workflows where one issue blocking another team should trigger an alert. At that point, webhooks plus a custom worker, or a platform like Beagle that sits in Slack and handles the judgment calls, fills the gap.