Request work from chat

Devboxes supports chat integrations for Slack, Microsoft Teams, and Google Chat. Connection and channel setup differ by platform; use the instructions shown for the selected integration in Credentials.

Configure the channel before using it

An owner or admin connects the integration and assigns the projects available to an exact channel. The connection alone is not an unrestricted route to every project.

Channel configuration grants execution authority through the configuring owner or admin. Anyone allowed to post in that configured channel, including another app, may be able to request work through it. Manage chat membership and app access accordingly. See the Slack guide for a concrete setup path.

Make a useful request

Mention Devboxes with the result you need and enough repository context to select the intended project. Keep the work bounded and supply required blueprint inputs when requested.

@devboxes fix the CSV export bug in the reporting project.
Values containing commas must remain in one field. Add a regression test
and report which checks you ran.

The projects, blueprints, and model access configured for that channel determine what it can run. A message in another channel does not inherit the same authorization.

Follow the response

Read the routing response before posting the task again. A request can need clarification or fail its setup checks before a run exists. Once a run is created, follow its status and session link.

A shared session view may be read-only and have a different access boundary from the private dashboard. Treat links as sensitive where they grant access to the conversation.

Change or remove access

Review channel assignments when people, apps, or project responsibilities change. Removing an integration or channel assignment affects future access; it does not undo work already published to a repository or another service.