# Coding sessions ![Delegate work to Linear Agent for implementation](https://webassets.linear.app/images/ornj730p/production/23131ce77d756701c51f3e3a36fde416db009675-3600x2160.png?q=95&auto=format&dpr=2) ## Overview Coding sessions let Linear Agent write code using Claude Code or Codex. Delegate a well-scoped issue to Linear, and the agent writes and tests the change in a secure cloud environment, then returns a draft pull request for review. Teammates with repository access can follow progress, add context, steer the approach, and review the diff in Linear. Existing GitHub permissions and review requirements still determine what ships. Use coding sessions to: * Fix well-scoped bugs as they enter triage using [Loops](https://linear.app/docs/loops) * Make contained changes with clear outcomes and constraints * Address review comments, rebase branches, fix lint issues, or add tests * Delegate changes without setting up a local environment > [!NOTE] > Coding sessions are supported on paid plans. Usage draws from your workspace’s AI credits. See [AI credits](https://linear.app/docs/ai-credits) for more information. > > To review coding session spending and manage spend limits, open **Settings → Usage & limits**. Learn more about [usage and spend limits](https://linear.app/docs/usage-and-limits). ## Setup A Linear owner or admin with GitHub organization owner access can enable coding sessions within your workspace by: 1. Navigating into your [GitHub Integration settings](https://linear.app/settings/integrations/github) and granting code access 2. Enabling [Coding sessions](https://linear.app/settings/ai/coding-agent) _If your GitHub organization or services accessed by coding sessions use IP allow lists, allow the Coding sessions IPs listed under GitHub Enterprise Cloud in the [GitHub integration documentation](https://linear.app/docs/github)._ Afterwards, any workspace member with a GitHub account linked in [Connected Accounts](https://linear.app/settings/account/connections) will be able to start a coding session. ## Choose a model Our current default model (tracked under _Auto_) is GPT-6 Sol. The model selected here is used for all subsequent coding sessions in the workspace. Workspace owners or admins can update the model selection from [Coding sessions settings](https://linear.app/settings/ai/coding-agent). We currently support Claude Opus 5.5, Claude Fable 5, Claude Opus 5, Claude Opus 4.8, and Claude Sonnet 5; GPT-6 Sol, GPT-6 Luna, GPT-5.6 Sol, GPT-5.5, and GPT-5.4; and GLM 5.3 and GLM 5.3 Flash. ![Coding sessions model selection](https://webassets.linear.app/images/ornj730p/production/7a592b6d536ee7e96905893333428b232289f56b-1711x906.png?q=95&auto=format&dpr=2) ## Configure coding environments Coding environments let workspace owners and admins configure repository-specific setup for coding sessions. Use them to provide the runtimes, tools, configuration, and instructions the agent needs to work in a particular codebase. To create an environment, go to **Workspace settings → AI & Agents → Coding sessions → Environments**. ### Configure an environment You can configure: * **Runtimes and tools:** Node.js, Python, Ruby, Go, PostgreSQL, and Redis, including specific runtime versions. * **Environment variables:** Use these for required runtime configuration. Names and values are visible to the coding agent and should not be treated as agent-hidden secrets. To add values from a `.env` file, choose **Import from .env**, paste the file contents, and select **Import variables**. Review the imported variables, then save the environment. * **Prepare script:** Run setup commands during environment preparation. * **Files:** Add text files at relative paths in the environment home directory, such as .npmrc. * **Custom guidance:** Provide repository-specific instructions for how the agent should work. * **Agent and model:** Choose an agent and model for the environment. Available options depend on the selected model and workspace configuration. ### Environment secrets Coding environments can securely store credentials for private registries and authenticated services outside your repository. This gives agents access to the private dependencies and services they need to build and test your code. When creating a new environment variable for your environment, check the _Secret_ checkbox to denote this state: ![Environment secrets](https://webassets.linear.app/images/ornj730p/production/b042a8af867c561822c645359190a128032bc7a3-1500x566.png?q=95&auto=format&dpr=2) Environment secrets are not visible to the coding agent by default, but are visible to anyone who can run a session in that environment. Treat them as development-time secrets, like a local .env file, not as values hidden from your team. ### Limitations * An environment contains one repository, and a repository can belong to only one active environment. * Repositories must be available through your workspace's GitHub integration. * Archived environments cannot be used for new coding sessions. ## Start a coding session When 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 autonomously—you'll be notified when your input is needed. When you ask Linear to make a change, Linear Agent starts working right away. That includes direct requests like fixing a bug, implementing a feature, opening a PR, or starting a coding session. If Linear has already offered to handle something, a quick reply like “proceed” is typically enough to begin. ![Collaborate with Linear Agent in a secure coding session](https://webassets.linear.app/images/ornj730p/production/583931386478f7632a8e9c9d841ed8a2cd760f41-2550x1904.png?q=95&auto=format&dpr=2) If you’re asking Linear to look into something first, it won’t start coding yet. Requests to investigate, debug, research, plan, or create the actual task are treated as scoping the problem, not implementing it. The same goes for messages that only say where the work should be tracked, like a team, project, cycle, milestone, or triage. As part of a coding session, Linear Agent can prepare projects that use supported runtimes, including Python, Ruby, Go, Rust, Java, and Node.js, and install dependencies from repository configuration and lockfiles. It can also start local applications, use browser automation to test changes, and capture screenshots or recordings for verification. ## Review code changes When 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. When a session includes verification artifacts, you can review the screenshots or recordings alongside the proposed changes. You 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. ![Inspect Linear Agent's code change in your Reviews tab](https://webassets.linear.app/images/ornj730p/production/f95d33c6f3b7a1d0ffac9f64c9d89c167d674b78-2140x1488.png?q=95&auto=format&dpr=2) ## Guidance and skills Coding sessions work from the issue you delegate and the repository access available to your workspace, and the guidance configured for Linear Agent. Coding 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` file or supported tool-version configuration, Linear Agent can use that context alongside the issue and repository context during a coding session. ### Writing effective issues Coding 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. **Too ambiguous** > Search is broken. > Improve the search experience. > Users can't find archived projects through search., ,This should respect the ,_Include archived_, toggle. --- **Well-scoped** > Issue search excludes issues from archived projects, even when Include archived is enabled., ,, ,Update ,`issueSearch.ts`, so issue search respects the existing ,`includeArchivedProjects`, flag. When enabled, issue search should include issues from archived projects that match the search query. When disabled, existing behavior should remain unchanged., ,, ,Reuse the existing ,`includeArchivedProjects`, filtering behavior used elsewhere in search rather than implementing archived project filtering independently., ,, ,Do not modify search ranking, pagination, or project search behavior. --- The 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. Information that reduces ambiguity or codebase exploration helps Linear reach an implementation faster and use AI credits more efficiently. For more information about AI credits, see [AI credits](https://linear.app/docs/ai-credits). ## Agent automations Once you've enabled coding sessions, the next way to drive efficiency is to kick them off automatically. [Loops](https://linear.app/docs/loops) 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. Internally, 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. ![Triage automations lets you kick-off Linear Agent's implementation automatically](https://webassets.linear.app/images/ornj730p/production/0b9bc1b157109715d3638d94da379768b48d17dc-2210x988.png?q=95&auto=format&dpr=2) ## AI credits Coding 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. Once used, workspace admins can top up AI credits to continue using coding sessions. Please see [AI credits](https://linear.app/docs/ai-credits) for more information.