Hand coding work to a cloud coding service

What this does for you

A bot can pass coding work to a cloud coding service (today, Devin) instead of doing it itself. The service works on its own, and you follow the job in the chat you started it from: its status, the files it produced, and each pull request it opened with whether it has been merged.

Point a bot at a coding service

1. Open the bot that should do the coding work, and open its settings.
2. In the Coding agent card, choose the service under Served by. The list only shows services your deployment has a credential for; if it says there is none, ask whoever runs your Botseon.
3. From now on, when another of your bots hands this bot a task, a job starts at the service.

To make the bot answer with its own model again, choose None: this bot answers with its model. Its other model settings are kept. Only the bot's owner can change this.

This hand-off is on by default, with no approval step. In a team organisation an admin can switch it off (Organisation, Policies, Delegate to coding agents). While it is off, the card says an admin turned it off and offers no service to choose, and a hand-off to a bot already pointed at one is refused with a sentence saying so. Going back to the model always works. A people group the admin set up can let its members past the switch.

Follow and cancel jobs

• In the chat you delegated from, a card shows the job and updates while the service works: Starting, Working, Waiting for input, Finished, Failed or Stopped, its files, and each pull request as Open, not merged yet, Merged or Closed without merging. After the work finishes, the card keeps following until every pull request is merged or closed.
• The coding bot's Coding jobs list shows every job handed to it that you can see, newest first: its status, each pull request with its merge state, a link to each file the work produced, and Open the job to see it at the service.
• Cancel job stops a job that has not ended. Botseon asks the service to end the session (within a minute); the job and its card then read Stopped, and the bot that handed it over is told the work was cancelled.

Limits

• Jobs are followed for about a week; a pull request still open after that is yours to chase.
• The service sees only the task your bot wrote, not your conversation.
• Cancelling stops the work, not the pull requests already opened: close those at your code host.