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

Slack Integration

Interact with DevBoxer directly from Slack

Open as Markdown

@DevBoxer on Slack

To mention @DevBoxer on Slack, you must first connect your Slack workspace in Settings.

How It Works

Mention @DevBoxer in Slack to create new DevBoxer tasks. DevBoxer will kick off a new task with the context of the message and respond with a link to the task created. When used in threads, devboxer will include the thread context as well.

What Happens

When you mention @DevBoxer:

DevBoxer uses the message and thread context to infer the repository for the task

For messages in threads, DevBoxer includes the full thread context.

If needed, DevBoxer uses your configured fallback repository or asks you to choose a repository in Slack

A new task is created automatically with the context of the message

DevBoxer responds with a link to the task created
Work begins in an isolated sandbox

You'll see the task appear in Home

Configuration

After connecting your workspace in Settings, you can configure:

  1. A fallback repository for cases where DevBoxer cannot confidently infer the correct repo from Slack context
  2. The default model for tasks created from Slack

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

GitHub Integration

Interact with DevBoxer directly from GitHub

Linear Integration

Delegate Linear issues to DevBoxer

On this page

@DevBoxer on SlackHow It WorksWhat HappensConfiguration