Ouroboros Self-Reflective Metaprogramming & Repair Engine

@q00/ouroboros · v2.0.0

A recursive self-reflective metaprogramming engine for DeepSeek Harness. Delivers runtime loop detection, automated compilation error recovery, and self-healing test-driven development (TDD).

Self-RepairTDDMetaprogrammingDebugging
GitHub Stars
42 K+
+12.4% this month
Monthly Downloads
156 K+
Monthly registry pulls
Reach Score
98.7/ 100
Top Tier Ecosystem
Runtime
Cordis v3+
Node 18+ / Bun / Deno

Installation & Integration

CLI one-click launch, package managers, and Cordis integration

bash
manager:
$ pnpm add @q00/ouroboros

Architecture

Ouroboros Evolution gives autonomous agents the resilience to diagnose and repair their own mistakes. Even the most capable LLMs generate code with occasional syntax mistakes, failing test assertions, or subtle library version conflicts. This plugin implements a self-reflective TDD feedback loop on top of Cordis. When a sandbox execution fails, Ouroboros captures the compiler stack trace and failing test names, isolating the exact failure boundary. It prompts the model with targeted diagnostic diffs, iterating systematically until all test suites turn green.

Architectural Principles & Constraints

01
Strict Type Isolation

Guaranteed by TypeScript compile-time contracts, inter-plugin event bus calls enjoy zero-drift safety.

02
Sub-Millisecond Hot Reload

Supports dynamic runtime mounting and graceful unloading without restarting the primary host process.

03
Deterministic State Machine

Embeds multi-phase execution lifecycle guards, preventing context loss during long-horizon reasoning.

04
Zero Native Build Dependencies

Designed for lightweight cross-platform environments, booting instantly across Node.js, Bun, and Deno.

Core Features

01
Automated TDD Self-Healing: Uses green unit tests as the objective standard for success
02
Stack Trace Distillation: Prunes verbose runtime noise to present only fatal fault lines
03
Reflection Loop Hard Cap: Enforces max attempt thresholds to prevent infinite retry loops
04
Fix Pattern Memorization: Automatically records successful repairs into long-term memory

Core Workflow

01

Execution Fault Capture

Captures compiler errors, unhandled rejections, and failing test assertion stacks.

02

Root-Cause Boundary Isolation

Filters noise to isolate exact source file line numbers causing the failure.

03

Hypothesis & Patch Synthesis

Agent reasons through the error trace and generates a minimal refactoring patch.

04

Sandbox Regression Re-run

Re-executes test suites in the sandbox until all assertions pass cleanly.

Configuration Parameters Reference (YAML / JSON)

ParameterTypeDefaultDescription
maxRepairAttemptsnumber5Maximum repair iterations allowed per failure
autoCommitOnSuccessbooleantrueAutomatically commit git diff when tests pass
testCommandstringnpm testCommand executed to verify bugfix assertions

Use Cases

Enterprise Production Agent

Relies on microkernel lifecycle guards and fault-tolerant state machines for continuous reliability.

SWE-bench Benchmark Evaluation

Native integration with SWE-bench workflows, automatically capturing diffs and verification metrics.

Autonomous Code Refactoring

Separates reasoning from tool actions to independently locate and refactor multi-file codebases.

Cross-Tool Workflow Automation

Safely orchestrates events across sandboxes to seamlessly link enterprise developer tooling.

Best Practices

01
Sandbox Permission Guard

Strictly isolate sub-process calls and network scope; deploy within Docker containers in production.

02
Exponential Backoff Retries

Configure adaptive exponential retries with strict timeouts to mitigate upstream model rate limits.

03
Session State Checkpointing

Persist state machine snapshots to survive hardware interruptions and resume instantly without loss.

04
Full Trajectory Audit Logs

Enable full trace logging, aggregating reasoning thought streams and tool I/O into your observability hub.

FAQ

Q1:How to handle timeouts in long-running autonomous tasks?

Increase the timeout parameter inside your YAML configuration and dispatch periodic heartbeat signals across the Cordis event bus. For long-running tool execution and model reasoning, configure persistent session snapshotting so suspended tasks can safely resume their exact context after interruptions, preventing the kernel from recycling active agent sessions prematurely.

Q2:How to capture and stream the model reasoning thought process?

The harness runtime natively provides end-to-end streaming hooks while its state machine automatically intercepts and strips <think> reasoning tags from model responses. Subscribe directly to the onThink event listener to consume live reasoning token streams in real-time, delivering typewriter animation to the user interface while persisting full trajectories for audit compliance.

Q3:How to resolve dependency conflicts across multiple plugins?

Cordis microkernel uses directed acyclic graph topological sorting to dynamically resolve plugin dependencies. When shared services or runtime versions conflict, assign distinct isolated namespaces at the application entrypoint. Leveraging context injection alongside lazy activation ensures dependencies load strictly on-demand when tools are triggered, maintaining system stability and preventing memory bloat.

Q4:How to enforce permissions and sandbox isolation in production?

Combine isolated container sandboxing with fine-grained capability checks to prevent plugins from accessing sensitive files or unauthorized external networks. Enforce explicit runtime system call whitelisting through the microkernel, executing all third-party tool scripts inside isolated ephemeral containers to block arbitrary code execution and eliminate security privilege escalation risks entirely.

Recommended Ecosystem Plugins

Explore related Cordis extensions designed to work synergistically