Ouro is derived from Ouroboros—the ancient symbol of a serpent consuming its own tail to form a perfect circle. It represents the ultimate cycle: a closed loop of self-consumption, constant renewal, and infinite iteration.
At Ouro AI Lab, this is our blueprint. We are building the next generation of AI agents capable of autonomous evolution—systems that learn from their own outputs, refine their own logic, and achieve a state of infinite self-improvement.
Two Modes, One Agent
Ouro ships with a unified agent core and two deployment modes:
| CLI Mode | Bot Mode | |
|---|---|---|
| What | Interactive REPL + one-shot task execution | Persistent IM assistant (Lark, Slack) |
| Install | uv tool install ouro-ai |
uv tool install ouro-ai |
| Run | ouro-cli |
ouro-bot |
| Guide | CLI Guide | Bot Guide |
Architecture
Ouro is organized into three layers with strict downward-only imports:
Each layer has its own README — start with the umbrella overview, then drill into core, capabilities, or interfaces.
Features
🤖 Agent Swarm — Multi-Agent Swarm with Persistent Tasks
The flagship feature. Enable with ENABLE_AGENT_SWARM=true in ~/.ouro/config.
- Persistent Task Store — SQLite-backed tasks with dependency graphs (
task_create,task_claim,task_update,task_list,task_get,task_delete) - Atomic Task Claiming — Agents race to claim available tasks; one agent, one in-progress task
- Auto-Swarm — Complex tasks are automatically decomposed and executed by multiple agents in parallel
- Replaces legacy
TodoToolandMultiTaskToolwhen enabled
🔄 Self-Verification — Ralph Loop
The agent verifies its own answer against the original task and re-enters the loop if incomplete. Enable with --verify or RALPH_LOOP_MAX_ITERATIONS=3.
🧠 Memory System
LLM-driven compression, file-based long-term memory, FTS5 conversation recall, and YAML session persistence resumable across restarts.
💬 Dual Deployment
Same agent core, two modes:
- CLI — Interactive REPL with rich TUI, slash commands, session resume
- Bot — Persistent IM assistant for Lark, Slack, WeChat with proactive cron scheduling
🔐 OAuth Login
--login / /login to authenticate with ChatGPT Codex subscription models.
📊 Benchmarks
First-class Harbor integration for agent evaluation (see Evaluation).
Quick Start
Prerequisites: Python 3.12+ and one of uv (recommended) or pipx.
# Recommended: installs ouro in an isolated environment and exposes global
# `ouro-cli` and `ouro-bot` commands
uv tool install ouro-ai
# Alternative
pipx install ouro-ai
# Upgrading later
uv tool upgrade ouro-ai # or: pipx upgrade ouro-ai
Plain
pip install ouro-aialso works but is not recommended — it mixes ouro's dependencies into your active Python environment. Useuv tool/pipxso theouro-cli/ouro-botbinaries are on$PATHwithout needing to activate a venv.
On first run, ~/.ouro/models.yaml is created. Add your API key:
models:
openai/gpt-4o:
api_key: sk-...
default: openai/gpt-4o
current: openai/gpt-4o
Then run:
# Interactive mode
ouro-cli
# Single task
ouro-cli --task "Calculate 123 * 456"
# Bot mode
ouro-bot
See LiteLLM Providers for the full provider list.
Evaluation
Ouro can be evaluated on agent benchmarks using Harbor. A convenience script harbor-run.sh is provided at the repo root:
- Edit
harbor-run.shto set your model, dataset, and ouro version. - Run:
export OURO_API_KEY=<your-api-key>
./harbor-run.sh # run with defaults in the script
./harbor-run.sh -l 5 # limit to 5 tasks
./harbor-run.sh --n-concurrent 4 # 4 parallel workers
Extra flags are forwarded to harbor run, so any Harbor CLI option works. See ouro_harbor/README.md for full details.
Documentation
- CLI Guide -- interactive mode, task mode, commands, shortcuts
- Bot Guide -- IM bot setup, commands, proactive mechanisms, personality
- Configuration -- model setup, runtime settings, custom endpoints
- Examples -- usage patterns and programmatic API
- Sandbox Providers -- BoxLite/smolvm sandbox tools and configuration
- Memory Management -- compression, persistence, token tracking
- Task V2 -- persistent task store with dependency graphs (Phase 1)
- Extending -- adding tools, agents, LLM providers
- Packaging -- building, publishing, Docker
Contributing
Contributions are welcome! Please open an issue or submit a pull request.
For development setup (install from source):
git clone https://github.com/ouro-ai-labs/ouro.git
cd ouro
./scripts/bootstrap.sh # creates .venv and installs editable + dev deps
source .venv/bin/activate
./scripts/dev.sh check # precommit + typecheck + tests
End-users should prefer uv tool install ouro-ai (see Quick Start); the source checkout is only needed when contributing.
License
MIT License
Metadata
Release files for ouro-ai 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ouro_ai-0.5.3.tar.gz | 379.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ouro_ai-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 735.6 kB
Release files / ouro_ai-0.5.3.tar.gz
| Download URL | ouro_ai-0.5.3.tar.gz |
|---|---|
| Size | 379.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c33921d42e2480b425feb498baa8475728af002f0954d55a1f1b0f6bd9e102c5
|
|
BLAKE2b-256 checksum How to use checksums |
ed3c71b49e7a7f98bd8aee02cc8c2cff481b362542fe3a638518eeb988a45d49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logRelease files / ouro_ai-0.5.3-py3-none-any.whl
| Download URL | ouro_ai-0.5.3-py3-none-any.whl |
|---|---|
| Size | 355.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
981c4e5b9773e5f86663f5e02000d25a5e39b616170fd419a9879101738ae4f9
|
|
BLAKE2b-256 checksum How to use checksums |
9635e06504243af9e40818debb1e20d409803e81cda44aa0a51319e11a562747
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency log