Choose the autodev mode

A project’s autodev mode decides what SupaCloud does with the project’s issues — leave it alone, work each one as it arrives, or run a prioritised backlog. The mode lives in the project’s Automation section, alongside an independent PR-review lane and a classifier. This page covers picking the mode, turning on the lane, and configuring the classifier.

Note

For the model behind these controls — how the modes, the lanes, the severity gate, approval mode, autonomy and the blast radius compose — see Automations.

Pick the mode

1. Open the project, then open its Edit modal and find the Automation section.
2. Set the autodev mode:
   • Off — issues are imported but nothing is dispatched.
   • Simple — each new issue is worked directly to a pull request, in arrival order (first in, first out).
   • Backlog — issues are classified and prioritised, then dispatched in priority order, bounded by the autonomy level, the concurrency caps and the budget.
3. Save.

Issues are always imported

The mode never affects import: SupaCloud always imports the project’s open issues from every connected source — the Git forge, Linear and Notion. The mode only governs whether and how those issues are dispatched to an agent. Pick which sources a project reads in its Issue tracker section.

Simple and Backlog both run the same scan → classify → dispatch pipeline. The only difference is the order work is picked off the queue: Simple takes the oldest queued issue first; Backlog takes the highest-priority one.

Choose which agents do the work

The backlog and simple modes hand each item to an agent. The Work agents control in the Automation section decides how that agent is picked:

• Single agent — one fixed agent type works every item. This is the default and is unchanged for existing projects.
• All agents — the auto-selection router picks the best agent per item across every agent you have connected. An agent you connect later is included automatically, with no reconfiguration.
• Selected agents — the router picks per item from a set of agent profiles you choose. An agent whose provider has no key is greyed out; add a key in Settings to make it selectable.

Which agent the router picked for each item is shown on the Auto Agent / Models page.

Turn on the orthogonal PR-review lane

The autodev mode is about the project’s own issues. A further automation reacts to events and is independent of the mode:

• PR-review runs the auto-developer over an incoming pull request.

A Backlog project can also review pull requests; turning the lane on does not change the mode. (Multi-model council deliberation is no longer a standalone issue-debate lane — it is a per-stage option on the backlog and PR-review arms; see Automations.)

Configure the backlog classifier

When the mode is Backlog, a classifier tags each imported issue before it is dispatched. Set it in the Automation section.

1. Choose the classifier variant:
   • Rules — fast and deterministic, driven by the issue’s labels, title and body. Needs no model or credential.
   • LLM — a model classifies the issue.
2. For the LLM variant, set:
   • the model (from the live model catalog — every model is listed, and a model whose provider has no key is greyed out with a link to add one);
   • the system prompt the classifier runs with;
   • the categories (one per line) it may assign.
3. Save.

The classifier sorts each issue along three axes — its kind, a priority that maps to a severity, and a scope (small, medium, large). Priority orders the backlog queue; severity sets a floor on the routing effort; scope nudges the effort up for a large change and down for a small one.

See also

• Automations
• Run the backlog
• Set the autonomy level