Introduction

What Reqursor Development is, how its pipeline works, and what this documentation will cover.

Reqursor Development is a self-hosted AI development agent. You install it on your own server or a Raspberry Pi 5. Your developers write tickets with clear acceptance criteria; the agent picks them up from the queue, implements them in your repository, and ships a change only when your own checks pass and every acceptance criterion is backed by evidence.

When a ticket can't be shipped, nothing is committed. Instead you get an escalation report that explains what was tried and why it stopped, so a person can decide what happens next.

How a ticket moves through the pipeline

Implement

The agent writes the change in your repository, in a fresh session of its own.

Checks

Your build, lint, typecheck and tests run as hard gates, together with built-in scans. Any failing check vetoes the ship.

Review and verify

An AI reviewer returns a structured verdict that cites file and line evidence for every acceptance criterion. An independent verifier, in a fresh session that never saw how the code was written, re-checks the diff against the ticket.

Security

The change is scanned for security issues. Low-risk findings are fixed automatically and re-checked.

Ship or escalate

If everything passes, the change is committed to your working branch or opened as a pull request. If not, you get an escalation report instead of a broken commit.

Where to go next