Ouroboros

English | 한국어 | 简体中文

◯ ─────────── ◯

O U R O B O R O S

◯ ─────────── ◯

It gets smarter on its own. We just hold the line.

Skip the prompt engineering. The agent runs, fails, and gets smarter every generation. The grading command and expected result never make it into the success contract we hand it.

The Agent OS for replayable AI coding workflows

Quick Start · Why · Results · How It Works · Commands · Philosophy · Guide

# macOS / Linux / WSL 2

curl -fsSL https://raw.githubusercontent.com/Q00/ouroboros/main/scripts/install.sh | OUROBOROS_INSTALL_REF=readme-hero bash

# Windows (PowerShell) — no Python needed; installs Git and uv for you

irm https://raw.githubusercontent.com/Q00/ouroboros/main/scripts/install.ps1 | iex

One command installs it. Then run ooo setup once inside your coding agent — details in Quick Start .

Demo videos for each runtime.

Terminal CLI — a task-management CLI: ouroboros init start asking about ordering and scope, then reporting an ambiguity score

ChatGPT (Codex) — called as an integration, on a video-publishing harness: the interview, its advisory lanes, and the ambiguity ledger

Claude Code — a YouTube automation task, with the six advisory lanes running in parallel before the interview submits

Hermes (Discord) — a kart-racing game, run as a chat bot, ending at Final ambiguity: 0.15

DeepSeek Harness — an OSS-trend outreach script, driven from a dsh chat: mcpouroborosouroboros_interview turn by turn, fan-out results submitted between rounds

Kiro — the Kiro CLI running the Ouroboros interview flow, turning a vague request into a structured, testable Seed

Antigravity — a YouTube-publishing automation interview: asks what to automate, shows advisory lanes, and submits the selected answer

Turn a vague idea into a verified, working codebase -- across Claude Code, Codex CLI, OpenCode, Hermes, Gemini, Kiro, Copilot, Pi, OMP, Zcode, Goose, GJC, Antigravity, and Grok.

Ouroboros is an Agent OS for AI coding: a local-first runtime layer that turns non-deterministic agent work into a replayable, observable, policy-bound execution contract. It replaces ad-hoc prompting with a structured specification-first workflow: interview, crystallize, execute, evaluate, evolve.

---

The Ouroboros Agent OS Stack

Like any OS, Ouroboros is split into a stable OS layer of primitives, an application layer of domain workflows, and a shell that humans actually sit in front of. Three repos, one stack:

How they connect:

  ourocode  ──►  ooo / ouroboros-plugins  ──►  ouroboros core (Seed · Ledger · MCP · Runtime)

shell user-level apps kernel

• The kernel (ouroboros) owns the contract: every action becomes a Seed-bound, ledger-recorded, replayable event — regardless of which LLM executes it.
• Plugins (ouroboros-plugins) declare scoped capabilities against that contract, so domain workflows (review a PR, triage a Linear ticket, run a release) stay auditable and policy-bound instead of being one-off prompts.
• Ourocode is the terminal shell: it surfaces MCP state, interview questions, and wonderTool decisions as first-class TUI elements, so you can drive the OS without leaving the keyboard or switching between CLIs.

Use ouroboros alone with any supported CLI, layer plugins on for domain workflows, or install ourocode when you want a unified terminal cockpit.

Disclaimer. The Ouroboros project and community are **not affiliated with

any cryptocurrency, token, memecoin, or trading community** — including, but

not limited to, any "ouroboros" tickers on pump.fun or other launchpads. This

is an open-source developer tool. We do not issue, endorse, or hold any

coins. Any token claiming association with this project is unauthorized.

Naming note. A separate, unaffiliated open-source project also uses the

name "Ouroboros" — Anton Razzhigaev's self-modifying, autonomous-memory agent

at github.com/razzant/ouroboros. No shared code, no relationship. This

project locks a specification before executing rath