{"slug": "linear-coding-sessions", "title": "Linear Coding Sessions", "summary": "Linear launched coding sessions that allow users to run agentic coding workflows directly within the platform, enabling automated pull request creation and code review through Claude Code or Codex. The feature, available on Business and Enterprise plans, lets workspace members delegate issues to Linear for automatic fixes, start multi-player coding sessions from Slack or Teams, and create PRs without local setup. Workspace owners or admins must enable the feature through GitHub Integration settings and grant code access before members can begin using coding sessions.", "body_md": "# Coding sessions\n\n[Overview](#overview)\n\nCoding sessions let you run agentic coding workflows in Linear.\n\nWhen you delegate an issue to Linear, we start a secure coding session through Claude Code or Codex. Linear drafts a PR and adds a diff to the issue, which you can check yourself before requesting review. Once approved, merge your PR directly from Linear.\n\nUse coding sessions to\n\n- Automatically fix incoming issues in\n[Triage](https://linear.app/docs/triage) - Start multi-player coding sessions from Linear, or by mentioning\n`@linear`\n\nin Slack or Teams - Let workspace members with repository access create PRs without a local setup\n\nCoding sessions are supported on Business and Enterprise plans. Usage draws from your workspace’s AI credits. See [our docs](https://linear.app/docs/ai-credits) for more information.\n\n[Setup](#setup)\n\nA Linear owner or admin with GitHub organization owner access can enable coding sessions within your workspace by:\n\n- Navigating into your\n[GitHub Integration settings](https://linear.app/settings/integrations/github)and granting code access - Enabling\n[Coding sessions](https://linear.app/settings/ai/coding-agent)\n\nAfterwards, any workspace member with a GitHub account linked in [Connected Accounts](https://linear.app/linear/settings/account/connections) will be able to start a coding session.\n\n[Choose a model](#choose-a-model)\n\nOur default model (tracked under *Auto*) is Claude Opus 4.8. We will continue to update our model selection over time. The model selected here is used for all subsequent coding sessions in the workspace.\n\nWorkspace owners or admins can update the model selection from [Coding sessions settings](https://linear.app/settings/ai/coding-agent). We currently support Claude Fable 5, Claude Opus 4.8, Claude Sonnet 4.6, GPT-5.5 and GPT-5.4.\n\n[Start a coding session](#start-a-coding-session)\n\nWhen you delegate work to Linear, Linear Agent creates an secure coding session tied to that issue and begins working from the context already there. Click on the session to steer or follow up with the agent, or let it run — you’ll be notified when your input is needed.\n\n[Review code changes](#review-code-changes)\n\nWhen a coding session produces a pull request, the workflow continues in your *Reviews* tab, where you can inspect the resulting diffs and follow review discussions.\n\nYou can also delegate code review actions to the Linear Agent directly to address any left review comments from other teammates, requirements to rebase open PRs onto master, or fixing tedious lint issues.\n\n[Guidance and skills](#guidance-and-skills)\n\nCoding sessions work from the issue you delegate and the repository access available to your workspace, and the guidance configured for Linear Agent.\n\nCoding sessions are guided from the existing Claude Code or Codex setup your team already uses, depending on your preferred model. If your repositories include guidance within a dedicated `skills.md`\n\nfile, Linear Agent can use that context during a coding session alongside the issue and repository context.\n\n[Writing effective issues](#writing-effective-issues)\n\nCoding sessions begin from the issue you delegate. The more clearly an issue defines the desired outcome, scope, and constraints, the less time Linear spends exploring the codebase or inferring requirements.\n\n**Too ambiguous**\n\nSearch is broken.\n\nImprove the search experience.\n\nUsers can’t find archived projects through search.\n\nThis should respect theInclude archivedtoggle.\n\n**Well-scoped**\n\nIssue search excludes issues from archived projects, even when Include archived is enabled.\n\nUpdate`issueSearch.ts`\n\nso issue search respects the existing`includeArchivedProjects`\n\nflag. When enabled, issue search should include issues from archived projects that match the search query. When disabled, existing behavior should remain unchanged.\n\nReuse the existing`includeArchivedProjects`\n\nfiltering behavior used elsewhere in search rather than implementing archived project filtering independently.\n\nDo not modify search ranking, pagination, or project search behavior.\n\nThe well-scoped example above points Linear toward the relevant code, existing patterns, and expected behavior while defining what should not change. [Code Intelligence](https://linear.app/docs/code-intelligence) can also be a useful tool to help iterate on issue descriptions for optimization prior to delegation.\n\nInformation that reduces ambiguity or codebase exploration helps Linear reach an implementation faster and use AI credits more efficiently.\n\nFor more detail on typical costs per session, see our [AI Credits documentation](https://linear.app/docs/ai-credits#typical-costs).\n\n[Agent automations](#agent-automations)\n\nOnce you’ve enabled coding sessions, the next way to drive efficiency is to kick them off automatically.\n\nTriage automations let you run agent behaviors, including coding sessions, each time an issue arrives in Triage. Optionally, filter to run only when an issue meets specific criteria, like a label, creator, or other filterable property.\n\nInternally, our favorite way to use these automations has been to have Linear take the first pass at issues coming into Triage. Each time [Triage Intelligence](https://linear.app/docs/triage-intelligence) identifies a new issue in triage issue as a bug, this automation runs to investigate and draft a PR if called for. You can set up automations of your own in a team’s triage settings.\n\n[AI credits](#ai-credits)\n\nCoding sessions usage will draw from your workspace’s AI usage credits. Any chat or automation that prompts for a code change will open a coding session.\n\nOn our launch date of June 11th, 2026, all workspaces on Basic, Business and Enterprise have a shared pool of promotional credits ($20 multiplied by the number of unsuspended users in your workspace). Once used, workspace admins can top up AI credits to continue using coding sessions.\n\nPlease see [AI credits](https://linear.app/docs/ai-credits) for more information.", "url": "https://wpnews.pro/news/linear-coding-sessions", "canonical_source": "https://linear.app/docs/coding-sessions", "published_at": "2026-06-12 03:57:05+00:00", "updated_at": "2026-06-12 04:48:37.866814+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "ai-products", "large-language-models", "generative-ai"], "entities": ["Linear", "Claude Code", "Codex", "GitHub", "Claude Opus 4.8", "Slack", "Teams", "Business"], "alternates": {"html": "https://wpnews.pro/news/linear-coding-sessions", "markdown": "https://wpnews.pro/news/linear-coding-sessions.md", "text": "https://wpnews.pro/news/linear-coding-sessions.txt", "jsonld": "https://wpnews.pro/news/linear-coding-sessions.jsonld"}}