# linear.app 15 of 15 indexed pages, ordered by how often the site's own pages cite them. This is all of them. Indexed by stealpage. Full record: https://stealpage.com/d/linear.app --- ## Download Linear · 43 words ![Linear desktop app icon](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/82d07241-84b3-4cdf-33b5-a09b8d169300/f=auto,fit=scale-down,metadata=none) Available for web, macOS, Windows, iOS, and Android. [Open Web app](https://linear.app/login) Linear Desktop. A fast and focused experience to plan and build your product. Linear Mobile. Designed for “away from keyboard” workflows that complement the desktop experience. iOS Android --- ## Linear Customers · 321 words 2.0x Increase in filed issues 3.3x Faster issue resolution 50% Issues authored by agents Powering more than 40,000 organizations. From ambitious startups to major enterprise and Fortune 20 companies. [ ![Pleo logo](https://webassets.linear.app/images/ornj730p/production/b778fb6b1f4c768fff589d5d9070b4bf3a92f26b-56x56.svg?q=95&auto=format&dpr=2) Pleo Pleo transitioned their internal support workflows to Linear Asks Fintech Read story → ](https://linear.app/customers/pleo)[ ![Klaviyo logo](https://webassets.linear.app/images/ornj730p/production/e08b228973f347e41fd1ded59d70f7a8af7a5b24-56x56.svg?q=95&auto=format&dpr=2) Klaviyo Klaviyo boosts visibility and velocity with Linear SaaS, Enterprise Read story → ](https://linear.app/customers/klaviyo)[ ![Mercury logo](https://webassets.linear.app/images/ornj730p/production/91c55d098003b92c00d5ab8ccc38ba3040fb0557-56x56.svg?q=95&auto=format&dpr=2) Mercury Mercury eliminated cluttered feedback with Linear Asks Fintech, Enterprise Read story → ](https://linear.app/customers/mercury)[ ![Sierra logo](https://webassets.linear.app/images/ornj730p/production/805551cdc94ee1d8627cb5e00fd73baec0904ce2-56x56.svg?q=95&auto=format&dpr=2) Sierra From project updates to accountability, Sierra moves as one company in Linear AI Read story → ](https://linear.app/customers/sierra)[ ![Cash App logo](https://webassets.linear.app/images/ornj730p/production/896d0e6ed13122608df8aa1a57bb3c19e9ad4862-56x56.svg?q=95&auto=format&dpr=2) Cash App Linear helps Cash App manage aggressive roadmaps Fintech, Consumer, Enterprise Read story → ](https://linear.app/customers/cashapp)[ ![Clay logo](https://webassets.linear.app/images/ornj730p/production/8861e93599dc80b90e04ae88157af4abc3391e80-56x56.svg?q=95&auto=format&dpr=2) Clay How Clay manages bugs using Linear SaaS Read story → ](https://linear.app/customers/clay)[ ![Watershed logo](https://webassets.linear.app/images/ornj730p/production/66314c542672167823e48ab60156459e5f1ca252-56x56.svg?q=95&auto=format&dpr=2) Watershed Watershed switched to Linear to accelerate their team SaaS Read story → ](https://linear.app/customers/watershed)[ ![Clio logo](https://webassets.linear.app/images/ornj730p/production/314cde3cd6d3063546973af031b72abab6bdeede-56x56.svg?q=95&auto=format&dpr=2) Clio How Linear helps engineering managers at Clio operate more efficiently SaaS, AI, Enterprise Read story → ](https://linear.app/customers/clio)[ ![Descript logo](https://webassets.linear.app/images/ornj730p/production/5494a32be3c77b5fd654e93da0a47b624d5ad4d3-56x56.svg?q=95&auto=format&dpr=2) Descript Why Descript builds with Linear SaaS, AI Read story → ](https://linear.app/customers/descript)[ ![Retool logo](https://webassets.linear.app/images/ornj730p/production/900344db813b157d72157b63aa859156a8e49b41-56x56.svg?q=95&auto=format&dpr=2) Retool How Retool turns customer feedback into engineering work SaaS Read story → ](https://linear.app/customers/retool)[ ![Remote logo](https://webassets.linear.app/images/ornj730p/production/159083854336376173d7b08664db1a6d53f3cdb2-56x56.svg?q=95&auto=format&dpr=2) Remote Remote switched their 1,000 person team to Linear to move faster SaaS, Enterprise Read story → ](https://linear.app/customers/remote)[ ![Cohere logo](https://webassets.linear.app/images/ornj730p/production/a29aa6a5a361fe63e0c0b0ed7016d20c71b08c32-56x56.svg?q=95&auto=format&dpr=2) Cohere Why Cohere builds with Linear AI Read story → ](https://linear.app/customers/cohere)[ ![Raycast logo](https://webassets.linear.app/images/ornj730p/production/e49b121abff6209db36584e2bc070ddb3b3dd5f2-56x56.svg?q=95&auto=format&dpr=2) Raycast Why Raycast builds with Linear SaaS Read story → ](https://linear.app/customers/raycast)[ ![Semgrep logo](https://webassets.linear.app/images/ornj730p/production/86b90fd7c098af86bd4bd36b6723c86efb147896-56x56.svg?q=95&auto=format&dpr=2) Semgrep Why Semgrep builds with Linear SaaS Read story → ](https://linear.app/customers/semgrep)[ ![Lightricks logo](https://webassets.linear.app/images/ornj730p/production/385544c10c843445c6a7ccd840bb6993cfad58f4-56x56.svg?q=95&auto=format&dpr=2) Lightricks Improving how teams work together at Lightricks AI Read story → ](https://linear.app/customers/lightricks)[ ![Alan logo](https://webassets.linear.app/images/ornj730p/production/a24595dad6f23ede11eb3182bab9586df2435dae-56x56.svg?q=95&auto=format&dpr=2) Alan Why Alan builds with Linear Health, Fintech Read story → ](https://linear.app/customers/alan)[ ![Twingate logo](https://webassets.linear.app/images/ornj730p/production/6b446f5aeb06ea5cbb24bd7169ef4ab3ebe12326-56x56.svg?q=95&auto=format&dpr=2) Twingate Why Twingate builds with Linear SaaS Read story → ](https://linear.app/customers/twingate)[ ![Pulley logo](https://webassets.linear.app/images/ornj730p/production/e7c7bf5936627ae1ccf55365d451a302af9d57a3-56x56.svg?q=95&auto=format&dpr=2) Pulley How Pulley uses Linear beyond their product teams Fintech Read story → ](https://linear.app/customers/pulley)[ Your company Make the switch ](https://linear.app/switch) --- ## Linear – Agents that follow work from conversation to code · 612 words AI and automations ![Create issues from conversationMention @Linear in Slack or Teams to turn discussions into scoped issues with the surrounding context.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/d88e5465-ccb5-446e-a95d-148b4c258f00/f=auto,fit=scale-down,metadata=none) *Create issues from conversationMention @Linear in Slack or Teams to turn discussions into scoped issues with the surrounding context.* ![Draft project updatesSummarize progress, risks, blockers, and recent changes into an update your team can review and post.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/5d4fbe20-2d39-43f1-e890-14443f445800/f=auto,fit=scale-down,metadata=none) *Draft project updatesSummarize progress, risks, blockers, and recent changes into an update your team can review and post.* ![Plan the next cycleRead the backlog, find repeated themes, and suggest what should move into the next cycle.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/341d7318-a62f-4f08-5689-fd7e54679500/f=auto,fit=scale-down,metadata=none) *Plan the next cycleRead the backlog, find repeated themes, and suggest what should move into the next cycle.* ![Check project statusSee what’s at risk, what’s falling behind,and where your attention is needed.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/34bcabf2-61fa-49e0-fcb3-b6df13ac3600/f=auto,fit=scale-down,metadata=none) *Check project statusSee what’s at risk, what’s falling behind,and where your attention is needed.* ![Save reusable skillsSave useful agent conversations as skills your team can run again from chat or a slash command.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/a75e6d0f-a835-4aeb-856c-092d4a58e300/f=auto,fit=scale-down,metadata=none) *Save reusable skillsSave useful agent conversations as skills your team can run again from chat or a slash command.* Triggeredtriage check Weeklyreview Dailysummary #### Put recurring work on a loop. Run agents on a schedule or when work matches your criteria. Each loop keeps its run history as context, so every pass builds on the last. ![Automate the overheadTriage Intelligence suggests assignees, teams, projects, labels, and related issues based on how your team already works.](https://webassets.linear.app/images/ornj730p/production/e522be49c136f6b81a1c5cb3aa7b2075f78404c0-1305x1444.jpg?w=72&q=95&auto=format&dpr=2) *Automate the overheadTriage Intelligence suggests assignees, teams, projects, labels, and related issues based on how your team already works.* ![Put incoming issues on autopilotUse rules to prioritize key customers, escalate critical bugs, and route new work before it slows the team down.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/4fbb70ab-8009-4d33-331e-4c203f49d700/f=auto,fit=scale-down,metadata=none) *Put incoming issues on autopilotUse rules to prioritize key customers, escalate critical bugs, and route new work before it slows the team down.* ![Assign your issues to LinearStart a session from any issue or conversation. Linear gathers context, works in a secure cloud sandbox, and comes back with a diff your team can follow.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c6519adf-c944-43ab-8690-e9330b0c9f00/f=auto,fit=scale-down,metadata=none) *Assign your issues to LinearStart a session from any issue or conversation. Linear gathers context, works in a secure cloud sandbox, and comes back with a diff your team can follow.* ![Background automationAssign issues directly, or let Linear pick them upthe moment they land in Triage.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/0afd2efe-f91d-46f3-de70-718538a93100/f=auto,fit=scale-down,metadata=none) *Background automationAssign issues directly, or let Linear pick them upthe moment they land in Triage.* ![Answers from the sourceAsk about your codebase and get answers grounded in the implementation, recent changes, and people with context.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/e357c29c-fcc4-4e0b-58e4-a149a96c5200/f=auto,fit=scale-down,metadata=none) *Answers from the sourceAsk about your codebase and get answers grounded in the implementation, recent changes, and people with context.* ![Iterate with agentsReview feedback, resolved at agent speed. Make changes from the diff and watch updates appear inline.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/a5be8aeb-8722-42eb-4e84-0a48d1460500/f=auto,fit=scale-down,metadata=none) *Iterate with agentsReview feedback, resolved at agent speed. Make changes from the diff and watch updates appear inline.* ![Guided reviewsGuided Reviews organize diffs by showing what changed and why, with a clear path through complex changes.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/5077757d-8028-4ffc-973a-67cbed0f2400/f=auto,fit=scale-down,metadata=none) *Guided reviewsGuided Reviews organize diffs by showing what changed and why, with a clear path through complex changes.* ![Work in motionSee what’s running, what shipped, and whatneeds a human across every team and agent.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/26f2d1a1-fcd5-4d95-b526-6aa507e2f800/f=auto,fit=scale-down,metadata=none) *Work in motionSee what’s running, what shipped, and whatneeds a human across every team and agent.* ![Bring more context inConnect tools like Granola, Glean, Notion, and PostHog to ground investigations, specs, and updates in more context.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/79dee234-006d-40ab-1a44-4ee6b9918e00/f=auto,fit=scale-down,metadata=none) *Bring more context inConnect tools like Granola, Glean, Notion, and PostHog to ground investigations, specs, and updates in more context.* ![Take your context anywhereLinear’s MCP server gives compatible AI tools secure access to your issues, projects, and comments.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/545b96b3-62d9-44c8-74b3-6dd4c7c9cc00/f=auto,fit=scale-down,metadata=none) *Take your context anywhereLinear’s MCP server gives compatible AI tools secure access to your issues, projects, and comments.* --- ## Linear Intake – Self-driving product operations · 528 words Intake and integrations ![Create issues at the speed of conversationMention @Linear in discussions on Slack or Microsoft Teams, and the Linear agent will create issues informed by your conversation’s context.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/b84abacb-7cea-4443-112d-5fe66f8f1600/f=auto,fit=scale-down,metadata=none) *Create issues at the speed of conversationMention @Linear in discussions on Slack or Microsoft Teams, and the Linear agent will create issues informed by your conversation’s context.* ![From intent to PR with a single commandTurn Slack and Microsoft Teams threads into issues and assign them directly to a coding agent. No handoffs required.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/885931ae-6049-4c94-cca0-2c90b0aa9500/f=auto,fit=scale-down,metadata=none) *From intent to PR with a single commandTurn Slack and Microsoft Teams threads into issues and assign them directly to a coding agent. No handoffs required.* ![Turn support tickets into issues with a single clickAuto-create well-scoped issues from Intercom and Zendesk conversations – even across long, multi-topic threads.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/ce941a08-c73d-4b5e-9389-80ce62b1b300/f=auto,fit=scale-down,metadata=none) *Turn support tickets into issues with a single clickAuto-create well-scoped issues from Intercom and Zendesk conversations – even across long, multi-topic threads.* ![Auto-create issues from customer callsAutomatically capture product feedback from Gong transcripts and route them into Linear. No prompts or clicks required.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c89b6d17-3d6b-488f-cdcf-d8454d1b9000/f=auto,fit=scale-down,metadata=none) *Auto-create issues from customer callsAutomatically capture product feedback from Gong transcripts and route them into Linear. No prompts or clicks required.* ![Create requests and bug reports from anywhereIntegrate Linear with the rest of your tools to create issues directly from your CRM, monitoring system, email, and more.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/89216e43-f46d-487c-2f34-c98f050cba00/f=auto,fit=scale-down,metadata=none) *Create requests and bug reports from anywhereIntegrate Linear with the rest of your tools to create issues directly from your CRM, monitoring system, email, and more.* ![Automate the overheadTriage Intelligence proactively suggests and applies the right assignees, teams, projects, and labels based on your team’s historical patterns.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/27f30e58-a465-4992-164a-2dd2ed1e4c00/f=auto,fit=scale-down,metadata=none) *Automate the overheadTriage Intelligence proactively suggests and applies the right assignees, teams, projects, and labels based on your team’s historical patterns.* ![Find duplicates before they slow you downTriage Intelligence identifies similar issues and links related work, so you don’t end up with three versions of the same thing.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/b631c9bc-a9a9-492a-1a19-3ec8bdde2000/f=auto,fit=scale-down,metadata=none) *Find duplicates before they slow you downTriage Intelligence identifies similar issues and links related work, so you don’t end up with three versions of the same thing.* ![Put incoming issues on autopilotAutomatically process incoming issues with predefined rules to prioritize key customers or escalate critical bugs.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/4fbb70ab-8009-4d33-331e-4c203f49d700/f=auto,fit=scale-down,metadata=none) *Put incoming issues on autopilotAutomatically process incoming issues with predefined rules to prioritize key customers or escalate critical bugs.* ![Auto-assign issuesUse a triage responsibility schedule to automatically assign or notify specific team members.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/1a2c30e4-5ba9-4c16-36e2-8c8e0b9f1400/f=auto,fit=scale-down,metadata=none) *Auto-assign issuesUse a triage responsibility schedule to automatically assign or notify specific team members.* #### SLAs Apply automatic deadlines to time-sensitive issues to communicate urgency. ![Understand customer needs in full contextual detailCapture feedback across any customer interaction – from sales calls to support chats – and turn it into a customer request linked to a Linear project or issue.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/b8fb7e59-47e9-4944-f8a7-544efe153300/f=auto,fit=scale-down,metadata=none) *Understand customer needs in full contextual detailCapture feedback across any customer interaction – from sales calls to support chats – and turn it into a customer request linked to a Linear project or issue.* ![Create powerful helpdesk workflowsStandardize workplace requests with forms and templates, and automatically route them to the right team in Linear.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/d3476031-9f48-45e7-94c7-059c2b622a00/f=auto,fit=scale-down,metadata=none) *Create powerful helpdesk workflowsStandardize workplace requests with forms and templates, and automatically route them to the right team in Linear.* --- ## Linear – Plan and navigate from idea to launch · 573 words Planning and monitoring ![Close the gap between planning and buildingConsolidate project specs, documents, issues, customer feedback, and updates in one centralized location.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/028734bb-2e5c-463d-c4ef-702eef293500/f=auto,fit=scale-down,metadata=none) *Close the gap between planning and buildingConsolidate project specs, documents, issues, customer feedback, and updates in one centralized location.* ![Milestones and dependenciesHighlight key dates and map out critical paths between projects to streamline resource allocation and execution.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/b376c074-a6a6-4eeb-fd82-55c6023c0f00/f=auto,fit=scale-down,metadata=none) *Milestones and dependenciesHighlight key dates and map out critical paths between projects to streamline resource allocation and execution.* ![Predict project outcomesUnderstand how your project is progressing and when it’s likely to complete, with scope and velocity visualized over time.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/f04b632b-6d2a-44e6-9d9b-8791ed595200/f=auto,fit=scale-down,metadata=none) *Predict project outcomesUnderstand how your project is progressing and when it’s likely to complete, with scope and velocity visualized over time.* ![Keep everyone up-to-date...Communicate health and progresswith built-in project updates.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/2a9cf1c1-104c-4c4c-3b7b-a32fdaf0c200/f=auto,fit=scale-down,metadata=none) *Keep everyone up-to-date...Communicate health and progresswith built-in project updates.* ![Linear](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/99b79259-77e8-4ea5-232f-0c13ae00ee00/f=auto,fit=scale-down,metadata=none) *...even if they are not in LinearAutomatically share project updates on Slack with bi-directionally synced comment threads.* ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/ed465fec-1482-4e76-9e14-7cc00c408f00/f=auto,fit=scale-down,metadata=none) ![Make strategic product work legible with InitiativesInitiatives serve as a canonical entry point, aligning everyone on the most important product efforts in your company.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/7f28d1ad-41ae-4253-a9f7-1c7f4a7c3e00/f=auto,fit=scale-down,metadata=none) *Make strategic product work legible with InitiativesInitiatives serve as a canonical entry point, aligning everyone on the most important product efforts in your company.* ![Align everyone on the strategyProvide a detailed summary for each initiative and link to resources and related documents.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/6ead787a-4eda-49eb-96bd-33fc939feb00/f=auto,fit=scale-down,metadata=none) *Align everyone on the strategyProvide a detailed summary for each initiative and link to resources and related documents.* ![Monitor progress at scaleQuickly see if your initiatives are on trackand identify any projects blocking progress.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/831ff340-6657-4e70-5124-4cb65208ca00/f=auto,fit=scale-down,metadata=none) *Monitor progress at scaleQuickly see if your initiatives are on trackand identify any projects blocking progress.* ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/8e00aad9-af8e-4f17-8401-c32df3291600/f=auto,fit=scale-down,metadata=none) Quarterly planningAlign teams on what’s shipping Product pipelineMonitor delivery stages across initiatives TimelineCreate roadmaps to plan visually Resource allocationBalance staffing across projects ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/d413c874-4d2f-47a7-859e-bf25d4227000/f=auto,fit=scale-down,metadata=none) ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/b83f4300-efb7-43f8-f9eb-efb645bb9100/f=auto,fit=scale-down,metadata=none) ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/e6b66162-3128-4581-4af6-c24a75f6c300/f=auto,fit=scale-down,metadata=none) ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/d9d11e0a-57b5-4a69-e087-6a9b95346b00/f=auto,fit=scale-down,metadata=none) ![A personalized feed for what’s happening across your companyPulse brings relevant updates from across your Linear workspace into a single unified feed tailored to the workstreams that are most important to you.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/f8306355-7133-4ff4-5e6a-562d3017fa00/f=auto,fit=scale-down,metadata=none) *A personalized feed for what’s happening across your companyPulse brings relevant updates from across your Linear workspace into a single unified feed tailored to the workstreams that are most important to you.* ![Narrow in on what’s most relevantCreate custom Pulse feeds to focus on a targeted subset of project and initiative updates.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c1c4aa7e-842c-4e54-0001-3613c5828800/f=auto,fit=scale-down,metadata=none) *Narrow in on what’s most relevantCreate custom Pulse feeds to focus on a targeted subset of project and initiative updates.* ![AI summaries, delivered to your inboxReceive a personal AI-generated update summary in your Linear inbox, available as text or a short audio digest.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/4a18c6df-6b52-4c87-b41a-f6c3bf96b500/f=auto,fit=scale-down,metadata=none) *AI summaries, delivered to your inboxReceive a personal AI-generated update summary in your Linear inbox, available as text or a short audio digest.* ![Instant analytics for any stream of workBuilding truly great products is both art and science. It’s part intuition and part data. To help with the data part, Linear offers a variety of advanced analytics features.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/8db6f0de-7c82-4805-1f72-3e7c97478100/f=auto,fit=scale-down,metadata=none) *Instant analytics for any stream of workBuilding truly great products is both art and science. It’s part intuition and part data. To help with the data part, Linear offers a variety of advanced analytics features.* ![Combine insights into dashboardsCreate custom, fully modular dashboardsto monitor and understand key metrics.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/725902d3-e9b6-435b-7176-d2fffdfc7f00/f=auto,fit=scale-down,metadata=none) *Combine insights into dashboardsCreate custom, fully modular dashboardsto monitor and understand key metrics.* ![Build your own reportingExport Linear data to Google Sheets,Fivetran, or Airbyte for deeper analysis.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/d4a8bdee-d32b-4dec-f205-c59a3e1a9400/f=auto,fit=scale-down,metadata=none) *Build your own reportingExport Linear data to Google Sheets,Fivetran, or Airbyte for deeper analysis.* --- ## Loops – Linear Docs · 2004 words ![Loops](https://webassets.linear.app/images/ornj730p/production/d50a83fccc38ccc78ad8c0092dbd8796d092e759-3600x2080.png?w=1440&q=95&auto=format&dpr=2) ### Overview[⁠](#overview) Loops let Linear drive work forward automatically. They can trigger on a scheduled cadence, or when issues match a set of conditions. Consider creating loops for repeatable tasks, like: - When an issue enters this team’s triage queue, investigate its likely root cause with [Code Intelligence](https://linear.app/docs/code-intelligence). If you think you can fix it, start a coding session. - Every Monday afternoon, review projects that had their first update in the last week or were mentioned as newly kicked off in `@Weekly sync document`. Send a Slack message to the `#product-marketing` channel so they’re aware of what’s coming. - When an issue is created in team Mobile, create separate issues for the iOS and Android teams, if relevant. Each loop has a schedule or issue-based trigger, instructions for the agent, optional MCP connectors for communicating with other services, and permissions that control its access. Loops can be configured for a specific team, a set of teams, or the whole workspace. ### Example loops[⁠](#example-loops) Here are some basic loops that are useful for most workspaces. Create custom loops for your team by prompting Linear, or get started with one of these examples. ##### Investigate and delegate bug reports ([Build this loop ↗](https://linear.app/agent?skill=loop-bug-triage))[⁠](#investigate-and-delegate-bug-reports-\(build-this-loop-\)) When new bugs arrive in Triage, check the codebase for a root cause. Delegate the issue to Linear to fix if the cause is found. Elapsed00:00 Remaining time unknown ##### Create follow-up issues from resolved incidents: ([Build this loop ↗](https://linear.app/agent?skill=loop-incident-follow-up))[⁠](#create-follow-up-issues-from-resolved-incidents:-\(build-this-loop-\)) When an issue with an incident label is marked done, do a root cause analysis and create follow-up issues. Elapsed00:00 Remaining time unknown ##### Create platform specific versions of incoming requests: ([Build this loop ↗](https://linear.app/agent?skill=loop-cross-platform-handoff))[⁠](#create-platform-specific-versions-of-incoming-requests:-\(build-this-loop-\)) When a new incoming issue is created, determine if new issues also need to be created for multiple platforms. Elapsed00:00 Remaining time unknown ##### Create user-facing messaging after issues close: ([Build this loop ↗](https://linear.app/agent?skill=loop-customer-follow-up))[⁠](#create-user-facing-messaging-after-issues-close:-\(build-this-loop-\)) After an issue closes, check the PR that closed it and generate user-facing messaging that Support can share with customers. Elapsed00:00 Remaining time unknown ### Create loops with Linear Agent[⁠](#create-loops-with-linear-agent) The best way to create loops is to first achieve the outcome you want in a Linear Agent chat, then continue to refine it into a loop. For example, you might be the lead of a project that has check-in meetings each Thursday morning. You’re about to write the agenda, but realize you could automate this instead. - Press ⌘/Ctrl + J to open a Linear Agent chat - Prompt Linear: Check the project Slack channel, open questions in the last update, and any issue threads that seem relevant. Add a new section in the Meetings project document with those details, using a format like \[...\] - Review the result to make sure it looks right. If it doesn’t, continue prompting Linear until the agenda looks complete, and in the desired format. - Then, ask Linear to create the loop. You’ll be prompted to add any missing details. ### Create loops manually[⁠](#create-loops-manually) You can also create a new loop directly in the interface. 1. In your sidebar, click **Loops** under the workspace group to start a new workspace-level loop. To create a new team loop, click the team name in your sidebar, then choose the **Loops** tab on that page. 2. Click **New loop** 3. Choose a trigger: an issue being created or updated and meeting conditions, or a schedule 4. Add instructions describing the outcome you want Linear to achieve 5. Optionally, add [MCP connectors](https://linear.app/docs/loops#mcp-connectors) 6. Review the loop’s scope and permissions 7. Click **Create loop** ![Create a Loop](https://webassets.linear.app/images/ornj730p/production/6902521b8d5f52eaa4f8cbc3ac9c98d547b3a27a-3056x2056.png?w=1440&q=95&auto=format&dpr=2) ### Update loops[⁠](#update-loops) Prompt Linear to update an existing loop, or make changes directly in the interface: 1. Open the list of **Loops** 2. Select the loop you want to update 3. Click **Edit** 4. Update the loop fields as needed. These changes are saved as a draft, and not yet live. 5. Click on **Publish** to apply all changes at once to the loop ![Edit a Loop](https://webassets.linear.app/images/ornj730p/production/7cfdb82ac59fc2ffa4e21feb2a1ddc5bc0900620-1800x1200.png?w=1440&q=95&auto=format&dpr=2) ### Review a loop’s runs[⁠](#review-a-loop's-runs) Each loop has a run history to let you audit its behavior. 1. Open **Loops** from the workspace or team that contains the loop 2. Open the loop you want to review 3. Select **Run history** 4. Review recent runs to see when the loop executed and what actions it took ![Run History Menu](https://webassets.linear.app/images/ornj730p/production/cf3bfc297bb27d85829dd05f6e0512ffe4d9a925-1988x882.png?w=1440&q=95&auto=format&dpr=2) ![Run History](https://webassets.linear.app/images/ornj730p/production/fd188bde19309e260dd9c92798b3a89b5cf2a1d8-3056x2056.png?w=1440&q=95&auto=format&dpr=2) ### Restoring a previous version[⁠](#restoring-a-previous-version) All published versions of a loop are saved and can be restored. Please note that removed connectors cannot be restored as they need to be authenticated again manually. 1. Start editing a loop as usual 2. Click on **Published versions** 3. Select a past version you want to restore 4. Click on **Restore version** ### MCP Connectors[⁠](#mcp-connectors) MCP connectors extend what Linear Agent can do during a loop run. When a connected MCP is available to a loop, Linear can use it to gather context or take supported actions in other services. For example: - Search or retrieve content from connected sources such as GitHub, Notion, or Sentry - Post comments or updates to external services like Slack - Fetch documentation, pull request details, or error reports to enrich an issue An MCP connector can only access data and perform actions that are permitted by the available MCP’s configuration and the loop’s data scope. When a user connects an MCP to a loop, they authorize that loop to act in the other service, so connector access should be granted thoughtfully. ![MCP Connectors available during a loop run](https://webassets.linear.app/images/ornj730p/production/1f5637a8a67dcada4d191a4dd6f05ea00cf00da0-1009x435.png?w=1440&q=95&auto=format&dpr=2) #### Managing available Connectors[⁠](#managing-available-connectors) Owners (Enterprise) or workspace Admins (Business) can elect to let users connect any MCP connector, or only allowlisted servers. ![security settings MCP server section -- All severs or only specific servers](https://webassets.linear.app/images/ornj730p/production/edd247935723320b36a2592447ed0793bf5c8a7a-959x625.png?w=1440&q=95&auto=format&dpr=2) If _Only specific connectors_ are selected, each MCP must first be approved in your workspace before it can be used in a loop. Workspace admins and owners can configure the full set of MCP connectors allowed in a workspace in [Security](https://linear.app/settings/security) settings. Once an MCP server has been added, users can add it when creating or updating a loop. Adding one requires the configuring user to authenticate with the connector, and it will use their personal account’s connection. ### Setup[⁠](#setup) - Workspace owners can manage who can create and manage workspace loops in [**Settings → Security → Workspace management → Manage loops**](https://linear.app/settings/security). - Team owners can control who can create and manage loops in **Settings → Teams → \[Team name\] → Access and permissions → Loop management**. ![Manage Loops Access](https://webassets.linear.app/images/ornj730p/production/f88dbcfb9a980145855dce2c8108fdec226f930c-1924x850.png?w=1440&q=95&auto=format&dpr=2) ### Permissions[⁠](#permissions) Loops support a range of permissions to control what they can access and do. Enable only the permissions your loop needs to fulfill its intended purpose, and consider the impact of each one before enabling it. ![Loop Permissions](https://webassets.linear.app/images/ornj730p/production/1e2a0a3a5f883454fdf4c77f8eb02d63cf8ea227-1988x1704.png?w=1440&q=95&auto=format&dpr=2) #### Team access[⁠](#team-access) Controls which teams the loop can access. It can read and write data only in those teams. By default, a loop at the workspace level or in a public team will have access to all public teams, while a loop inside a private team will have access only to that team. Loops that can access all public teams can also access workspace-level objects like Initiatives and Customers. #### Web access[⁠](#web-access) If enabled, the loop can query any website. You can use this to set up loops that can take actions like researching competitor announcements, or checking the documentation of services your product integrates with. Use caution when enabling web access. **Web access can send workspace content to external services.** Do not enable it for loops that may process sensitive data unless you are comfortable with that data leaving Linear. #### Code Intelligence[⁠](#code-intelligence) If enabled, the loop can use [Code Intelligence](https://linear.app/docs/code-intelligence) to browse and analyze repositories configured in your workspace. Enable Code Intelligence for loops designed to investigate bugs or answer questions about your code. #### Coding sessions[⁠](#coding-sessions) If enabled, the loop will be able to start a [coding session](https://linear.app/docs/coding-sessions) to open a draft pull request. Allow coding session access for loops that delegate implementation work to Linear. #### Externally synced issues and comments[⁠](#externally-synced-issues-and-comments) If enabled, the loop will be able to write data on issues or comment threads that are synced with external applications, like issues created from Slack with bi-directionally synced threads. Enable this with care, as some synced threads may be visible outside your workspace — if you use [GitHub sync](https://linear.app/docs/github#configure-github-issues-sync) in a public repo for instance, the loop would be able to post comments to that repo’s GitHub Issues. #### External sources[⁠](#external-sources) Issues can be created from sources outside Linear, like Slack messages or emails received to a particular address. For security reasons, loops will only run by default on issues created from within Linear. If you want a loop to run on issues created from external sources, you can enable specific external sources on a per-loop basis. Workspace owners can configure the list of allowed external sources in [Security](https://linear.app/settings/security) settings. After that, configured external sources can be enabled for individual loops. #### Allow changes outside of triggering issue[⁠](#allow-changes-outside-of-triggering-issue) If enabled, the loop can write data to any issues included in the **Team access** scope. If disabled, the loop can only write data on the single issue that triggered the loop for a given run. ### AI credits[⁠](#ai-credits) Starting July 20, Loops will require AI credits to run. AI credits are purchased and managed by workspace admins in [Settings](https://linear.app/settings/billing). To help your team get started, we’re giving Business and Enterprise workspaces **$20 per seat** in promotional credits. These credits are pooled at the workspace level, applied automatically, and expire on August 20. If your balance reaches zero or your promotional credits expire, Loops will pause unless an admin has enabled auto top-ups or purchased additional credits. Your workspace is only charged automatically if auto top-ups are enabled. Learn more about [AI Credits](https://linear.app/docs/ai-credits). ### FAQ[⁠](#faq) Clearly describe the intended outcome and any actions Linear Agent should avoid. For example: > Investigate the issue using the available context. Add a comment summarizing the likely cause and recommend the next action. Do not change the issue’s assignee or status. For best results: - Use Linear Agent Chat to help build your instructions (see Create a loop with Linear agent) - Describe the outcome, not only an action - Specify which context or connected tools Linear Agent should use - State which changes are permitted A loop can only use MCP connectors that are connected to your workspace, enabled for Linear Agent, and allowed by your workspace admins. Access also depends on the loop’s scope and permissions. Enable web access only when a loop needs information from external websites. A good fit is research on public information, like competitor announcements, documentation, or API references, where the loop does not need to send sensitive workspace content to external services. Enable this intentionally, since allowing external web access can increase the risk of exposing workspace data outside Linear. First, a workspace admin must enable Code Intelligence and configure code access for the workspace. Then, enable the [Code Intelligence permission](https://linear.app/settings/ai/code-intelligence) on the loop itself. First, a workspace admin must enable coding sessions and configure code access for the workspace. Then, enable the [Coding Sessions permission](https://linear.app/settings/ai/coding-sessions) on the loop itself. Workspace admins can review credits and usage via Settings under [AI & Agents > AI usage & credits](https://linear.app/settings/billing/usage) If your workspace runs out of AI credits, loops stop running until more credits are added. To troubleshoot, open the loop’s **Run history** to check recent runs and any visible failures. Common causes a loop run might fail include missing permissions, untrusted external sources, or your workspace running out of AI credits. To get a more detailed description of what went wrong, you can also ask Linear. Press ⌘/Ctrl + J while looking at the run history and ask for a detailed description of why the loop run failed. Right-click on the loop from either the workspace or team loop view and select **Enable** or **Disable.** Deleting a loop is permanent and cannot be undone. Consider disabling the loop instead if you may need to restore it in the future. --- ## Linear – Move work forward across teams and agents · 890 words Build, review and ship ![Artificial teammates. Natural collaboration.Linear is built for multiplayer work with AI. You can assign agents to any issue and mention them in comment threads, just like any other member of your team.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/344ddb1f-7bcb-4d44-9335-d142bc388500/f=auto,fit=scale-down,metadata=none) *Artificial teammates. Natural collaboration.Linear is built for multiplayer work with AI. You can assign agents to any issue and mention them in comment threads, just like any other member of your team.* ![Agents for every use case, at your commandChoose from a variety of AI agents and start delegating work, from code generation to other technical tasks. Or build your own agent.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/8d952e14-1f2d-43c0-3f44-85624539df00/f=auto,fit=scale-down,metadata=none) *Agents for every use case, at your commandChoose from a variety of AI agents and start delegating work, from code generation to other technical tasks. Or build your own agent.* ![Orchestrate issues at scaleDelegate multiple issues in paralleland monitor the agent’s progress.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/6179a227-d590-48c6-6b9a-38dd5b58f800/f=auto,fit=scale-down,metadata=none) *Orchestrate issues at scaleDelegate multiple issues in paralleland monitor the agent’s progress.* ![Go from issue to code instantlyOpen any issue directly in your AI coding tool of choice preloaded with full context and a custom prompt.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/8e9f511c-e657-409a-ef12-1f403924bb00/f=auto,fit=scale-down,metadata=none) *Go from issue to code instantlyOpen any issue directly in your AI coding tool of choice preloaded with full context and a custom prompt.* ![Backlog hygiene, automatedKeep your backlog clean and uncluttered with Linear’s auto-closing and auto-archiving features.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/ab3be882-47bb-4266-ad37-4623d725b900/f=auto,fit=scale-down,metadata=none) *Backlog hygiene, automatedKeep your backlog clean and uncluttered with Linear’s auto-closing and auto-archiving features.* ![Modern sprint planning, purpose-built for software teamsPlan work in clear, time-boxed cycles. Linear keeps upcoming cycles ready automatically, so your team can stay focused and maintain momentum.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/9574a995-e4c7-4cb3-166c-09de16fcee00/f=auto,fit=scale-down,metadata=none) *Modern sprint planning, purpose-built for software teamsPlan work in clear, time-boxed cycles. Linear keeps upcoming cycles ready automatically, so your team can stay focused and maintain momentum.* Auto-assign and updateAuto-assign issues and move them to a started status when you copy the git branch name Branch-specific rulesDefine custom workflow automations based on specific target branches Link and automate PRsAutomatically change issue status based on pull/merge request updates Auto-assign and updateAuto-assign issues and move them to a started status when you copy the git branch name Branch-specific rulesDefine custom workflow automations based on specific target branches PR review statusSee the reviewers and review states of your pull and merge requests directly in Linear Auto-assign and updateAuto-assign issues and move them to a started status when you copy the git branch name Link and automate PRsAutomatically change issue status based on pull/merge request updates Branch-specific rulesDefine custom workflow automations based on specific target branches PR review statusSee the reviewers and review states of your pull and merge requests directly in Linear Auto-assign and updateAuto-assign issues and move them to a started status when you copy the git branch name Branch-specific rulesDefine custom workflow automations based on specific target branches Link and automate PRsAutomatically change issue status based on pull/merge request updates Auto-assign and updateAuto-assign issues and move them to a started status when you copy the git branch name Branch-specific rulesDefine custom workflow automations based on specific target branches PR review statusSee the reviewers and review states of your pull and merge requests directly in Linear Auto-assign and updateAuto-assign issues and move them to a started status when you copy the git branch name Link and automate PRsAutomatically change issue status based on pull/merge request updates Branch-specific rulesDefine custom workflow automations based on specific target branches PR review statusSee the reviewers and review states of your pull and merge requests directly in Linear ![A fast and focused review experienceSee every review that needs your attention in one focused interface. Open diffs instantly, respond quickly, and keep your team unblocked.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/4ab9a069-8c54-41e8-c609-7dae71041e00/f=auto,fit=scale-down,metadata=none,width=2464) *A fast and focused review experienceSee every review that needs your attention in one focused interface. Open diffs instantly, respond quickly, and keep your team unblocked.* ![Review notifications you’ll actually seeNever miss a review request again. Every PR notification surfaces clearly in a focused inbox built for action.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/d231f84e-fea9-4a22-a3b5-840911b6c200/f=auto,fit=scale-down,metadata=none,width=800) *Review notifications you’ll actually seeNever miss a review request again. Every PR notification surfaces clearly in a focused inbox built for action.* ![Structural highlightingStrip away formatting-only edits to focus oncode changes, not the noise around them.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/61d9e8a9-82ec-4f58-91cc-7cacbf873500/f=auto,fit=scale-down,metadata=none) *Structural highlightingStrip away formatting-only edits to focus oncode changes, not the noise around them.* ![Iterate with agentsReview feedback, resolved at agent speed. Make changes from the diff with agents and watch updates appear inline.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/820ea50d-0737-47a9-cc2a-24a151ac9800/f=auto,fit=scale-down,metadata=none) *Iterate with agentsReview feedback, resolved at agent speed. Make changes from the diff with agents and watch updates appear inline.* ![Review code in contextEach diff is tied directly to the issue it resolves.No tab or tool switching required.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/4067463c-4db5-4746-6df1-b5f39b672300/f=auto,fit=scale-down,metadata=none) *Review code in contextEach diff is tied directly to the issue it resolves.No tab or tool switching required.* ![A clear path through complex changesLarge PRs are hard to review without a clear way in. Guided reviews walk you through changes in semantic order, separating out supporting changes and glue code.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/1a1250f1-ce3c-4854-a661-3a395db9cf00/f=auto,fit=scale-down,metadata=none,width=2464) *A clear path through complex changesLarge PRs are hard to review without a clear way in. Guided reviews walk you through changes in semantic order, separating out supporting changes and glue code.* ![Model how each team actually shipsCreate a release pipeline for every product and environment, whether continuously deployed or released on a schedule, and see every version live in one place.](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/0927e8e6-452f-4f82-1763-fa208759ff00/f=auto,fit=scale-down,metadata=none) *Model how each team actually shipsCreate a release pipeline for every product and environment, whether continuously deployed or released on a schedule, and see every version live in one place.* --- ## The coding agent behind 60% of Ramp’s merged PRs · 964 words Ramp adopted Linear when the company was just five people. Over 1,500 employees later, with their entire product workflow running through Linear, Zach Bruggeman (an engineer at Ramp) wanted to see what else it could power. He’d been watching AI agents grow more capable, and along with a couple of his colleagues, spent two weeks building a background coding agent tightly integrated into the workflows Ramp already ran through Linear. FoundedNew York, 2019 SwitchedOctober 2019 Company size1,600 Businesses shuttle [many billions of dollars](https://support.ramp.com/hc/en-us/articles/4417685250195-Ramp-overview) along the lines of code in Ramp’s codebase each year. Yet today, [over 60 percent of all merged PRs](https://x.com/rahulgs/status/2020984194038628832?s=20) at the company have been authored by Inspect, Ramp’s internal coding agent; demonstrating how an organization operating in a sensitive regulatory environment can scale AI adoption responsibly. #### How Ramp built a coding agent for its own stack[⁠](#how-ramp-built-a-coding-agent-for-its-own-stack) Inspect is a background coding agent Ramp built themselves. It writes code and verifies the output using the same context and tools a Ramp engineer would. For backend tasks, Inspect can run tests, review telemetry, and query feature flags; and for frontend work, it can visually verify changes and return screenshots or live previews. Each session runs in a sandboxed environment configured with the infrastructure Ramp engineers already use. Inspect began as a casual idea shared by Zach and two of his colleagues, [Jason Quense](https://x.com/monasticpanic) and [Rahul Sengottuvelu](https://x.com/rahulgs). Instead of defaulting to one of the many coding agents already on the market, they decided to [build an agent](https://builders.ramp.com/post/why-we-built-our-background-agent) optimized for Ramp’s internal workflows. “It’s a really tight integration with our development lifecycle and our tooling,” Zach says. Being an internal tool, the team could be precise about how the agent connected to Ramp’s other systems. As Zach put it, “we know our one API key for _this_” and “we know exactly what the schema of _these_ logs is going to be.” This helped them build the agent faster, while also improving its performance because there are fewer layers of abstraction between Inspect and the company’s tooling. One of the most important of those tools is Linear. Ramp runs its entire product development process through Linear, which means the platform holds a structured record of everything associated with building product at the company. The specs teams write, the customer feedback they collect, roadmaps they plan against, and the relationships between all of it. By integrating Inspect through Linear’s [API for agents](https://linear.app/developers/agents), the Ramp team gave the agent native access to that entire layer of context. And because Inspect can also reach into Ramp’s codebase, internal documentation, and other systems, the combination means the agent operates with something close to the full picture a well-informed engineer would have. When someone asks Inspect to fix a bug or think through a feature idea, it can trace the thread from a customer request through a product spec to the relevant code, rather than working from a narrow prompt. Zach described the connection as a “natural fit” noting that the API was especially well-suited to background agent workflows and has become one of the more popular integrations internally. Building the integration was also fast. Zach says he prompted a coding agent with [Linear’s docs](https://linear.app/developers/agents), added a couple of rough pointers, and it got the integration “90 percent of the way there in about 30 minutes.” #### How Inspect scaled AI workflows at Ramp[⁠](#how-inspect-scaled-ai-workflows-at-ramp) Inspect gained traction inside Ramp through multiple entry points, including a web interface, a Chrome extension, and, most potently, a Slack integration. Slack brought Inspect out into the open, and when people saw the agent in action, they were more likely to try it themselves; a pattern we tracked when [Linear’s Slack integration](https://linear.app/changelog/2025-10-23-linear-agent-for-slack) was introduced. The visibility also helps engage non-engineering teams like Design, Product Management, Product Ops, and Data. Zach’s premise is that people in these roles already have the context to guide good product decisions, and Inspect allows them to apply that expertise without needing to start by going through Engineering. For example, while reworking a dashboard panel on Ramp’s web app, a designer might start in a Figma file and use Inspect to get the change most of the way there, before linking the session to an engineer. As a next step, instead of bothering to download code locally, Engineering can easily step in and bring the redesign live. Inspect was built to be “multiplayer” to support exactly this kind of handoff. If someone starts a session with the agent, they can share a link to it with their teammate for further input. Alternatively, if Inspect was being directed from Slack, others can jump into the same thread and continue the work there. That shared workflow is becoming one of Inspect’s most prominent patterns of use. The result is that non-technical teams can carry ideas further into production on their own, leaving engineers to review work that’s already most of the way there. This model works in part because Ramp built [shared rails for AI adoption](https://x.com/geoffintech/status/2042002590758572377#:~:text=4.%20Build%20from%20the%20center%2C%20drive%20from%20the%20spokes). A central team defines how agents can access internal systems and what they’re allowed to do, which makes it easier (and safer) for functional teams to build their own custom automations safely. #### Software development’s next constraint[⁠](#software-development's-next-constraint) Inspect has accelerated Ramp’s culture of acting promptly on product feedback, instead of letting small issues languish in the backlog. As Zach describes it, feedback comes in through Slack, someone replies with “@Inspect, fix this,” a PR opens, and once approved, the change ships. That speed has shifted the bottleneck from writing code to reviewing it. A new challenge any company using coding agents at scale will face. Ramp is exploring ways new tooling can help them overcome this constraint and move even faster. Zach says he’s paying close attention to how companies [like Linear](https://linear.app/diffs) are shaping the review process. --- ## MCP server – Linear Docs · 2032 words ![Abstract image of a drive with Linear's logo and the words "Remote MCP server"](https://webassets.linear.app/images/ornj730p/production/54373418b3cb31208f112cd8137d7dd825d1b7c0-3600x1800.png?w=1440&q=95&auto=format&dpr=2) The Model Context Protocol (MCP) server provides a standardized interface that allows any compatible AI model or agent to access your Linear data in a simple and secure way. Connect to our MCP server natively in Claude, Cursor, and other clients or use the [`mcp-remote`](https://github.com/geelen/mcp-remote) module for backwards compatibility with clients that do not support remote MCP. Linear’s MCP server follows the authenticated remote [MCP spec](https://modelcontextprotocol.io/specification/2025-03-26), so the server is centrally hosted and managed. The Linear MCP server has tools available for finding, creating, and updating objects in Linear like issues, projects, and comments — with more functionality on the way, and [feedback](https://linear.app/contact/support) on its functionality is welcomed. For help getting started after setup, see some of our [example prompts](https://linear.app/docs/mcp#common-use-cases). ### Setup[⁠](#setup) #### General[⁠](#general) Our MCP server uses Streamable HTTP as the primary transport, accessible at the following address. The interactive setup flow uses OAuth 2.1 with dynamic client registration. You can also authenticate directly with a bearer token or Linear API key — see the FAQ for details. Read-write access is provided through `https://mcp.linear.app/mcp` by default. For read-only access, you have two options: - Connect to `https://mcp.linear.app/mcp/readonly`, which only ever exposes read tools. - Use the standard `/mcp` endpoint, but only request the `read` OAuth scope. Clients that request `read` are granted read-only access, and the underlying token can’t reach write APIs. For instructions for specific clients, read on. Dedicated setup pages are also available for [Claude](https://linear.app/integrations/claude), [Cursor](https://linear.app/integrations/cursor-mcp), [VS Code](https://linear.app/integrations/vs-code-mcp), [Windsurf](https://linear.app/integrations/windsurf), and [Zed](https://linear.app/integrations/zed/). #### Claude[⁠](#claude) **Team, Enterprise (Claude.ai)** Navigate to the [connectors](https://claude.ai/customize/connectors) page and connect Linear. **Free, Pro (Claude desktop)** From Claude settings > Connectors you can add the Linear connector. If you use Okta, first configure SAML for Linear using [Okta’s OIN](https://linear.app/docs/saml-and-access-control#configure). Then enable **MCP enterprise managed authentication** from your Okta identity provider settings in Linear. Lastly, enter the Okta [**Issuer URI**](https://developer.okta.com/docs/guides/sign-into-spa-redirect/-/main/#find-your-config-values) for the authorization server used for MCP authentication, for example: ``` https://your-org.okta.com ``` This allows supported external MCP clients such as Claude to authenticate users automatically using your Okta-managed access policies. #### Claude Code[⁠](#claude-code) ``` claude mcp add --transport http linear-server https://mcp.linear.app/mcp ``` Then run `/mcp` once you’ve opened a Claude Code session to go through the authentication flow. #### Codex[⁠](#codex) The setup steps for the MCP server are the same regardless of whether you use the IDE Extension or the CLI since the configuration is shared. **Configuration via CLI:** Run the following command in Terminal: ``` codex mcp add linear --url https://mcp.linear.app/mcp ``` This will automatically prompt you to log in with your Linear account and connect it to your Codex. **Note**: If this is the first time you are using an MCP in Codex you will need to enable the `rmcp` feature for this to work. Add the following into your `~/.codex/config.toml`: ``` [features] experimental_use_rmcp_client = true ``` **Configuration through environment variables:** 1. Open the `~/.codex/config.toml` file in your preferred editor 2. Add the following: ``` [features] experimental_use_rmcp_client = true [mcp_servers.linear] url = "https://mcp.linear.app/mcp" ``` Run `codex mcp login linear` to move through the authentication flow. #### Cursor[⁠](#cursor) To add the MCP to Cursor, you can install by clicking [here](cursor://anysphere.cursor-deeplink/mcp/install?name=Linear&config=eyJ1cmwiOiJodHRwczovL21jcC5saW5lYXIuYXBwL21jcCJ9), or searching for Linear from Cursor’s [MCP tools page](https://cursor.com/docs/context/mcp/directory). ![C](https://webassets.linear.app/images/ornj730p/production/7ff4a8f3f3f95e1a25a241c49f5d46c66e17b80a-760x343.png?w=1440&q=95&auto=format&dpr=2) #### Jules[⁠](#jules) - In Linear, go to **Settings** > **Account** > **[Security & Access](https://linear.app/settings/account/security)** - Generate a new API key and copy it somewhere secure - Now in Jules, go to [**MCP Settings**](https://jules.google.com/settings/mcp) - Select **Connect** on the Linear server and paste your API key #### Visual Studio Code[⁠](#visual-studio-code) ``` { "mcpServers": { "linear": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"] } } } ``` 1. CTRL/CMD P and search for **MCP: Add Server**. 2. Select **Command (stdio)** 3. Enter the following configuration, and hit enter. `npx mcp-remote https://mcp.linear.app/mcp` 1. Enter the name **Linear** and hit enter. 2. Activate the server using **MCP: List Servers** and selecting **Linear**, and selecting **Start Server**. #### v0 by Vercel[⁠](#v0-by-vercel) To add the MCP to v0, you can install from the [connections](https://v0.app/chat/settings/mcp-connections) page. #### Windsurf[⁠](#windsurf) 1. CTRL/CMD , to open Windsurf settings. 2. Under Scroll to Cascade -> MCP servers 3. Select **Add Server -> Add custom server** 4. Add the following: ``` { "mcpServers": { "linear": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"] } } } ``` #### Zed[⁠](#zed) 1. CMD , to open Zed settings. 2. Add the following: ``` { "context_servers": { "linear": { "source": "custom", "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"], "env": {} } } } ``` #### Others[⁠](#others) Hundreds of other tools now support MCP servers, you can configure them to use Linear’s MCP server with the following settings: - **Command**: `npx` - **Arguments**: `-y mcp-remote https://mcp.linear.app/mcp` - **Environment**: None ### Common use cases[⁠](#common-use-cases) The MCP server lets you work with your Linear data from any compatible AI client. To help get started with the Linear MCP tooling, feel free to copy some example prompts into your own client to explore what’s possible. **Use case** Use this workflow to turn a planning document into a structured Linear project, with issues, milestones, and relationships that make the work easier to organize and track. **Example prompt** You are helping turn a planning document into a well-structured Linear project. Read the document, create a project that reflects its objective, scope, and timeline, then create the issues needed to represent the work with clear titles and populated descriptions. Each issue should make the work actionable by capturing the problem, the goal, the proposed approach when one is provided, and any open questions that remain. Organize issues into milestones when the document clearly implies phases, deliverables, or checkpoints, and add related relationships where issues are meaningfully connected, but do not invent dependencies or structure that the source material does not support. If the document is too vague or ambiguous to produce high-quality work, flag the uncertainty and return a proposed outline for review instead of guessing. Before creating anything, show the proposed project, milestones, issues, relationships, and any decisions that need review. **Use case** Use this workflow to turn standup notes into clear updates on the relevant Linear issues, so progress and blockers stay documented without extra manual work. **Example prompt** You are helping turn live standup notes into updates on existing Linear issues. Read the notes, identify any issues mentioned by ID, title, owner, or clear surrounding context, and match each note only when the connection is strong. For every confident match, add a concise comment that captures what changed, the current status or blocker, and the next step if one is mentioned. Keep each comment factual and specific to that issue. If a note is ambiguous or you cannot confidently match it, do not guess or create work from it; return it as unmatched with a short explanation. Before applying any changes, show which issues you plan to update and the exact comment you would post to each one, then apply the comments and separately list any notes you skipped. Standup notes: `[Paste the notes’ raw text here or attach the transcript as a document]` **Use case** Use this workflow to investigate a reported bug from an existing Linear issue, identify a likely root cause, and capture the findings back on the issue for the team. **Example prompt** You are helping investigate a bug that is already tracked in Linear. Start from the referenced issue, use its description and any linked context as the starting point, and search for the most likely root cause by following relevant technical, product, or workflow clues. Focus on producing a clear, evidence-based explanation of what is happening, what changed if that is relevant, and what the likely cause appears to be. Do not guess when the evidence is weak; instead, call out uncertainty and explain what additional context would help. Once you have enough information, write a concise summary of the findings and post that summary as a comment on the issue so the investigation is documented for the team. Linear issue to investigate: `[LIN-123]` **Use case** Use this workflow to summarize what a team completed during a specific cycle or timeframe, making it easier to review progress and communicate outcomes. **Example prompt** You are helping summarize work completed during a specific Linear cycle or timeframe. Identify the most recently completed cycle to analyze for the selected team or teams, gather the relevant issues, and produce a concise summary of what was accomplished. Focus on the work that was actually completed, the main themes across that work, and any notable patterns such as bugs resolved, projects advanced, or areas of concentrated effort. Keep the summary clear and useful for sharing with others, and avoid overstating progress where the underlying work is still in flight. Team identifiers: `[LIN, FEA]` **Use case** Use this workflow to build a historical timeline of work in Linear around a topic, so teams can understand how a project, incident, or theme evolved over time. **Example prompt** You are helping document the history of work in Linear around a specific topic. Gather the relevant issues and projects connected to that topic, review their historical activity, and produce a timeline that shows the key developments in chronological order. Focus on meaningful milestones such as when work was created, when direction changed, when major decisions or updates were recorded, and when important work was completed. Keep the timeline factual and grounded in the underlying activity, and call out any gaps or ambiguity rather than inferring events that are not clearly supported. Topic: `[Insert a specific topic from your workspace]` **Use case** Use this workflow to turn an initial idea into a reviewed implementation plan, then create the corresponding Linear work and delegate execution to the right people or agents. **Example prompt** You are helping plan and structure a development effort in Linear. Start by designing an approach based on the provided context, with enough detail to explain the proposed solution, major workstreams, and any important tradeoffs or open questions. Treat that initial plan as a draft that can be reviewed and edited before any work is created. Once the plan is approved, create a parent issue that captures the overall goal and create sub-issues for the concrete pieces of work needed to execute it. Keep the breakdown clear and actionable, and assign or delegate work only when the requested owners or agents are explicitly specified. Context: `[Insert enough context to help orient the agent]` ### FAQ[⁠](#faq) Enter the following in the Terminal to clear saved auth info: `rm -rf ~/.mcp-auth` then try again to connect. Additionally you may need to update to a newer version of node if required. The Linear MCP server authenticates each session via OAuth. Because reconnecting alone does not switch the workspace within an existing auth session, each workspace needs its own separate authentication context. If your client or the `mcp-remote` module supports a configuration directory (for example via `MCP_REMOTE_CONFIG_DIR`), point each workspace to a different path: ``` MCP_REMOTE_CONFIG_DIR=~/.mcp-auth/workspace-a npx mcp-remote https://mcp.linear.app/mcp MCP_REMOTE_CONFIG_DIR=~/.mcp-auth/workspace-b npx mcp-remote https://mcp.linear.app/mcp ``` Authenticate each configuration separately. For clients that manage their own auth storage, check the client’s documentation for workspace-switching options. The MCP server supports passing OAuth token and API keys directly in the `Authorization: Bearer ` header instead of using the interactive authentication flow. You can use this to interact with the MCP server as an `app` user, provide read-only access through a restricted API key, or integrate with an existing Linear OAuth application without an extra authentication hop. For an alternative read-only approach with your own API key, create a Linear API key with only the `Read` permission enabled. The SSE endpoint at `https://mcp.linear.app/sse` is a deprecated fallback for clients that do not support Streamable HTTP. For all new setups, use the primary Streamable HTTP endpoint at `https://mcp.linear.app/mcp`. Remote MCP connections can occasionally need a reconnect in some client setups. Try disconnecting and reconnecting the server from your client’s MCP settings. This is a routine client-side reset and does not affect your Linear data or authentication session. The default connection uses Streamable HTTP at `https://mcp.linear.app/mcp`. If that does not work in WSL, use this SSE fallback instead (`/sse` is a legacy path for clients that do not support Streamable HTTP): `{"mcpServers": {"linear": {"command": "wsl","args": ["npx","-y","mcp-remote","[https://mcp.linear.app/sse](https://mcp.linear.app/sse)","--transport sse-only"]}}}` --- ## AI Agents – Linear Docs · 754 words Build and deploy AI agents that work alongside your team ![list of agents in assignee menu, Charlie and ChatPRD are visible](https://webassets.linear.app/images/ornj730p/production/68c955d01e0e45b23747e8cd7362b018b06a6655-2880x1768.png?w=1440&q=95&auto=format&dpr=2) ### Overview[⁠](#overview) Agents, also known as “app users”, behave similar to other users in a workspace. Depending on the permissions granted during installation, agents can be mentioned, delegated issues through assignment, create and reply to comments, and collaborate on projects and documents. App users are installed and managed by workspace admins. Agents are not traditional assignees. Assigning an issue to an agent delegates the issue to that agent while the human teammate remains the primary assignee and owner — explore [Assign and delegate issues](https://linear.app/docs/assigning-issues) to learn more. ### Adding Agents[⁠](#adding-agents) Workspace admins can install agents by following the setup instructions provided by the agent developer. Find available agents in the [Integrations Directory](https://linear.app/integrations/agents). During installation, you’ll be prompted to choose which teams the agent has access to. ![Installing the codegen agent into Linear permissions modal](https://webassets.linear.app/images/ornj730p/production/9a11b2deb2fd1f6b5649f00ebaa928124f061099-1292x1019.png?w=1440&q=95&auto=format&dpr=2) *Example of installing an agent into Linear* Once installed, any user with access to the selected teams can interact with the agent. Admins can also review agent access from the [AI & Agents](https://linear.app/settings/ai) settings in the _Installed Agents_ section. ### Using Agents in Linear[⁠](#using-agents-in-linear) Agents are designed to work seamlessly alongside human teammates: - **Delegate issues to them** by assigning the issue to the agent. This triggers the agent to take action based on its programmed behavior. - The human assignee remains responsible for the issue, even after delegation to an agent. - **@mention them** in comments or descriptions to trigger their functions. If you’re not sure how to interact or what they’re able to help with, you can try @mentioning the agent to ask for help. ### Guiding Agents[⁠](#guiding-agents) Agent guidance lets you provide instructions that agents will automatically receive when they work on issues in your workspace. ![Screenshot of the Additional guidance panel showing repository instructions for agents](https://webassets.linear.app/images/ornj730p/production/d9cb1836286c78822dddee0e6e9ec3c67a1c10a9-1570x788.png?w=1440&q=95&auto=format&dpr=2) Agent guidance provides instructions that help agents work within your team’s conventions. Guidance can specify which repository to use for certain code changes, how to reference issues in commits or pull requests, and what review process to follow, so agents align with your existing workflows. **Note:** All guidance is passed to the agent, but how it is interpreted or applied depends on the specific agent integration. If an agent doesn’t appear to follow the guidance, please share feedback with the team responsible for that agent directly. Workspace guidance applies across the entire organization, while team-specific guidance can be used to include additional instructions unique to that team. When both exist, team guidance takes priority. Guidance is authored in a markdown editor with full history, so instructions can be formatted clearly and reviewed or updated over time. To edit your workspace-level agent guidance, navigate to [_Settings_ > _Agents_ > _Additional guidance_](https://linear.app/settings/agents). For team-level guidance, navigate into your parent or sub-team’s settings > _Agents_ > _Additional guidance_. Both workspace and team level guidance may not exist in all agent contexts. ### Viewing Agent Activity[⁠](#viewing-agent-activity) You can track what an agent has done in the same ways you track other teammates: - **Agent** [**user pages**](https://linear.app/docs/user-views) show issue activity and contributions. - In the **My issues** view, issues that you’ve delegated to agents will still appear—so you maintain visibility and control over the work in progress. - **Custom views** filtered by **Delegate** to monitor agent involvement on specific types of issues or workflows. - Use **Insights** sliced or segmented by **Delegate** to measure how much work is being directed to and handled by agents. ### Building Your Own Agent[⁠](#building-your-own-agent) Developers can build custom agents using Linear’s developer platform. Documentation on agent APIs, authentication, and behavior can be found in our [Developer Docs](https://linear.app/developers/agents). ### FAQs[⁠](#faqs) Agents are not counted as billable seats in Linear. The services that provide the agent may have their own pricing structure, and you should refer to their documentation before installing. Linear does not train on customer’s data. We use models from common model providers, a complete list is available in our [DPA](https://linear.app/dpa). Agents themselves would be 3rd party integrations approved by your workspace, in which case we can’t speak to how the agent provider operates and you’d have to refer to the agent service provider. Agents cannot sign in to the app, access admin functionality or manage users. In the event that you have a member on your workspace with the same name as an Agent, the Agent’s username will simply append a number at the end to keep it unique. For example, Charlie would become Charlie1. ### [⁠](#) --- ## Changelog – Linear · 9340 words August 20, 2026 [ ### Coding sessions: environments, browser use, and updated pricing ](https://linear.app/changelog/2026-08-20-coding-environments) Elapsed00:00 Remaining time unknown Linear Agent can now set up, run, and test your code before returning its work. That means fewer handoffs and changes that are further along when they come back to you. We’re also introducing lower, more transparent pricing, making AI credit usage easier to understand and control. ### **Configurable environments**[⁠](#configurable-environments) Coding sessions now automatically adapt to each codebase’s configuration, with broader out-of-the-box support for Python, Ruby, Go, and more. During a session, Linear detects and installs the toolchains and dependencies it needs to complete the task. Teams can go further by pinning runtime versions, adding setup scripts, and defining environment variables. To get started, create an environment in [settings](https://linear.app/settings/ai/coding-sessions). Visit the [docs](https://linear.app/docs/coding-sessions) for more details. ### Browser testing[⁠](#browser-testing) Once the application is running, Linear Agent tests its work where users experience it: in the browser. The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots, making visual changes easier to review alongside the code. Browser testing can catch broken interactions and visual regressions that code review alone might miss. If the agent finds a problem, it can make a fix, rerun the test, and return the work with that validation complete. ![Screenshot of Linear UI](https://webassets.linear.app/images/ornj730p/production/4949ed5cd70ac79c7cb914eb65373f5e494af720-3600x2160.png?q=95&auto=format&dpr=2) ### Transparent pricing[⁠](#transparent-pricing) As coding sessions take on more work, costs need to be easy to understand and easy to control. Starting today, coding sessions use a lower-cost pricing model with two components: - **Model usage:** Tokens are charged at the provider’s published rates, with no markup - **Sandbox runtime:** Charged at $0.25 per 20-minute block Together, model usage and runtime determine the AI credit cost of a session. The usage dashboard shows the breakdown, along with token usage and cost by model. Admins can also set workspace-wide and per-user spend limits that reset daily, weekly, or monthly. When a limit is reached, additional AI credit usage is paused until the limit resets or an admin increases it. Learn more about AI credits in the [docs](https://linear.app/docs/ai-credits). - Agents Fixed an issue where Linear couldn’t find or assign a future cycle when referenced by its number (e.g. “Cycle 13”) in Slack and comments - Android Fixed read AI conversations appearing bold in the conversation picker - Desktop Fixed search and create issue buttons in the sidebar not responding to clicks at narrow window sizes - Diffs Fixed merge queue duration tooltips appearing stuck - Diffs Fixed guide sections with a lot of files in them not being scrollable - Diffs Fixed Linear guest users with a connected GitHub account being able to edit Diff title and description if they have write access to that PR on GitHub - Diffs Removed hover underlines from GitHub code embed header links, kept their link cursors when focused, and added external-link indicators to file names - Diffs Fixed repeated review cache errors when IndexedDB is unavailable - Asks Added a per-channel Asks setting that posts a message mentioning the new assignee in the synced Slack thread when an Ask is assigned - Authentication Improved pending SAML domain verification from 24 hours to seven days - Diffs Improved meaningful change count on PR tooltips as well - IOS Improved error messages for unsupported media formats - Issues Added the full issue copy menu to the issue header URL button - Team Home Initiative documents pinned to a team’s overview now also appear in the team’s documents tab - Views Added ability to subscribe to events in project views and receive notifications in Inbox or Slack - Issues Open a GitHub-synced issue in GitHub with OG - Issues Fixed Cmd/CtrlUp/Down scrolling to the top or bottom of an issue after editing its title or description August 13, 2026 [ ### Team initiatives ](https://linear.app/changelog/2026-08-13-team-initiatives) ![Initiatives view showing active company goals, nested team initiatives, owners, lead teams, project progress, and health.](https://webassets.linear.app/images/ornj730p/production/4a9c8a92201a695eeaa5f3a6fccb507adac9c661-3600x2080.png?q=95&auto=format&dpr=2) Initiatives are Linear’s way to manage product strategy and high-level planning across projects. Strategy may start at the company level, but teams carry it forward. You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broader direction. For work that requires tighter access, initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects, audits, and other restricted work. Learn more about initiatives in the [docs](https://linear.app/docs/initiatives). Linear’s MCP now supports managing employee access through your existing Okta-managed identity. When employees connect from a supported Anthropic agent, Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually. Available to Enterprise workspaces with Okta SAML configured. Learn more in the [docs](https://linear.app/docs/mcp#enterprise-managed-authorization). - Agent Fixed agent sometimes not showing a progress indicator - Agent Fixed Linear Agent sometimes claiming a Slack thread synced when it did not - Comments Prevented document comment threads from shifting away from their referenced text when content changes size - Cycles Fixed new cycle names with quarter or half-year labels not incrementing correctly - Cycles Fixed fast issue creation while viewing completed cycles - Diffs Fixed code review discussions crashing when a file path is missing - Diffs Fixed comment links not opening the associated thread - Diffs Fixed authored pull requests appearing in “To review” after commenting - Diffs Fixed closing an already-closed GitHub pull request failing to remove it from review lists - Diffs Fixed stale PR Guides not refreshing after a pull request update - Editor Added support for comments on Mermaid diagrams - GitHub Fixed closing an abandoned draft pull request changing the status of an issue already marked Done or Canceled - GitLab Fixed merge requests from deleted users failing to process - Integrations Fixed disconnecting a personal Notion account opening Notion instead of removing the connection - Integrations Renaming an OAuth application now updates the name shown in the activity of issues it creates - Issues Fixed imported recurring issues missing their recurring-series link in issue history - Issues Fixed drag-and-drop for sub-issues in views sorted by status, title, or due date - Issues Fixed “Copy as” prompt copying a parent issue instead of the selected sub-issue - Notifications Fixed duplicate notifications for GitHub review requests - Notifications Fixed members being unable to disable Slack alerts for shared custom views - Projects Fixed blocking and blocked-by relationships appearing in the wrong direction in project activity - Projects Fixed project and initiative update reminders being sent when an update was already posted on the previous business day - Search Improved exact user name matches in search results - Triage Added GitHub usernames to GitHub-sourced issues in triage - Agent Linear Agent can now update releases - Billing Added the ability to remove a previously set tax ID - Coding sessions Added GPT-5.6 Luna as a model option - Cycles Added an explanation of cycle success to the tooltip - Diffs Added a branch-status widget showing whether a branch is up to date, behind, or has conflicts - Diffs Grouped agent and bot review comments under Agents & Bots - Diffs Made structural diff highlighting the default - Diffs Showed merge-queue time on pull request hover - Editor Added support for mentioning pull requests from the editor mention picker - Editor Pressing Enter at the end of an issue or document title now starts a new line at the top of the content below it - Git Updated `relates to` and `related to` magic words to mark pull requests as related rather than contributing - Importer Added an option to skip workspace-level labels and templates during Linear-to-Linear imports - Integrations Improved the channel connection labels across Slack and Microsoft Teams menus - IOS We now indicate progress while importing photo library attachments for comments - Loops Made the **Disabled** badge interactive so loops can be re-enabled directly - Projects Added project milestone agent widgets on iOS - Added `subscribers` field on `Document` - Added a subscription for user settings updates - Teams Fixed CtrlShift1–9 shortcuts for opening team home pages July 30, 2026 [ ### Coding sessions on mobile ](https://linear.app/changelog/2026-07-30-coding-sessions-on-mobile) Elapsed00:00 Remaining time unknown Your coding session doesn’t have to stop when you leave your desk. Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent. Open any diff and switch to the Changes tab to inspect the code. When you spot something to change, tap the relevant line to add it to your message to steer the coding session in the direction you want. We’ve also added section under My Issues → Assigned for your delegated issues. It shows the status of each coding session, and gives you a quick way back into active work. ![ My Issues → Assigned showing delegated issues on iOS mobile app](https://webassets.linear.app/images/ornj730p/production/de5bfa7b44714eef4e54f0bb4c6bfab6841eb716-3600x2360.png?q=95&auto=format&dpr=2) Download the Linear mobile app for [iOS](https://apps.apple.com/us/app/linear-mobile/id1645587184) and [Android](https://play.google.com/store/apps/details?id=app.linear&hl=en_US&pli=1). ### Guided Reviews are now generally available[⁠](#guided-reviews-are-now-generally-available) [Guided Reviews](https://linear.app/changelog/2026-05-27-linear-diffs#guided-reviews-\(beta\)) break diffs into focused sections with explainers on what changed and why. As part of general availability, they are now generated for larger pull requests, with a bigger context window and better latency. Guided Reviews are available on Business and Enterprise plans at no additional cost. ![Guided Review for Diff on Refactor notification model and capture parse failures](https://webassets.linear.app/images/ornj730p/production/0bae3de361f646dc692b226b236f9f7e1ae19224-3600x2200.png?q=95&auto=format&dpr=2) ### Support for GitHub teams in reviews[⁠](#support-for-github-teams-in-reviews) You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox. Learn more in the [docs](https://linear.app/docs/diffs#notifications). ![Diff with Frontend team tagged as reviewer](https://webassets.linear.app/images/ornj730p/production/f2560c920ea56c0a8f04279cc509c27818c76ab4-3600x1942.png?q=95&auto=format&dpr=2) ### Signed commits for coding sessions[⁠](#signed-commits-for-coding-sessions) Coding sessions now support signed commits. Add your SSH or GPG key in [Settings](https://linear.app/settings/account/security) to enable signing. Workspace admins can also require users to upload a signing key before using coding sessions. ### GitHub Copilot for Linear[⁠](#github-copilot-for-linear) GitHub Copilot users can assign issues directly to Copilot’s cloud agent from Linear. Copilot uses the issue context to work in its own development environment, open draft pull requests, and update the issue as it makes progress. Choose model and agent settings, set the base and working branches, then steer ongoing work through comments in Linear. To get started, install [GitHub Copilot for Linear](https://linear.app/integrations/github-copilot), or read the [GitHub announcement](https://github.blog/changelog/2026-07-23-copilot-cloud-agent-for-linear-is-now-generally-available/) for more details. - Agents Queued agent messages now display readable text in previews instead of raw markup - API Fixed issue SLA sort to order by the displayed SLA bucket (Breached / High / Medium / Low / Achieved / Failed) instead of raw `slaBreachesAt`, so mobile lists no longer show repeated SLA sections - Comments Inline images no longer appear too large in iOS comments - Diffs Pull request reviews no longer unexpectedly open an inline comment draft when the revision changes - Diffs Dismissed issue suggestions no longer reappear on pull requests - GitHub Pull request events now update issue statuses when a Git automation branch pattern contains unsupported regex syntax - Inbox Fixed new project and initiative update notifications appearing as separate inbox entries for the same parent - Integrations GitHub Enterprise Server setup no longer gets stuck on “Verifying installation” after the Linear app is created - Integrations Prevented Slack Asks from responding to unmentioned thread messages after creating an Ask - IOS File, image, and video attachments in document comments now open when tapped, and attachment cards have better contrast in the comments drawer - Issues Issue boards now show an error instead of an empty state when too many issues match - Reviews Structural diffs no longer mark entire reformatted statements as changed when only part of the statement changed - Reviews Resolving a review thread that no longer exists in GitHub now shows a clear message instead of a generic error - Search Searching for a GitHub URL now finds issues that reference the pull request - Slack Fixed Slack review request notifications sometimes showing the wrong person as the requester - Slack Fixed pasting a project milestone link into Slack now previewing that milestone instead of another milestone from the same project - Teams Fixed internal custom view and dashboard links in Team Home displaying generic labels or icons - Triage “Copy as prompt” no longer moves issues out of triage - Diffs Diffs linked as `Related` no longer change the status of the issue - Diffs AI can now generate a Linear issue from a pull request or suggest an existing issue to link - Diffs Inline feedback can now be sent to the Linear Agent, added to a review, or posted to the diff - Diffs New agent sessions can now be started from any pull request using the Agent panel - Diffs TypeScript and JavaScript regular expressions can now be tested directly from the file where they’re introduced - Diffs Pull requests now show the number of meaningful changes, excluding tests and documentation - Diffs Improved Slack notifications for a pull request removed from the merge queue to include the reason it was removed - Editor Updated the keyboard shortcut cheat sheet to show Cmd/CtrlEnter for toggling checklist items - Importers It is now possible to import issues into a sub-team if it doesn’t inherit statuses from its parent team - Issues You can now restore an archived or deleted issue from the iOS app - Loops Improved the “Authenticated email intake” trusted source by renaming it to “Email intake” and explaining when an email is treated as trusted - Loops Added ability for Loops to send user notification - Zendesk Improved the Zendesk integration to allow connection using an agent role instead of an end-user role - Added Zapier to the built-in MCP connector directory - Editor Toggle a checklist item with Cmd/CtrlEnter when the cursor is inside it. Hold Shift to also toggle nested items - Search Escape now clears the search input while keeping the current results, then dismisses search when the input is empty - Triage Triage keyboard shortcuts now follow the order of the actions: `1` accepts, `2` declines, `3` marks as duplicate July 23, 2026 [ ### Text attribution and agent-assisted editing ](https://linear.app/changelog/2026-07-23-agent-assisted-editing) ![a document and an agent panel showing the prompt to edit ](https://webassets.linear.app/images/ornj730p/production/15b9a90d9ef28e617836383f0b295536c437b4b1-3600x2080.png?q=95&auto=format&dpr=2) Documents and project descriptions are critical context for your teams and agents. You can now edit text with [Linear Agent](https://linear.app/docs/linear-agent), and use [Loops](https://linear.app/docs/loops) to keep docs and project descriptions up-to-date. Author name indicators let you check if text was written by a colleague or added by a loop. When editing, changes you make through Linear Agent highlight separately so they’re easy to review. If you need to revert to an earlier version, restore to any previous checkpoint from version history. Show author names or open version history from the ⌘/Ctrl + K menu, or in document display options. Learn more in our [documentation](https://linear.app/docs/project-documents#edit-documents). The issue sidebar now closely integrates issue properties with the main content. We’ve pinned Diffs to the top of this panel so you can access the issue’s pull requests from anywhere on the page. ![New issue sidebar with diffs at the top](https://webassets.linear.app/images/ornj730p/production/fdbe518ba5882edab1681f7410f9af78716021f2-3600x2058.png?q=95&auto=format&dpr=2) - Asks Fixed issues created through Slack Asks ignoring a chosen template’s default status - Comments The resolved comments menu no longer appears when there are no resolved comments - Diffs Submit review flyouts now properly close when clicking outside them - GitHub Prevented revert pull requests from reopening issues linked to another GitHub repository - GitHub Fixed linking GitHub pull requests to issues via pasted URLs. - Initiatives Fixed oversized initiative titles - Integrations Fixed a bug where removing a linked GitHub pull request disconnecting GitHub issue sync - Integrations Fixed Slack project channel setup retrying after a project was deleted or archived - Settings Fixed IP restrictions not appearing when searching for “IP” in settings - Slack Fixed truncated issue summaries in Slack unfurls - Views Fixed view filters (like Cmd/Ctrl F filtering) resetting when navigating to an item in a split view list - Editor Added Backspace navigation from empty issue descriptions and document bodies back to the title - Issues Improved issue composer to suggest templates as a quick suggestion, surfaced before other suggestions because they apply a bundle of issue properties - Projects Added a way to view a project’s issues filtered by a specific milestone from the project overview on iOS - Triage Added triage responsibility to the triage screen on iOS, showing who is responsible for incoming issues and letting you manage the action and responsible members - Diffs “Quick to review” now shows up for slightly larger PRs and also appears for the author of the PR - Added `bodyData` to GraphQL pull request comments - `CycleCreate` and `CycleUpdate` now prevent overlapping schedules and validate neighboring cycles using their dates. July 20, 2026 [ ### Introducing Loops ](https://linear.app/changelog/2026-07-20-introducing-loops) Elapsed00:00 Remaining time unknown Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it should run on a schedule or in response to an event. From there, Loops use context from your workspace and connected tools to decide on the next best action. For example: - Review incoming issues, research root causes, and dispatch to coding agents - Create and coordinate follow-up work based on unstructured notes, like meeting transcripts or incident reports - Keep launch plans and project specifications up-to-date - _See more ways to use Loops in the [docs](https://linear.app/docs/loops#example-loops)_ Elapsed00:00 Remaining time unknown Loops run at the team and workspace level, with shared visibility and control. Anyone with access can review their instructions, see how they are configured, and inspect what happened during each run. Loops are available today on Business and Enterprise plans and use AI credits. To help you get started and understand usage, we’re giving your workspace $20 per seat in promotional credits. These credits are applied automatically to runs, and expire on August 20, 2026. Read the [blog post](https://linear.app/now/introducing-loops) to learn more. - Android Added a fallback page for auth redirects so users can reopen the app when browser handoff fails - Asks Fixed Asks created by mentioning the Asks agent in private Slack channels weren’t syncing the originating thread to the issue - Cycles Fixed archived cycles getting stuck behind persisted label and other view filters with no visible way to clear them - Diffs Pull requests with more than 50 commits now loading up to 450 commits - Documents Private team document templates now consistently appearing in the template selector - Editor Fixed checklists pasted from Google Docs rendering incorrectly - Email Prevented notification emails from being sent to deactivated users - Inbox Fixed email intake issues not appearing in the assignee’s inbox when the intake template auto-assigned the issue back to the sender - Integrations Fixed GitHub Enterprise Cloud installation webhooks routing to the wrong workspace region before the installation was known to Linear - Integrations Fixed GitHub Enterprise Cloud setup showing a generic error when an IP allow list blocked Linear, with clearer guidance on allowing Linear IPs - Notifications Fixed duplicate Slack notifications when a newly created issue is added to a view with Slack notifications enabled - Projects Fixed project pages crashing when a graph tooltip referenced a stale date - Pulse Added an unsubscribe action for Pulse items shown through team project update subscriptions - Triage Intelligence Fixed Triage Intelligence no longer requiring destination teams to have workspace-wide scope to be eligible for suggestions - Agent Linear Agent can now manage inbox notifications - Asks Email intake threads can now be resolved and unresolved - Asks Synced comment threads (Slack and Asks) can now be resolved and unresolved, and a new reply reopens a resolved thread - Comments Added inline issue description comments on iOS, including highlights in the description, tap-to-scroll to the thread, and quoted text above description comments - Desktop Added support for Cmd+Z to restore accidentally closed tabs, with timeline-ordered priority and batch restore for bulk close operations - Diffs Added the Diffs inbox as a default home view option - Diffs Improved visibility of auto-merge status in review controls - Diffs Showed failed checks in merge queue removal events - Diffs Showed GitHub force-push events in pull request timelines - Interface Added an Underline links preference under Interface and theme to always underline links in issue descriptions, comments, and documents - Teams Added display options to team member lists for sorting, filtering by member type, and choosing visible columns - Improved attachment uploads to accept base64 payloads with whitespace or `data:` URL prefixes July 2, 2026 [ ### Initiative properties ](https://linear.app/changelog/2026-07-02-initiative-properties) ![Top-level initiatives page on a workspace level showing initiatives grouped by "Company bet" label. Every initiative has an explicit priority assigned.](https://webassets.linear.app/images/ornj730p/production/22e763f897ab3be86523145a6edd20b1cb032d2d-3600x2080.png?q=95&auto=format&dpr=2) Initiatives define your company’s high-level goals and organize the projects that contribute to them. To help you manage initiatives as your roadmap grows, we’ve added a new set of focused initiative properties: - **Proposed** and **canceled** statuses make it clear when an initiative is under consideration or has been intentionally set aside - **Priority** communicates which initiatives are most important - **Labels** group initiatives by product line, region, or other meaningful categories Use these properties to group and filter initiatives on any plan, or build custom initiative views on Enterprise plans. Learn more about initiative properties in the [docs](https://linear.app/docs/initiatives#initiative-properties). ### Centrally manage access to Linear’s MCP server in Claude[⁠](#centrally-manage-access-to-linear's-mcp-server-in-claude) Give employees secure access to Linear and other MCP servers in Claude, without requiring them to authenticate with each server individually. Enterprise-managed Authorization lets Okta administrators manage access and permissions centrally, and users automatically get access to the MCP servers they’re authorized to use when they sign in to Claude. Enterprise-Managed Authorization is available to Enterprise workspaces using Okta as an identity provider and Claude as an MCP client. Learn more in the [docs](https://linear.app/docs/mcp) or in the [MCP specification](https://modelcontextprotocol.io/extensions/auth/enterprise-managed-authorization). You can now share any filtered view by copying its URL from your browser, or by pressing `⌘`/`Ctrl` `Shift` `C` on desktop. Share filtered views to discuss a subset of an existing view with someone else — like an issue view filtered by an assignee, or project or initiative view filtered by a label. - Agents Fixed issues with editing collapsible sections inside documents and descriptions with the Linear agent - API Stopped automatically cancelling and restarting active Triage Intelligence runs after issue content changes - API Fixed fieldless GraphQL input metadata from turning persisted filters into match-all filters - Asks Slack `/asks` commands now pre-fill the modals with the entered text - Automations Fixed showing agent automation `Show more` prompt buttons only when hovering an automation block - Comments Fixed a transient agent session wrapper appearing after mentioning an agent that only handles comment events - Cycles Fixed renamed cycles showing their local generated cycle number in some client Chrome - Desktop Fixed OAuth application creation form resetting when switching tabs on desktop - Diffs Added Linear details comments for manually linked GitHub pull requests when the link is created or changed - Diffs Kept combined code review diffs aligned with side-by-side view when inserted additions are followed by a later paired helper extraction - Diffs Show pull request status icons for coding session inbox notifications tied to PRs - Diffs Fixed review notifications to now open the diff at the relevant comment instead of the guide - Diffs Fixed Team reviews settings appearing when Diffs were disabled - Diffs Fixed poor contrast of JSDoc comments in the GitHub Light syntax theme - Diffs Fixed scroll position jumping when expanding collapsed code sections in diff view - Diffs Fixed commit navigation controls shifting when the changed file count changes between selected commits - Diffs Comment filters on the PR Diffs tab no longer hide comments in the Guide - Editor Fixed emoji rendering in italicized text so emojis remain upright - Editor Improved autolink for a broader list of TLDs when pasting URLs in the editor - Email Fixed email intake settings occasionally displaying an incomplete email address - Initiatives Fixed initiative list with sub-initiatives correctly restoring scroll position on navigation - Initiatives Fixed transparency issues with the icon picker when editing initiatives inline in the list - Integrations Reverted a GitHub sync change that stopped updates from Linear to GitHub once an issue is synced via the `one-way` sync - Integrations Added a warning to Slack issue dialogs when selected labels include multiple labels from the same label group - Integrations Fixed Google Calendar out-of-office status labels showing an absence as starting today when it starts tomorrow in the user’s timezone - Integrations Fixed GitHub issue sync sending Linear label updates back to repositories configured for one-way GitHub-to-Linear sync - Integrations Fixed Linear user mentions in Slack unfurls notifying mentioned users - Integrations Fixed Slack synced comment import retries when Slack returns missing scopes while fetching message replies - Issue Activity Fixed issue activity history no longer briefly reordering or regrouping while loading when lots of labels are involved - Issue templates Fixed blank optional-only form template submissions from creating empty issues - Issues Fixed issue sidebar hover styles not updating after switching between dark and light mode - Issues Fixed copied issues including sub-issues after the Include sub-issues option was disabled - Issues Fixed SLA workflow triggers failing when a workflow condition did not include an issue filter - Mobile Prevented synced email threads from being resolved from Android - Project Views Fixed a problem where hidden groups could not be restored in timeline views - Projects Fixed completed projects appearing in project dependency blocker counts - Projects Fixed newly created projects now receiving varied default icon colors, matching initiatives - Projects Fixed the project update editor border disappearing after Agent highlight interactions - Releases Fixed started release stage rows appearing taller than other rows in release pipeline settings - Settings Fixed existing application images now showing when editing an OAuth application - Settings Fixed settings search input box now respecting custom sidebar theme colors - Settings Fixed customer status and tier row dividers appearing brighter than the header divider in settings - Settings Fixed workspace security settings copy incorrectly referencing recurring issues for workspace template management - Sidebar Properly aligned controls in the sidebar into one consistent column and fixed their focus rings - Slack Stopped retrying permanent Slack webhook errors for disabled app message tabs and invalid block payloads - Teams Fixed duplicate favorite action in action menu on team views - Triage Fixed Triage rules sometimes showing duplicate or missing rows immediately after saving - Triage Fixed the issue preview closing when a new issue entered a label-filtered Triage queue - Views Fixed some server-backed views not loading correctly with some complex filter conditions - Projects Project and initiative overview latest updates no longer inherit the previous latest update’s open state - Diffs Fixed commit titles of specific lengths from overflowing the commit selector dropdown - Initiatives Initiative target dates now use the same completed date rendering semantics as project target dates - Initiatives Show the notifications subscribe control on initiative pages - Estimates Restored the selected issue’s estimate total in the bulk action toolbar - Editor Fixed dragging URL-backed Linear content into editors that was inserting duplicated mentions - Pulse Fixed Pulse summary item navigation inside the inbox and added a breadcrumb back to the originating summary - Documents Fixed restoring deleted documents whose project parent is archived - Pull requests Cmd-clicking linked pull requests now opens them in a new tab - Diffs Fixed bug where some code in Code Review diffs could not be copied to the clipboard - Android Added support for toggling todo checkboxes directly in issue descriptions and comments - Diffs Added syntax highlighting for `.gjs` and `.gts` files in Diffs - Diffs Added settings to control whether GitHub team review requests appear in Reviews and count as To Do - Diffs Collapsed generated protobuf Go files in pull request diffs by default - Diffs Changed PR comment copy menu label to refer to threads when copying prompts for comment threads - Inbox Added ability to filter inbox notifications by related review status - Issues Renamed canonical issue duplicate relation labels from “Duplicated by” to “Duplicates” - Search Updated search tabs to show the search term with a Search prefix and a search-results icon - Teams Improved the spacing between team home columns at medium-width resolutions - Settings Clarified the keyboard preference for submitting comments and agent chat messages - Insights Improved performance of issue and insights queries that filter by initiative - GitHub Added `Linear issue` to the list of `magic words` linking pull requests to issues - Added read-only MCP tools for listing and retrieving Linear Agent skills - Added support for managing releases, release notes, and release issue associations through the MCP server - Added source URL support to the `save_customer_need` tool - Added an external-user actor variant to the webhook actor union - Included the top-level `url` field in data-change webhook payloads for remove actions when an entity URL is available - Fixed entity webhooks for external-user actions so their top-level actor is populated - Added the \] shortcut to show or hide the Agent sidebar from Diffs when an Agent session is available - Fixed Shift Cmd/Ctrl ArrowDown not opening sub-issues in board view June 18, 2026 [ ### Agent assisted project updates ](https://linear.app/changelog/2026-06-18-agent-assisted-project-updates) Elapsed00:00 Remaining time unknown Project and initiative updates keep teams aligned, but writing them means pulling out recent changes from issues, documents, and discussions. Instead of finding that context manually, click **Write with Agent** to let Linear do it for you. The agent reviews changes made since the last update, checks messages in the linked Slack channel, and writes an update draft for you to refine. Add your own perspective by prompting for further changes or editing directly, then publish the update. ### Desktop navigation history and pinned tabs[⁠](#desktop-navigation-history-and-pinned-tabs) We’ve rebuilt our desktop tabs to make navigation feel fluid and predictable. - Each desktop tab now has its own history stack, so moving backwards won’t navigate you to another tab - Pinned tabs are now a reliable home for important work. They stay anchored in the tab bar, persist after quitting and reopening the app, and aren’t replaced by new content you open. These changes are live for current desktop users. Try Linear on desktop by [downloading the app](https://linear.app/download). ### Private sub-teams[⁠](#private-sub-teams) Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handling sensitive data like People Ops. When you create a sub-team under a private team, you can now choose between two access options: - **Restricted to parent team members** — parent team members can see and choose to join the sub-team. This makes it easy to manage private team structures without coordinating invitations to each sub-team. - **Private to team members** — the team is hidden, except to members directly invited to that sub-team Private sub-teams are available on Business and Enterprise plans. Learn more in our [documentation](https://linear.app/docs/private-teams#restricted-and-private-sub-teams). ### Build agents with Vercel Eve[⁠](#build-agents-with-vercel-eve) Vercel Eve is an open-source framework for building custom agents. Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback. You can deploy agents on Vercel with the guided setup, or host them wherever you run your Eve app. Once connected to Linear, teammates can delegate issues to your agent or mention it in comments. Learn more about Eve in Vercel’s [documentation](https://beta.eve.dev/docs/getting-started). ### Release pipeline changelogs[⁠](#release-pipeline-changelogs) [Releases](https://linear.app/changelog/2026-04-30-releases) let you plan and track your software releases. Now, you can also keep your team aligned on what’s shipping with changelogs for each release pipeline. These changelogs bring a pipeline’s release notes together in one place, so progress is easy to review and share. Choose to auto-generate release notes in pipeline settings so your changelog is always up to date. Learn more in our [documentation](https://linear.app/docs/releases#changelogs). ![release pipeline changelog for an iOS pipeline showing fixes in releases 1.81.0 and 1.82.0](https://webassets.linear.app/images/ornj730p/production/d5760a65b0d93563cb4baeb4ec79df2bb8b04357-3600x2192.png?q=95&auto=format&dpr=2) ### OAuth application manifests[⁠](#oauth-application-manifests) OAuth application manifests let platforms provide a one-click OAuth app setup experience for users creating integrations. Use URL parameters to send users directly to a pre-filled _Create OAuth App_ form in Linear. An equivalent JSON manifest format lets you store configurations in files, validate them locally, or generate them programmatically. Find the details in our [developer docs](https://linear.app/developers/oauth-app-manifests). - Command menu Added the missing command menu action for recently deleted initiatives - Comments Threaded comment highlight corners now match with the reply composer below the thread - Customers Fixed stale customer request counts on issues and projects after archiving or restoring customer requests - Desktop Middle-clicking a link to a document comment now properly navigates to the comment - Diffs Fixed the Unified/Split layout toggle not taking effect when a narrow column had forced the diff into unified view - Diffs The tooltip on group headers in the Reviews inbox now covers the entire clickable header - Documents Creating an issue from a selection in a team document now creates it in the correct team - Duplicates When you remove a duplicate relation, it now restores the issue’s last status - Duplicates Fixed duplicate merges running concurrently for the same issue during bulk deduplication - Filters Fixed the filter button not staying visually active while its menu is open - Front Fixed processing Front conversation links for conversations without a primary recipient - GitHub Fixed GitHub integrations being marked “disconnected” after a transient GitHub authentication blip - Inbox We no longer send a _removed from merge queue_ notification when a pull request is successfully merged by GitHub’s merge queue - Inbox Fixed inbox notifications occasionally appearing as blank while the sender’s name was loading - Insights Fixed release-filtered burn-up charts failing to render - Issues Fixed oversized issue status icons in delete confirmation toasts - Milestones Fixed a flicker in the milestone list when creating the first milestone from a project overview - Notifications Each recipient’s name display preference is now respected in project and initiative update notifications - Project Updates Fixed the project updates panel occasionally leaving an empty wrapper element on the page after navigating elsewhere - Pull requests Right-clicking pull request pills in issue lists now opens the correct menu - Pull requests Fixed pull request details overflowing their container when hovering over a PR badge - SCIM Renaming a linked SCIM role group (e.g. `linear-admins`) in the identity provider no longer causes Linear to stop managing the associated role - Settings Prevented the language selector from overlapping the scrollbar in Code & Reviews settings - Settings Fixed an odd transition when switching between the same settings page of different teams - Slack Slack thread sync no longer fails to import a comment when one of its reactions came from a user without access to the issue - Slack Underscores in pull request titles are now preserved in Slack notifications - Slack Slack comment notifications now link out to unsupported images instead of sending invalid Slack image blocks - Slack Slack pasted message links now sync to Linear threads as a clickable link - Agents AI chat thinking steps are now shown as blockquotes when copying conversations as markdown - Diffs Added a “Missing issue” PR filter that shows PRs without a linked issue - Diffs Raised the size limit for generating Guides on larger pull request diffs - Diffs Holding Opt and clicking the chevron in the file header now expands/collapses all files - Diffs Review list approval copy now shows who approved a pull request - Diffs Whole added/removed lines in diffs render more clearly with the same color as inline added/removed characters - Diffs Added the ability to use custom font for code in diffs - Diffs Added contextual help about the Reviews feature and related keyboard shortcuts - Diffs Polished the pull request review layout — removed the divider between the conversation and code columns, and the Guide now has even horizontal padding with the scrollbar no longer overlapping content - Diffs Added copy link to file actions in pull request diffs - GitHub/GitLab Unassigned triage issues remain in triage for Git request and commit automations, unless the final merged change closes the issue - PagerDuty Added support for PagerDuty shift-based schedules, so triage responsibility on-call now syncs from both shift-based (v3) and classic layer-based schedules (v2) - Team documents The documents list now supports multi-select - Views Updated the sort direction icons so the arrow direction matches the active sort order - MCP project status update tools are now available in workspaces without recent project update history - Fixed issue with fetches failing when descriptions contained Unicode line or paragraph separators - `templateCreate` and `templateUpdate` now reject unsupported form field payloads June 11, 2026 [ ### Coding sessions in Linear ](https://linear.app/changelog/2026-06-11-coding-sessions) Elapsed00:00 Remaining time unknown Earlier this year, we launched [Linear Agent](https://linear.app/changelog/2026-03-24-introducing-linear-agent), giving teams a new way to plan and coordinate their issues and projects. Since then, we’ve added [Code Intelligence](https://linear.app/changelog/2026-05-14-code-intelligence) to extend that understanding to the codebase, and [MCP support](https://linear.app/changelog/2026-04-23-linear-agent-mcp-support) to bring all of your context together. Today we’re closing the loop: **Linear Agent can now write code using Claude Code and Codex.** You can triage, plan, review, and ship—all in Linear. Start a coding session by assigning an issue to Linear, or ask it to make a change in a chat, comment, or Slack thread. Each session is grounded in your workspace context, pulling in issue details, history, customer requests, discussions, and related work. ![Linear agent working alongside a diff](https://webassets.linear.app/images/ornj730p/production/020e273126f3f486fdc16fdc7b6a8a337fe31aa1-3600x2160.png?q=95&auto=format&dpr=2) ### A coding agent your team will love[⁠](#a-coding-agent-your-team-will-love) Coding sessions run in the cloud, so you can prototype ideas and make changes without setting up a local development environment. When the change is ready, Linear returns a new diff for review. Share [preview links](https://linear.app/docs/diffs#pull-request-preview-links), bring teammates into the discussion, and address feedback with further iterations in the same thread. ### Automate the first pass[⁠](#automate-the-first-pass) When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team. It follows your team’s guidance, gathers evidence from tools like Sentry or Datadog through MCP, and inspects the codebase to trace the root cause before producing a fix. Linear uses this workflow internally to resolve roughly 30% of incoming bug reports, mostly on the first pass. You can set up your own agent automation in your team’s Triage settings. ![issue activity feed, showing a completed coding session](https://webassets.linear.app/images/ornj730p/production/19f7e609de632c335811b8c3ea412ceadf1383af-3600x2275.png?q=95&auto=format&dpr=2) ### Availability and pricing[⁠](#availability-and-pricing) Coding sessions are available on Basic, Business, and Enterprise plans. They require a GitHub connection with code access and use AI credits to run. Workspace admins can enable coding sessions in [Settings](https://linear.app/settings/ai/coding-sessions) and manage access, usage, and credits from the usage dashboard. [Learn more in the docs](https://linear.app/docs/coding-sessions). - Agents Filled in the thumbs down button after submitting AI feedback - Agents Fixed a missing space between the integrations link and surrounding text on the team agents settings page - Agents Vertically centered the label and preview text in the agent session card’s status row - Agents Fixed left padding of the agent session card header to match other activity cards - Archive Fixed restoring a trashed issue or document failing in rare cases where the document’s trashed flag was stored as `false` - Asks Allowed Slack workflows and external users using the Asks Agent to access private teams’ channel-configured templates - Customers Fixed excessive row spacing and the limited customer list on the unfiltered customers page - Customers Fixed the customer merge preview showing annual revenue under the monthly revenue label - Customers Fixed a bug where linking a Slack channel to a customer failed for workspaces with multiple Slack connections but a single Asks connection - Diffs Opening a `linear.review` link in a workspace without Diffs enabled now routes to enable-reviews instead of bouncing back to GitHub - Diffs Fixed showing GitHub legacy commit statuses (e.g. external CI like RWX or Jenkins) in PR checks - Diffs Fixed “Update branch → with rebase” creating a merge commit instead of rebasing - Diffs Fixed the file list sidebar not scrolling when the file tree was taller than the viewport - Display options Fixed the display options menu being slow to open on views grouped into a large number of items - Editor Fixed customer and customer request mentions not loading their details in the iOS editor - Editor Pasting `linear.app/review///pull/` now properly embeds as a PR mention - Editor Fixed the tooltip for plain links covering link controls - GitHub Fixed Linear issues with comma-containing label names failing to sync to GitHub - Initiatives Fixed Initiative projects table columns occasionally overlapping or taking up too much width - Integrations Fixed an importer freeze when mapping a large number of users - Issues Fixed a line break appearing between an issue’s status icon and its identifier in undo/redo toasts - Labels Archived labels no longer appear in the form-template label group picker - Links Fixed a crash when a link embed with a missing or invalid URL failed to load a preview - Mobile Release, Release Note, and Release Pipeline mentions now display properly on mobile - Notifications Fixed agent completion notifications not being delivered to the user who delegated the work - Projects Project issue list deep links now redirect to the project overview instead of the filtered issue view - Project Views Fixed saved project views unexpectedly showing empty groups when grouping and filtering projects - Pulse Fixed daily Pulse summaries being skipped when a single feed update had a malformed body - SCIM Fixed SCIM role group pushes not repairing a stale role when the user was already tracked in the role’s membership - Settings AI settings dependent on the Linear Agent now show “Disabled” when the Linear Agent is turned off - Slack Sharing a project comment link in Slack now unfurls the comment instead of the project - SLAs Fixed missing SLAs for issues created from Slack asks - Updates Fixed inconsistent icon spacing in the project/initiative update health control - Asks Improved longer, cleaner fallback issue titles when creating Asks from Slack without an AI-generated title - Diffs The “Copy pull request number” action now copies just the number, without the leading `#` - Diffs Added a file action to open the full file in GitHub from the review diff - Diffs Guided reviews now jump directly to a selected file instead of scrolling slowly through every file in between - Documents Added “New document” and “New document from template” to the right click menu on the create issue button - Team Documents Added cycle documents to the team documents tab, including support for grouping documents by cycle - Triage On Android, choosing a status that requires a priority to leave triage now opens the priority picker automatically instead of hiding those statuses - Editor Changed the strikethrough shortcut to Cmd/Ctrl Shift X - `list_comments` now returns comments on archived issues - Documents can now be listed and created under a team June 4, 2026 [ ### Team documents ](https://linear.app/changelog/2026-06-04-team-documents) ![Shows a team page with pinned docs and links](https://webassets.linear.app/images/ornj730p/production/6263cddeb0816ce7f9ce24e49dc6870d55b37c65-3600x2080.png?q=95&auto=format&dpr=2) Important team context doesn’t always belong in a specific issue, project, or initiative. Teams also need a dedicated place for the notes, docs, and shared references that support their work over time. Now, every team has a page to keep its context organized and easy to access. Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections. Open a team’s page by clicking on its name in your sidebar, or search by pressing `o`, then `t`. Learn more in our [documentation](https://linear.app/docs/teams#team-documents). ### Shared skills for Linear Agent[⁠](#shared-skills-for-linear-agent) [Skills](https://linear.app/docs/linear-agent#skills) let you save reusable instructions for Linear Agent. We now support sharing skills with your team so great personal workflows can become shared team process. Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates. Use skills in any agent conversation by clicking on _Skills_ or using a slash command. You can share an existing skill from [settings](https://linear.app/settings/account/agents), or by asking Linear Agent. Learn more in our [documentation](https://linear.app/docs/linear-agent#shared-skills). You can now comment directly on text or images in issue descriptions. Select any part of a description to leave a comment anchored to that exact spot. Use description comments to share feedback on a specific part of the description, rather than commenting on the issue as a whole. - Asks The Creator in activity log copy for Slack Asks issues now always matches the `creator` filter. - Attachments Linear now preserves the original filename (and extension) when downloading attachments whose name contains characters like middle dot (`·`) or non-breaking space. - Comments Fixed synced Slack thread replies that could fail or disappear after switching threads. - Comments Fixed mentioning app users in comments created through triage automations. - Comments We now correctly strip leading whitespace from comment paragraphs on submit. - Diffs Files marked as viewed in the Guide tab now stay collapsed when returning to the Diff tab. - Diffs Fixed links in Guide jumping or over-scrolling past the target when navigating to a file or symbol. - Diffs Fixed the diff horizontal scrollbar not being draggable when a collapsed unchanged-lines row was present. - Diffs Fixed Guide showing large blocks of unchanged code when an LLM-supplied hide directive sat adjacent to a long unchanged stretch. - Documents Capped the document table of contents markers height, showing only top-level headings when there are too many to fit. - Documents Fixed a previously open document staying selected after creating a new document in side-by-side view. - Display options Toggling a display option back to its default now correctly clears the modified indicator on the Display button. - Editor Fixed portrait videos being clamped when going fullscreen. - Figma Fixed Figma links in comments triggering repeated comment update errors and slow issue loads. - GitHub GitHub backlink comments are now posted for issues that reference a GitHub URL even when the target repo isn’t synced to a Linear team, as long as the GitHub install can access it. - GitHub We now correctly handle null GitHub ghost users across webhook, issue sync, and pull request intake paths. - GitHub Fixed GitHub issue sync failing with a 401 “A JSON web token could not be decoded” error in some GitHub Enterprise Cloud workspaces. - Google Sheets Fixed a Google Sheets export failure caused by large issue batches overflowing the call stack. - Inbox Returning to Inbox no longer scrolls to a previously-viewed notification without selecting it. - Insights Fixed incorrect Insights results when using “Time in status” after an issue status was renamed. - Integrations Fixed Linear Agent creating a Slack channel for new projects when “Automatically create channel for new projects” was disabled. - Keyboard Pressing Esc on a page opened directly in a new tab no longer wipes that page from browser history, so the browser back button can still return to it. - Linear Agent Stopped the Linear agent from chiming in on later Slack thread chatter after it creates an issue/Ask. - Login Login now shows a clear error instead of a false “email sent” confirmation when emails can’t be delivered to a suppressed address. - Onboarding Fixed the onboarding invite step hanging on desktop after sending invites. - Performance Loading icon animations are more performant and use less CPU. - Projects Fixed missing icons on project milestone context menu actions. - Projects Fixed missing padding around the milestones help text shown when a project has no milestones. - Projects Fixed project activity showing the wrong priority change after consecutive priority updates. - Pulse Fixed Pulse summaries rendering document links with a stray `@` prefix instead of a proper document mention. - Releases Fixed a bug that caused only partial release names to be saved. - Diffs Clicking “Request review” on a draft pull request that already has requested reviewers now marks it ready for review directly. - Diffs Outdated review comments are now reflected separately from resolved comments in the code review comment summary. - Search Fixed exact issue identifier searches with different casing not ranking the matching issue first. - Sidebar Fixed alt-clicking a team in the sidebar downloading an HTML file instead of collapsing/expanding all teams. - Sidebar Fixed the “Exploring” sidebar section dropping a team when navigating to its documents tab. - Sidebar Sidebar nav item hover state changes are now instant. - Slack project channels Linear no longer overwrites a connected Slack channel’s topic when a project’s description changes. - Templates Fixed an error that could occur when saving templates that contained legacy invalid content. - Templates Fixed issue templates intermittently losing their default project and milestone. - Triage Fixed the triage automation actor name showing “Triage Behaviour” instead of “Triage Behavior”. - Triage Fixed the triage responsibility settings separators appearing darker than the triage rules card. - Version history Fixed the “Highlight changes” toggle disappearing when turned off in version history. - Views Fixed a freeze that could occur when opening some saved issue views. - Agents Added an _Error_ option to the agent session issue filter and insights grouping. - Diffs You can now paste a GitHub pull request link into command menu to open it in Linear. - Diffs Customers on legacy plans can now use Diffs. - Diffs We now show indentation changes in diffs for more whitespace-sensitive languages (CoffeeScript, Elm, F#, HAML, Haskell, LiveScript, MoonScript, Nim, Stylus, Makefile). - Editor We now support right-clicking an issue mention in a doc or editor to change its properties. - Editor We now treat ) and ( as emoji autocomplete aliases for standard smile and sad results. May 28, 2026 [ ### Linear Diffs ](https://linear.app/changelog/2026-05-27-linear-diffs) Elapsed00:00 Remaining time unknown Agents generate large volumes of code, but individuals are still accountable for the changes that merge. This leads to a lot of review work, and the capability and performance of traditional review tools hasn’t kept up. Today, we’re releasing Linear Diffs to make reviewing code a fast and fluid experience native to Linear. You can now review diffs from any issue with a PR, iterate on further changes with agents, and ship code from Linear. All reviews in Linear sync back to GitHub, so the current state of review work is always clear. ![main diffs ui showing code changes and a file list](https://webassets.linear.app/images/ornj730p/production/597fabd8e9471472b51411838daa13ac9b108f4c-3600x2058.png?q=95&auto=format&dpr=2) #### Guided reviews (beta)[⁠](#guided-reviews-\(beta\)) Guided reviews help you efficiently review large PRs. When you view a diff in this format, you’ll see the core of change first, so you don’t have to dig for an entrypoint. Each section of diffs has an explanation — starting with what the change is, then moving into its consequences. Guided reviews separate out glue code and secondary changes so you can stay focused on what matters. This style of review makes it much easier to move through large changes in a single sitting. Guided reviews are free during beta and available for Linear customers on Business and Enterprise plans. ![guided review with an explanation and file selection on the left, and the diffs on the right](https://webassets.linear.app/images/ornj730p/production/b5c45bfed8d9d634f390c5a48461980055869637-3600x2200.png?q=95&auto=format&dpr=2) #### Review Inbox[⁠](#review-inbox) Staying on top of reviews is easier when review notifications live alongside the rest of your work. Linear notifies your Inbox for work like review requests, your approved PRs, and comment mentions. You can set up additional real-time desktop, Slack, email, or mobile [notifications](https://linear.app/settings/account/notifications). We’ve also added a dedicated Reviews tab in your sidebar so you can see all your review work at once. The default focus ordering sorts reviews by what’s closest to shipping, so the work that needs your attention most rises to the top. ![Reviews dedicated tab showing what needs your input](https://webassets.linear.app/images/ornj730p/production/3852f8c30d20c29a0831c1d6ca1682542c7b386e-3600x2200.png?q=95&auto=format&dpr=2) #### Reviewing code[⁠](#reviewing-code) When a review calls for changes, keep iterating from the diff surface with a background coding agent. Agent changes update the diff in real-time, so you don’t need to check out the branch locally for every small tweak. Diffs is responsive when reviewing even very large PRs. You can view unified or split diffs, enable line wrapping and structural highlighting, and choose custom code themes. ![Making changes with agents in a diff](https://webassets.linear.app/images/ornj730p/production/7320fa30208068db3493fe8b9e64bdb46b8a852c-3600x2058.png?q=95&auto=format&dpr=2) Linear Diffs is available now on all plans. Guided reviews are free during beta and available for Linear customers on Business and Enterprise plans. Workspace admins can enable Diffs by [upgrading](https://linear.app/settings/integrations/github) Linear’s GitHub integration for code access. Then, individual users can choose to [review diffs in Linear](https://linear.app/enable-reviews). To learn more about why we built Diffs, read [Code review should be fast](https://linear.app/now/code-review-should-be-fast). For more on Diffs functionality, check our [documentation](https://linear.app/docs/diffs). - Agents Fixed choppy animation when expanding agent thoughts - Agents Fixed agent chat incorrectly minimizing on external link click - Agents Fixed the “Worked for X” label on agent session turns to measure active work time, excluding any idle wait between turns - Agents Fixed agent panel staying focused when expanding or collapsing - Agents Prevented the Ask Linear popup from reopening off-screen after the window height shrinks - Agents Fixed Ask Linear drafts being lost when switching between chats - Agents Fixed agent lists showing too many skills - Asks Linear Asks Agent will now automatically reply to external users when requesting additional information - Asks Fixed Asks Web submission attributions when the submitter logged into Asks Web before accepting their Linear workspace invite - Desktop Fixed an issue where the desktop application could hang when waking up your computer from sleep - Desktop Fixed desktop app flash of white background on new window open - Diffs Fixed deduplication of linked PRs in issue attachment data - Diffs Fixed refreshing the diff when a PR’s target branch changes (e.g., after a stacked parent merges and GitHub retargets the child) - Diffs Stopped attributing GitHub PR comments authored by deleted (“ghost”) users to the wrong user in notifications - Documents Fixed document mention notifications firing on every edit instead of just when a user is newly mentioned - Documents Shortened the placeholder in the “Change document subscribers” action menu so its keyboard shortcut indicator no longer gets clipped - GitHub Comments on a not-yet-linked GitHub PR now backfill the issue→PR link via magic-word matching the same way PR lifecycle and review events do - Inbox Fixed “From is not” filter to correctly exclude issue assignment notifications from integration and OAuth application-driven assignments - Inbox Fixed inbox badge getting stuck when arriving on a review via a legacy `/agent` URL - Insights Fixed a bug where two Duplicate options appeared in the Time in status filter - Integrations Figma links now show a clean `Figma` title instead of the raw marketing page title - Issues Removed Duplicate status from quick issue create and issue template - Project templates Allowed project-template sub-issues to target other private teams again - Sentry Fixed a bug where Sentry-created issues could be assigned to deactivated users in triage - Settings We now correctly truncate long team names in Teams settings list instead of overlapping the next column - Shortcuts Fixed the Copy as Prompt shortcut so it updates issue status when auto-start-on-open is enabled - Sync Fixed “Linear servers are not reachable” error that could appear after laptop unlock - Triage Fixed workspace issue templates not appearing in triage automation filters - Views Fixed list rows shifting horizontally when toggling a group in views with grouped columns - Android Improved Android to use server-side filtering for skills - Agents Dashboard pages are now used as context in the Linear agent chat - Integrations Connecting GitHub now defaults to enabling code access - Project Slack channels Used an info-style toast when starting project Slack channel creation - Reviews Activity page file and code comment links, and PR notifications, now open whichever code view (Diffs or Guide) you last visited - Skills Updated empty state for skills to match other settings - Timeline Improved timeline projects aside panel visibility to be remembered per view instead of globally - Updates Removed the UI for hiding project and initiative update details --- ## Text attribution and agent-assisted editing – Changelog · 437 words [Changelog](https://linear.app/changelog) [](https://linear.app/changelog/2026-07-23-agent-assisted-editing) ![a document and an agent panel showing the prompt to edit ](https://webassets.linear.app/images/ornj730p/production/15b9a90d9ef28e617836383f0b295536c437b4b1-3600x2080.png?q=95&auto=format&dpr=2) Documents and project descriptions are critical context for your teams and agents. You can now edit text with [Linear Agent](https://linear.app/docs/linear-agent), and use [Loops](https://linear.app/docs/loops) to keep docs and project descriptions up-to-date. Author name indicators let you check if text was written by a colleague or added by a loop. When editing, changes you make through Linear Agent highlight separately so they’re easy to review. If you need to revert to an earlier version, restore to any previous checkpoint from version history. Show author names or open version history from the ⌘/Ctrl + K menu, or in document display options. Learn more in our [documentation](https://linear.app/docs/project-documents#edit-documents). The issue sidebar now closely integrates issue properties with the main content. We’ve pinned Diffs to the top of this panel so you can access the issue’s pull requests from anywhere on the page. ![New issue sidebar with diffs at the top](https://webassets.linear.app/images/ornj730p/production/fdbe518ba5882edab1681f7410f9af78716021f2-3600x2058.png?q=95&auto=format&dpr=2) - Asks Fixed issues created through Slack Asks ignoring a chosen template’s default status - Comments The resolved comments menu no longer appears when there are no resolved comments - Diffs Submit review flyouts now properly close when clicking outside them - GitHub Prevented revert pull requests from reopening issues linked to another GitHub repository - GitHub Fixed linking GitHub pull requests to issues via pasted URLs. - Initiatives Fixed oversized initiative titles - Integrations Fixed a bug where removing a linked GitHub pull request disconnecting GitHub issue sync - Integrations Fixed Slack project channel setup retrying after a project was deleted or archived - Settings Fixed IP restrictions not appearing when searching for “IP” in settings - Slack Fixed truncated issue summaries in Slack unfurls - Views Fixed view filters (like Cmd/Ctrl F filtering) resetting when navigating to an item in a split view list - Editor Added Backspace navigation from empty issue descriptions and document bodies back to the title - Issues Improved issue composer to suggest templates as a quick suggestion, surfaced before other suggestions because they apply a bundle of issue properties - Projects Added a way to view a project’s issues filtered by a specific milestone from the project overview on iOS - Triage Added triage responsibility to the triage screen on iOS, showing who is responsible for incoming issues and letting you manage the action and responsible members - Diffs “Quick to review” now shows up for slightly larger PRs and also appears for the author of the PR - Added `bodyData` to GraphQL pull request comments - `CycleCreate` and `CycleUpdate` now prevent overlapping schedules and validate neighboring cycles using their dates. --- ## Cycle graph – Linear Docs · 368 words The graph displays the progress you’ve made in your cycle. ![Cycle graph visual showing progress](https://webassets.linear.app/images/ornj730p/production/ec0484ed17e913e650b6e875124052f3a286ffad-2110x976.png?w=1440&q=95&auto=format&dpr=2) ### Overview[⁠](#overview) Cycle graphs autogenerate once a cycle has begun and update automatically as work in the cycle changes. When viewing a specific cycle, open the cycle sidebar with Cmd/Ctrl I to view the graph. From the Cycles view, you’ll also see the graph belonging to the current cycle. ### How to read a cycle graph[⁠](#how-to-read-a-cycle-graph) The **gray line** displays the total scope of your cycle. The **blue dotted line** represents the “target”—an even distribution of the total estimated points within the cycle over the remaining days in the cycle. It flattens over weekends since people generally do not work on weekends. If your progress line stays at or above the target line, you are on track to complete everything within the cycle. The **yellow line** depicts the number of issues started. It is drawn stacked on top of the completed line, so the combined height of the yellow and blue areas represents all active work. The **solid blue line** shows how many issues have been completed. The **blue bars** also represent completed issues. This can be useful to more easily compare relative issue completions over time, especially in cases when completed and started lines travel nearly identical paths. ### Understanding scope[⁠](#understanding-scope) Scope is based on the total work in the cycle. Depending on the options selected in [Settings > Team > General > Estimates](https://linear.app/settings/teams), this uses estimate points, including the team default for issues without an explicit estimate, or falls back to issue count. ### Assign completed issues to previous cycles[⁠](#assign-completed-issues-to-previous-cycles) Issues that were already part of a cycle when it closed can still be counted back into that cycle if they are completed shortly afterward, before the next cycle starts. ### FAQ[⁠](#faq) The overall Cycle Success is calculated based on the percentage of issues completed or started during a cycle. Completed issues are fully counted, while started issues are counted as 25% done. For an example cycle with 10 issues, where 5 are completed, 4 are started and 1 is untouched, you will see 60% cycle success (4 started issues × 25% = 1 issue equivalent, or 10% of 10 total) --- ## Project graph – Linear Docs · 537 words The graph shows you the progress you’re making toward completing your project and estimates when you’ll complete it. ![Project Graph visual](https://webassets.linear.app/images/ornj730p/production/dec684e2f9d0666eac860146ac9c6e82d1e94c47-409x321.png?w=1440&q=95&auto=format&dpr=2) ### Overview[⁠](#overview) Project graphs autogenerate once the status of a project has been moved to a Started status and we’ve collected enough project issue data for them to be created. Project graph statistics update hourly with the latest issue activity, and the time granularity of graph points is every 7 days. Predictions are calculated based on weekly velocity data. ### Where to find it[⁠](#where-to-find-it) From the project view, open the project sidebar Cmd/Ctrl I to view the graph. If it’s not there, that means that we have not generated it yet. ![](https://webassets.linear.app/images/ornj730p/production/c377a88c314fd6d0ceacf255f927c3220f1d9a07-16x16.svg?q=95&auto=format&dpr=2) **ProTip**: It can be helpful to set a target date to deter scope creep and create accountability for the project to ship in a reasonable amount of time. ### How to read it[⁠](#how-to-read-it) A gray line shows you the project scope and how it has changed over time, giving you an easy way to see (and mitigate) scope creep. We have separate lines for _Started_ and _Completed_ issues. This lets you see exactly what is being worked on and what is done. Blue bars also indicate completed issues over time for ease of interpretation when _Started_ and _Completed_ lines overlap. You can see how a project’s issues break down by assignee and label, as well as what percentage of issues in those categories have been completed. You can hover over any assignee or label and click “filter” to show related issues. You can also hover over the graph to see the exact values of scoped, completed and started issues over time. If you have a target date set, it’ll show up as a red vertical line. #### Live predictions[⁠](#live-predictions) We show an estimated completion date once the project has enough history to calculate a weekly velocity. Moving issues into a Started status contributes to that prediction. You’ll see the purple line for completed issues continues on with a dotted line to the predicted completion date. The graph will always start at 0. The projected completion date(s) are calculated by how long it will take to complete the remaining issues based on the current weekly project velocity. Project velocity is calculated based on weekly historical data: how many completed issue points per week. More recent weeks are weighted more heavily, as they indicate a more current rate of progress. We need at least one week of data to show prediction. Remaining issue points are calculated by summing the points of incomplete issues with a 1/4 modifier for any in-progress issues. After calculating a predicted completion date, we offer an optimistic and pessimistic completion date that includes a buffer of about ±40%. When available, these predictions are displayed as dotted lines starting from the Completed line at the current date. ### FAQ[⁠](#faq) This can happen when project scope is reduced, in order to maintain a representative relationship between the Scope and Progress lines. Examples include when someone deletes or removes issues from a project, cancels issues from a project, or reduces issue scope. If estimates are off in a team, all issues are treated as 1 estimate point for the purposes of building the project graph. --- ## Linear – The system for product development · 766 words ### The product development system for teams and agents ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/6600ca96-e49b-4fd9-c03a-7979faddad00/f=auto,fit=scale-down,metadata=none,width=2560) ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c7fa8f5f-d439-4329-6a65-de549b51e300/f=auto,fit=scale-down,metadata=none,width=2560) #### Faster app launch Render UI before `vehicle_state` sync when minimum required state is present, instead of blocking on full refresh during iOS startup. ##### Activity ![Avatar of Karri](https://webassets.linear.app/images/ornj730p/production/f79251b06e9edeeacbf2875384defe629e000b3c-352x352.png?w=72&q=95&auto=format&dpr=2) Linear created the issue via Slack on behalf of Karri·2min ago Triage Intelligence added the labels Performance and iOS·2min ago ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c2f6447a-d507-43c1-f3ab-3f2c6fbceb00/f=auto,fit=scale-down,metadata=none) Linearconnected by Jori·2 min ago Changed 2 filesDraft PR awaiting your review·2 min ago Linear moved from Todo to In Progress·just now Reviews Revert Properties In Progress Medium ![Avatar of Karri](https://webassets.linear.app/images/ornj730p/production/f79251b06e9edeeacbf2875384defe629e000b3c-352x352.png?w=72&q=95&auto=format&dpr=2) Karri ![Linear](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c2f6447a-d507-43c1-f3ab-3f2c6fbceb00/f=auto,fit=scale-down,metadata=none)Linear Cycle 144 Labels Releases Linear App1.6881...⋅Jun 25 [](https://linear.app/customers) Powering the companies building the future ### **A new species of product tool.** Purpose-built for modern teams with AI workflows at its core, Linear sets a new standard for planning and building products. Purpose-built Linear is shaped by the practices and principles of world-class product teams. Powered by agents Designed for workflows shared by humans and agents. From drafting PRDs to pushing PRs. Designed for speed Reduces noise and restores momentum to help teams ship with high velocity and focus. Fig 0.1 Purpose-built Linear is shaped by the practices and principles of world-class product teams. Fig 0.2 Powered by agents Designed for workflows shared by humans and agents. From drafting PRDs to pushing PRs. Fig 0.3 Designed for speed Reduces noise and restores momentum to help teams ship with high velocity and focus. Reduce UI flicker during autonomy... Add buffering for autonomy event streams Reduce startup delay caused by vehicle sync Fix delayed route updates during rerouting Remove UI inconsistencies BugDesign TypeError: Cannot read properties Bug Upgrade to Claude Opus 5 AI Optimize load times Performance Remove contentData from GraphQL API 61039 Launch page assets Design Prevent duplicate ride requests on poor... Bug62048 Clean up deprecated APIs... API61002 Reduce latency in autonomy st... 61005 Reduce ETA fluctuations durin... 61202 Improve fallback messaging UI61149 Improve rider visibility into veh... ![lena](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/580cd9c0-2770-4fe4-1ad2-95c76fc6f000/f=auto,fit=scale-down,metadata=none) Anyone else noticing the iOS app feels slow to open if you haven’t used it in a bit? ![didier](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c8aeedda-7726-4a4f-226a-f573f85d8d00/f=auto,fit=scale-down,metadata=none) Yea, we’re still blocking initial render on a full vehicle\_state sync every time… ![andreas](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/22210a73-581d-42db-d42a-bf2907860300/f=auto,fit=scale-down,metadata=none) Feels like we could render sooner and load the rest in the background. Probably also worth tracking startup timing so we know how often this happens! @Linearcreate issues and assign to me ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/7d7115d9-a0eb-4a92-5900-3ca3ee077d00/f=auto,fit=scale-down,metadata=none) MAR APR MAY JUN JUL AUG SEP 2 9 16 23 6 13 20 27 4 11 18 25 1 8 15 22 6 13 20 27 3 10 17 24 7 14 21 28 UI Refresh Core screens Polish Split fares Internal Public Beta Autonomy status clarity Alpha Autonomy telemetry reliability Beta GA Oct 2025 Nov 2025 Dec 2025 Jan 2026 Feb 2026 ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/584d7dbd-ff4a-41bb-4fab-74fd5217a400/f=auto,fit=scale-down,metadata=none) what are the three most important customer requests around permissions? add them to the Access Controls project Worked for 8 sec Three issues ranked by customer impact: ENG-2298Add granular project permissions ENG-2647Let guests access multiple teams ENG-2352Create custom roles with scoped access I’ve added them to Access Controls add retry handling for failed image uploads described in this issue ENG-2844added to context Review today’s mobile triage and group the issues by what should happen next Mobile Triageadded to context review this issue, draft complete offline mode requirements, and break the work into sub-issues ENG-2521added to context Worked for 1 min Updated the issue with requirements, open product decisions, and acceptance criteria. ENG-2920Define offline mode requirements ![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c16152f3-a36c-468e-89ae-f87c2f244d00/f=auto,fit=scale-down,metadata=none) ENG-2076Reduce ETA jitter #55423PerformanceWorking…![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/13a0909f-186f-4d83-3fd3-d04883ec2d00/f=auto,fit=scale-down,metadata=none)![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/36d030ed-3a7c-48bb-349b-0427c2b60d00/f=auto,fit=scale-down,metadata=none)Oct 6 ENG-2108Handle GPS dropouts gracefully #55409MapsWorking…![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/13a0909f-186f-4d83-3fd3-d04883ec2d00/f=auto,fit=scale-down,metadata=none)![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/36d030ed-3a7c-48bb-349b-0427c2b60d00/f=auto,fit=scale-down,metadata=none)Oct 2 ENG-2143Optimize map tile loading on initial app open Maps![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c9d0b44c-78f9-4a9b-0a8e-f06a8187be00/f=auto,fit=scale-down,metadata=none)Oct 7 ENG-2187Prevent duplicate ride requests on poor networks BugWorking…![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/f9ed2721-1966-4abc-129b-93aaac1a6200/f=auto,fit=scale-down,metadata=none)![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/21de8e51-12ad-4d17-e347-f0e038c3a000/f=auto,fit=scale-down,metadata=none)Oct 5 ENG-2254Reduce unnecessary map re-rendering on home screen Maps![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/f28b59f4-538c-4517-cfd7-510913015200/f=auto,fit=scale-down,metadata=none)Oct 10 ENG-2291Clean up deprecated APIs used by the rider app API![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/e3bd83aa-9996-412f-0da3-7bf1f4701100/f=auto,fit=scale-down,metadata=none)Oct 9 ENG-2327Speed up CI pipelines for mobile builds Performance![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/21de8e51-12ad-4d17-e347-f0e038c3a000/f=auto,fit=scale-down,metadata=none)Oct 9 ENG-2358Reduce flakiness in mobile UI tests Reliability![](https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/e0a81846-aac4-488d-743e-cac098b8f700/f=auto,fit=scale-down,metadata=none)Oct 4 ``` import React from 'react'import { View, ActivityIndicator } from 'react-native'import { useVehicleState } from '@hooks/useVehicleState'import { Dashboard } from '@components/Dashboard'export const HomeScreen = () => { const { vehicleState, isFullySynced } = useVehicleState() if (!isFullySynced) { return } return ( )} ``` ``` import React from 'react'import { View, ActivityIndicator } from 'react-native'import { useVehicleState, SyncStatus } from '@hooks/useVehicleState'import { Dashboard } from '@components/Dashboard'export const HomeScreen = () => { const { vehicleState, syncStatus } = useVehicleState() if (syncStatus === SyncStatus.PENDING) { return } return ( )} ``` ``` export const CodeReview = () => { }; ``` ### Changelog ---