DevBoxerDevBoxer Docs
DevBoxerDevBoxer Docs
Back to App

Introduction

WelcomeQuick StartCommon Workflows

Using DevBoxer

Tasks
AutomationsGitHub IntegrationSlack IntegrationLinear IntegrationDevBoxer CLI & MCPMobile

Agents

Claude CodeOpenAI CodexOpenCodeGemini CLIAmp

Configuration

Environment Setup
MCP SetupCustom System PromptsGit Checkpointing

Help & Resources

Get HelpCommon IssuesBilling OverviewPrompt ExamplesEarly access featuresRelease NotesTerragon ShutdownSecurity & PermissionsDevBoxer App

Linear Integration

Delegate Linear issues to DevBoxer

Open as Markdown

Delegate Linear issues to DevBoxer by connecting your Linear workspace and routing issues into tasks automatically.

Setup

A DevBoxer organization admin must connect Linear in Settings. You can optionally configure a fallback repository for cases where DevBoxer cannot confidently infer the correct repo from the issue.

After connecting Linear, your org admin can also choose the default model DevBoxer should use for Linear-created tasks.

How It Works

Assign an issue to DevBoxer or mention DevBoxer in a Linear comment to create a task automatically.

Assign the Linear issue to DevBoxer to kick off a new task.

Add a comment asking DevBoxer to work on the issue. DevBoxer uses the issue context and your latest prompt when creating the task.

What Happens

When Linear sends a request to DevBoxer:

DevBoxer tries to infer the best repository from the Linear issue context
If needed, DevBoxer falls back to your configured repository or asks you to choose a repository in Linear
Issue details and prompt context are included in the task automatically
Work begins in an isolated sandbox

Linear gets a link back to the DevBoxer task in Home

As work progresses, DevBoxer posts status updates back to Linear and adds the pull request link when one is available

Follow Ups

Additional prompts from the same Linear agent session are added to the existing DevBoxer task as follow-up messages, so the work stays in one thread instead of creating duplicates.

If you stop the session in Linear, DevBoxer stops the linked task as well.

Configuration

Linear tasks currently use:

  1. Repository inference based on the Linear issue context
  2. The fallback repository configured in Settings, if you set one
  3. The default model configured for the Linear integration
  4. Your usual DevBoxer organization permissions and repository access

If no default model is configured for Linear, DevBoxer falls back to the installer's default model selection.

If DevBoxer cannot confidently choose between multiple repositories, it asks you to pick one in Linear before starting the task.

If no writable repositories are available for the integration user, DevBoxer will not start the task and will report the setup error back to Linear.

Having issues with Linear integration? See Common Issues or Get Help.

Slack Integration

Interact with DevBoxer directly from Slack

DevBoxer CLI & MCP

Command-line interface for interacting with DevBoxer that can also be used as an MCP server

On this page

SetupHow It WorksWhat HappensFollow UpsConfiguration