kryptobaseddev / cleo

CLEO - Contextual Language Engine & Orchestrator CLEO is a comprehensive task management and agent orchestration system designed for AI-powered software development workflows. It provides structured task tracking, session management, memory systems, and multi-provider AI integration through a unified interface. What is CLEO? CLEO stands for **Contextual Language Engine & Orchestrator**. It's built to solve the coordination challenges that arise when working with multiple AI coding assistants across complex software projects. Core Capabilities • **Task Management**: Hierarchical task tracking with dependencies, priorities, and lifecycle states • **Session Management**: Contextual work sessions with automatic state persistence • **Agent Orchestration**: Multi-agent coordination with protocol compliance • **Memory Systems**: Persistent knowledge storage with brain-like retrieval • **Multi-Provider Support**: Works with Claude Code, OpenCode, Cursor, and more • **MCP Server**: Full Model Context Protocol integration for AI assistants Monorepo Structure This monorepo contains 6 packages that work together to provide the complete CLEO ecosystem: | Package | Purpose | Description | |---------|---------|-------------| | | Type Definitions | Domain types, interfaces, and contracts - the foundation of the type system | | | Business Logic | Task management, sessions, memory, orchestration, and lifecycle management | | | Provider Integration | Unified adapters for Claude Code, OpenCode, Cursor, and other AI providers | | | Agent Protocols | Subagent templates and protocol definitions for autonomous execution | | | Skill Definitions | Pre-built skills and capabilities for common development workflows | | | CLI & MCP Server | Command-line interface and Model Context Protocol server | Quick Start Installation Initialize a Project Basic Usage Using the MCP Server CLEO includes a full MCP (Model Context Protocol) server for AI assistants: Development Setup Prerequisites • Node.js >= 24.0.0 • pnpm >= 10.30.0 (package manager) Clone and Install Package Development Database Operations Architecture Overview Key Features Task Management • Hierarchical tasks with parent-child relationships • Priority levels and sizing estimates • Dependency tracking and blocker identification • Automatic sequencing and critical path analysis • Archive and restore functionality Session Management • Contextual work sessions with automatic persistence • Session notes and progress tracking • Safe stop and checkpoint mechanisms • Briefing generation for context handoff Memory Systems • Brain-like knowledge storage with semantic search • Sticky notes for ephemeral context • Memory bridges for cross-session persistence • Context injection for AI assistants Agent Orchestration • Subagent spawning with protocol compliance • Wave-based parallel execution • Consensus workflows for multi-agent decisions • LOOM (Logical Order of Operations Methodology) lifecycle Multi-Provider Support • Claude Code integration with statusline sync • OpenCode adapter with spawn hooks • Cursor support • Extensible adapter architecture Commands Overview CLEO provides 80+ commands organized into domains: | Domain | Commands | |--------|----------| | **Tasks** | add, list, show, find, complete, update, delete, archive, start, stop, current, next | | **Session** | session, briefing, phase, checkpoint, safestop | | **Memory** | memory, memory-brain, observe, context, inject, sync, sticky, note | | **Check** | validate, verify, compliance, doctor, analyze | | **Pipeline** | release, lifecycle, promote, upgrade, specification, roadmap, plan | | **Orchestration** | orchestrate, ops, consensus, contribution, decomposition, implementation | | **Research** | research, extract, web, docs | | **Nexus** | nexus, init, remote, push, pull, snapshot, export, import | | **Admin** | config, backup, skills, migrate, grade, map, commands | Contributing We welcome contributions! Please see our Contributing Guide for details. Development Workflow • Fork the repository • Create a feature branch ( ) • Make your changes • Run tests ( ) • Commit with conventional commits ( , , , etc.) • Push to your fork • Open a Pull Request Code Style • TypeScript with strict mode enabled • Biome for linting and formatting • Conventional commit messages • Comprehensive test coverage with Vitest Documentation • API Documentation • Architecture Guide • Skill Development • MCP Specification Community • GitHub Discussions • Discord Server • Twitter/X @cleocode Support If CLEO helps your workflow, consider supporting development: License MIT License - see LICENSE for details. Star History