You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add WorkQueueOps and BatchOps doc pages under design patterns #22001
We need "WorkQueueOps" and/or "BatchOps" pages to discuss the various ways to approach work queues and batching.
Approaches to work queues and planning
use an issue with a checklist of all the work to be done. Use "update-issue" to indicate progress. Linear only, parallelization will almost certainly result in conflicts and repeated work.
use an Epic issue with linked sub-issues. Can be parallelized to some degree, e.g. by closing out issues independently
use cache memory or repo memory to track work
use a discussion with comments saying what has been completed and what to work on next. Again probably linear only, hard to parallelize without conflicts and duplication
other ideas?
Approaches to batching
Operations on issues like labelling are often lightweight and can often be done in batches
Best to have traditional YAML workflows collect up work and add them to a work queue, and then trigger an agentic workflow to process it when enough work is collected, or a time limit has been hit.
Activity
dsyme commentedon Mar 20, 2026
@pelikhan @mnkiefer Can you add further thoughts on this please? Anything you think on these topics.
pelikhan commentedon Mar 20, 2026
Batching lets you control costs and prevent high frequency events to be abused. You can use sub agents internally to process individual items.