Skip to main content
← Documentation

Workflow Modes

Workflow Modes

When a ticket comes in, the AI decides which workflow mode to use based on the ticket content. There are four modes, each suited to different types of work.

Full processing

The complete automated pipeline for feature requests, complex bugs, and performance issues.

What happens: The AI analyses the ticket, implements a fix, reviews the code, runs tests, and prepares a pull request for your team to approve.

  • Takes up to 30 minutes
  • Pauses for human approval before creating the pull request
  • Your team reviews and approves all proposed changes

Analysis only

A lightweight investigation for questions, documentation requests, and exploratory issues.

What happens: The AI investigates the codebase and posts its findings as a comment on the ticket. No code changes are made.

  • Takes up to 5 minutes
  • No approval needed (read-only investigation)
  • Useful for understanding how something works or where an issue might be

Quick fix

A streamlined pipeline for simple changes like typos, config tweaks, and obvious bugs.

What happens: The AI analyses the issue, makes the fix, runs relevant tests, and responds on the ticket.

  • Takes up to 10 minutes
  • Only runs tests related to the changed files
  • Best for small, isolated changes

Human only

For work that AI cannot handle, such as design decisions, client meetings, or strategic planning.

What happens: The AI posts a structured comment explaining why this ticket needs human attention and what specific action is needed.

  • Completes in under a minute
  • No code analysis or changes
  • Ensures the ticket is properly flagged for your team

How routing works

The AI reviews each ticket's title, description, and type to decide which mode to use. It considers:

  • What kind of work the ticket describes (bug, feature, question, design, etc.)
  • How complex the issue appears (trivial through to very complex)
  • How urgent it is
  • Whether AI can help or if human involvement is clearly needed

The system defaults to full processing when it is confident the AI can help. It only routes to human-only for work that genuinely requires a person, such as design mockups, client calls, or business decisions.

For safety-sensitive situations (data deletion, security changes, or ambiguous high-risk requests), the system always flags the ticket for human review regardless of the workflow mode.