For developers

Use Devboxes for a coding task you can describe and verify: fix a reproducible bug, add a focused test, or make a small repository change. The agent works in a container while you keep access to its transcript and diff.

Set up once

Follow the quickstart to connect a repository, create a project, and start a runner. You need an owner or admin role to configure and start runs. For a team with an existing setup, ask which project, blueprint, and model account to use.

Choose a workspace image that contains the tools the repository needs. Open the project's Environment tab and choose Add key for required variables and secrets. Keep credentials out of task instructions.

Write a task the agent can verify

Give the agent the observed problem, the intended result, and the checks to run. Name constraints that matter, such as keeping an API unchanged or avoiding unrelated files.

Fix the CSV export so values containing commas or quotes remain in one field.

Reproduce the issue with a value such as: London, UK
Keep the existing column order and public export function signature.
Add tests for commas, embedded quotes, and empty values.
Run the export tests and report any checks you could not complete.

Use commands that exist in your repository. The example describes a task; it does not assume a particular test framework.

Follow the session

Open the session after dispatch. The Transcript shows the agent's work and requests for input. Review shows the changes available for inspection. Runtime helps you understand execution state, and Session provides context about the work.

Respond to questions with the missing fact or decision. For a follow-up, describe the specific change needed and how you will verify it. Keep related work in the same session when you need its context.

Review before merging

Compare the result with the original task. Read the diff, check what actually ran, and examine failures or skipped checks. A success status reports execution, not an independent approval of the code.

When the workflow produces a pull request, review it through your team's normal process. Repository rules and review requirements still apply.

Work from your terminal

The CLI guide covers sign-in, dispatch, session following, and runner management. The dashboard remains useful for reading the transcript and reviewing a change even when you start the task elsewhere.

For repeated work, blueprints let you define a versioned sequence of steps instead of rewriting the process in every prompt.