Skip to main content

User Guide

The User Guide is for the people who use Ouroboros day to day: you queue issues, shape the workflows that work on them, watch loops run, answer the questions they raise, and merge what they produce. You need a workspace to sign in to — if you are setting one up, deploying the stack or enrolling build-farm runners, start with the Administration section instead, and come back here once you can sign in.

What Ouroboros does​

Ouroboros is an autonomous software delivery loop: issues in, verified pull requests out. It picks up an issue from your tracker, sizes it, works it through a workflow you control, builds and tests the change on your own build farm, checks that the pull request does what the issue asked, and merges it — stopping to ask you whenever a decision is yours to make. What it learns along the way feeds the next loop.

The path through this guide​

Read it in order the first time; after that, jump to the screen you are on.

  1. Concepts — the loop from issue to merged pull request, where you decide, and what dry-run means. Read this first: every other page uses its words.
  2. Getting started — sign in, run the Get Started wizard and watch your first loop.
  3. Finding your way — the sidebar, the workspace switcher and the header.
  4. Feeding the loop — the Mission Control dashboard, Issues (intake, sizing and queuing) and Planning (turning prose into tickets).
  5. Shaping the work — Workflows on the canvas or as code, and Models (which model does which kind of work).
  6. Following a loop — the run console, test results and pull request verification.
  7. Deciding — the Needs-you inbox, where every question a loop is blocked on waits for your answer.
  8. Getting better — Insights, the Build Analyzer and Knowledge (skills, learned facts and playbooks).

Meet a word you do not know? The Glossary lists every term with a link to the page that explains it.

What this guide covers​

Every page describes what Ouroboros does today. Where the app shows a surface that has not arrived yet — a sidebar row marked soon, or a note saying a feature "arrives with" a later release — the page says so in one line and does not describe it as working.