DevBoxerDevBoxer Docs
DevBoxerDevBoxer Docs
Back to App

Introduction

WelcomeQuick StartCommon Workflows

Using DevBoxer

Tasks
Creating TasksManaging TasksTask Follow-upsSlash CommandsDraft TasksScheduled TasksRetry Tasks
AutomationsGitHub IntegrationSlack 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 NotesSecurity & PermissionsDevBoxer App

Tasks Overview

Tasks in DevBoxer

Open as Markdown

What are Tasks?

Tasks are the core unit of work in DevBoxer:

  • Each task runs in its own sandbox
  • Each task is scoped to a specific git repository and branch
  • Each task is assigned to a single agent

You can think of a task as a conversation with an Agent with access to a specific repository and branch. The agent will be able to plan, edit and verify the changes it makes to the repository.

Different ways to create a task

Tasks can be created in a few different ways:

  • Run a task immediately from the dashboard
  • Schedule a task to run at a specific time in the future
  • Retry an existing task with a new prompt
  • @devboxerhub in a GitHub issue or pull request
  • @devboxer in a Slack message
  • devboxer create via the CLI
  • An Automation in response to a predefined event (eg. Pull Request Code Reviews, Issue Triage, etc.)

Common Workflows

Tips for using DevBoxer effectively

Creating Tasks

Create coding tasks in DevBoxer

On this page

What are Tasks?Different ways to create a task