Burst mode

Some jobs are many small jobs: research ten companies, review twenty files, draft one email per customer. Burst mode splits a job like that into parts, runs them at once in threads of the bot's own, and writes one result when they are done.

Start a burst

Type /burst in a bot's chat, followed by the job (for example /burst compare these four vendors on price and support). The bot lists the parts it would run and shows a card first; nothing runs yet. The card says:

• how many tasks there are, which model runs them, how many run at once, and about how long it will take;
• the first few tasks, with +N more for the rest.

Choose Run to start it, Edit to change the instructions every task gets or the list of tasks (one task per line), or Cancel.

While it runs

The card becomes the burst's progress: how many are done, running, waiting and failed. Show tasks lists every part, and each part opens as its own thread. The parts are listed under the card, not on their own in the bot's threads, unless one needs you or is working. Cancel all stops the parts still running; Retry failed runs the failed ones again.

When every part has finished, the bot writes one result from them in the chat where you started the burst. A part that did not finish is named on the card with the reason.

How much runs at once

When the bot proposes more tasks than the plan runs in one burst, the card says how many will run. On the desktop app or a server you run, burst.maxParallel in config.json changes how many run at once.