⚡ KURO 2.0 (kurocode)
The Autonomous, Local-First AI Terminal Assistant & Operating System Copilot
KURO is an autonomous desktop terminal agent designed to think, plan, execute, verify, heal, and evolve directly on your machine. Unlike passive AI chat widgets, KURO has hands: it compiles code, executes shell commands, inspects live PC telemetry, captures screenshots, automates browsers, heals its own errors, and installs plug-and-play tools on the fly.
Key Features • Architecture • Quickstart • CLI Orders & Slash Commands • Security & Vault • Self-Healing & Evolution • KuroHub
🚀 Key Features
🏛️ System Architecture
KURO 2.0 separates presentation, orchestration, domain capabilities, and storage into clean, decoupled layers:
graph TD
User([User / Developer]) -->|CLI Input / Slash Command| CLI[CLIAdapter / REPL]
CLI -->|CoreEvent / InputRequest| IOBus[core.io_bus.IOHost]
IOBus --> Agent[core.agent.KuroAgent]
subgraph Core Intelligence & Routing
Agent --> Router[core.model_router.ModelRouter]
Agent --> Context[core.context_engine.ContextEngine]
Router -->|Task-Aware Model Selection| LLM[core.llm.ask_llm]
LLM -->|Provider Fallback & Key Pool Rotation| Providers[Gemini / Groq / OpenRouter / OpenAI / Ollama]
end
subgraph Execution & Security Perimeter
Agent --> Parser[Safe JSON Action Parser]
Parser --> Gate{core.permissions.check_permission}
Gate -->|CONFIRM in SAFE_MODE| Prompt[Interactive User Prompt]
Gate -->|SAFE or Allowed| Sandbox[core.sandbox.SandboxGuard]
Sandbox -->|AST Check Passed| Tools[Tool Execution Registry]
end
subgraph Tools & Capabilities
Tools --> FSTools[Files & Diffs]
Tools --> Shell[System Shell & Telemetry]
Tools --> Vision[Screen Grab & Image Vision]
Tools --> Web[Headless Browser & Playwright]
Tools --> Store[Store & Dynamic Tools]
end
subgraph Verification & Self-Healing
Tools --> Verif[core.verification.VerificationEngine]
Verif -->|Check Failed| Heal[healing.SelfHealingEngine]
Heal -->|Auto-Pip / Rollback / Dir Fix| Tools
end
subgraph Persistence & Evolution
Agent --> MemoryDB[(SQLite brain/kuro.db)]
Agent --> Vault[(Encrypted Vault DPAPI / AES)]
Agent --> Evolution[evolution.EvolutionEngine]
Evolution -->|Ledger Commit| EvoLedger[evolution_history.json]
end
⚡ Quickstart & Installation
Prerequisites
- Python: 3.10, 3.11, 3.12, or 3.13
- Git: Installed and available in PATH (for automatic checkpointing)
- OS: Windows (optimal, full DPAPI vault), Linux, or macOS
✅ Option 1 — Install from PyPI (Recommended)
pip install kurocode
That's it. After install, run:
kuro
PyPI releases are published automatically on every tagged GitHub Release using OIDC Trusted Publishing — no manual token management required.
🛠️ Option 2 — Install from Source (for contributors & developers)
# Clone the repository
git clone https://github.com/kurolabs-ai/KuroCodeAgent.git
cd KuroCodeAgent
# Create and activate a virtual environment
python -m venv .venv
# Windows:
.venv\Scripts\activate
# Linux / macOS:
source .venv/bin/activate
# Install in editable mode (changes take effect immediately)
pip install -e .
Then launch with:
kuro
🔑 Configure API Keys
You have two options — pick whichever suits your workflow:
Option A — Interactive Vault (Recommended)
Launch KURO and save keys directly into the encrypted vault:
kuro
# Then inside the KURO terminal:
/key gemini AIzaSyYourGeminiApiKeyHere
/key groq gsk_YourGroqApiKeyHere
Keys are encrypted with Windows DPAPI (or AES-256 on Linux/macOS) and never stored in plaintext.
Option B — .env File
Create a .env file in your working directory (or project root):
# Primary LLM Providers
GEMINI_API_KEY=your_gemini_api_key_here
GROQ_API_KEY=your_groq_api_key_here
OPENROUTER_API_KEY=your_openrouter_api_key_here
OPENAI_API_KEY=your_openai_api_key_here
# Agent Execution Tuning
KURO_PROVIDER=gemini
KURO_MAX_STEPS=10
KURO_SAFE_MODE=true
KURO_GIT_CHECKPOINTS=true
💻 Operating Modes
Interactive REPL Mode
Experience the complete terminal interface with dark themes, autocomplete, syntax highlighting, and live spinners:
kuro
# or
python main.py
Headless Single-Shot Mode
Execute single commands directly from CI/CD pipelines, background scripts, or terminal workflows:
# Direct task execution
kuro "Analyze the git status and list modified files"
# Output structured JSON for automation
kuro --json "Check database schema and table names"
🎮 CLI Orders & Slash Commands
KURO's interactive terminal REPL provides a streamlined, clutter-free Tab menu containing essential system, security, KuroHub, and skill commands:
┌────────────────────────────────────────────────────────────────────────┐
│ KURO 2.0 COMMAND CENTER │
└────────────────────────────────────────────────────────────────────────┘
⚙️ System & Configuration
| Command | Usage / Example | Description |
|---|---|---|
/status |
/status |
Displays active provider, model, loaded key counts, Safe Mode, and checkpoint status. |
/system |
/system |
Displays live hardware telemetry: CPU logical cores, RAM utilization, and disk storage stats. |
/top |
/top [limit] |
Scans active operating system processes ordered by memory footprint. |
/safe |
/safe <on|off|toggle|allow <tool>|clear> |
Configures permission gate. /safe on requires approval for file writes; /safe allow run_command whitelists a tool. |
/pool |
/pool |
Displays live multi-key pool rotation status, active keys, and HTTP 429 rate-limit cooldown timers. |
/models |
/models [provider] |
Displays priority fallback model chains for the active provider. |
/key |
/key [provider] <KEY> |
Securely saves an API key to the active provider pool and commits it to the encrypted vault. |
/undo |
/undo |
Rolls back the last automated file changes using Git stash checkpoints. |
!<cmd> |
!git status or !dir |
Direct Shell Bypass: Executes locally in OS shell without calling LLM. |
🧩 KuroHub & Capabilities
| Command | Usage / Example | Description |
|---|---|---|
/hub |
/hub [list|search <q>|install <item>|remove <item>|info <item>|update] |
Browse and manage capabilities in KuroHub (tools, plugins, skills, integrations). |
/store |
/store [list|search <q>|install <item>|remove <item>|info <item>|update] |
Alias for /hub store manager. |
/skills |
/skills |
Lists all installed and self-learned procedural skills in skills.json. |
/<skill> [prompt] |
/<skill-name> <custom instructions> |
Directly executes an installed procedural skill with LLM guidance and parameters. |
/plugin |
/plugin [list|install <source>|remove <name>] |
Manages modular plugins (installed as complete folders into plugins/). |
/integrations |
/integrations [connect <service> <token>|disconnect <service>] |
Manages external service bridges (Telegram, Discord, GitHub, Google Drive). |
🧠 Memory, Vault & Session
| Command | Usage / Example | Description |
|---|---|---|
/vault |
/vault [status|list|set|get|delete|lock|unlock] |
Manages Windows DPAPI / AES-256 encrypted credential vault. |
/memory |
/memory |
Inspects stored episodic conversation memories and context summaries from SQLite. |
/clear |
/clear |
Clears active conversation memory for a clean workspace. |
/help |
/help |
Displays the categorized command reference. |
exit / quit |
exit or quit |
Terminates the active KURO session. |
Autonomous Execution: Capabilities such as web searching, headless browsing, multimodal image inspection, code execution, planning, note taking, and self-healing error recovery are orchestrated autonomously by Kuro without cluttering the slash menu.
🔒 Security, Sandboxing & Vault
KURO adheres to a strict principle of least privilege:
┌────────────────────────────────────────────────────────┐
│ KURO SECURITY PERIMETER │
├────────────────────────────────────────────────────────┤
│ 1. Central Permission Gate │
│ • Actions classified: SAFE, CONFIRM, DANGEROUS │
│ • Destructive actions blocked unless confirmed │
├────────────────────────────────────────────────────────┤
│ 2. Encrypted Credential Vault │
│ • Windows DPAPI (CryptProtectData) zero-leak │
│ • PBKDF2-HMAC-SHA256 (200,000 iterations) fallback │
│ • Credentials masked in memory (sk-12...cdef) │
├────────────────────────────────────────────────────────┤
│ 3. AST Execution Sandbox Guard │
│ • Banned imports: _ctypes, winreg, msvcrt │
│ • Dangerous call detection: shutil.rmtree, popen │
│ • Destructive shell regex: format, rm -rf, del /s │
├────────────────────────────────────────────────────────┤
│ 4. Automated Git Checkpoint Safety Net │
│ • Auto-stash snapshot before file writes │
│ • Instant rollback via /undo │
└────────────────────────────────────────────────────────┘
🩺 Self-Healing & Evolution
The Self-Healing Loop
When a tool fails during autonomous execution, the Self-Healing Engine (kurocode.healing) takes over:
- Detection:
FailureDetectormatches stack traces against 10 error categories (MISSING_DEPENDENCY,SYNTAX_ERROR,FILESYSTEM_ERROR,NETWORK_ERROR, etc.). - Diagnosis:
FailureDiagnosticiancalculates confidence and formulates a repair hypothesis. - Automated Repair:
- Missing Package: Executes
pip install <missing_module>and retries. - Syntax Error: Restores previous working file snapshot and retries with AST linting.
- Filesystem Error: Recursively creates missing directory paths.
- Network / 429: Pauses with exponential backoff and cascades to secondary provider.
- Missing Package: Executes
Controlled Capability Evolution
KURO audits its own performance over time (kurocode.evolution):
- Detects recurring failure patterns in
brain/kuro.db. - Analyzes user requests for unsupported capability keywords (
cannot do,missing tool). - Synthesizes formal
ImprovementProposalrecords with unique proposal IDs. - Tests and validates newly synthesized skills in an isolated workspace before deploying to production.
- Tracks all milestones in an append-only ledger (
evolution_history.json).
🧩 KuroHub & Modular Capability Architecture
KURO manages capabilities as modular, plug-and-play puzzle pieces:
- Tools: Discrete callable functions saved as individual
.pyfiles intools/and registered inbrain/tools.json. - Plugins: Full modular capability packages installed as complete directory trees into
plugins/and registered inbrain/plugins.json. - Skills: Multi-step procedural routines installed as directory trees into
skills/and registered inbrain/skills.json. - Integrations: Connected service bridges installed into
integrations/and registered inbrain/integrations.json.
Direct Procedural Skill Invocation (/<skill-name>)
Installed skills are dynamically loaded into your Tab autocompletion menu. When invoked via:
/<skill-name> [prompt or parameters]
# Example:
/git-release-workflow bump version to 2.1.0 and run tests
KURO automatically loads the skill instructions from skills/<name>/SKILL.md (or README.md), composes the execution plan with your prompt, and executes the routine step-by-step with deterministic verification.
The KuroLabs Capability Hub (kuroLabs-ai/hub)
KURO is natively integrated with the official community registry at https://github.com/kuroLabs-ai/hub:
- Live Hub Sync: Run
/hub updateto fetch the latest capability registry (kuro-hub.json). - One-Click Installation: Install community puzzle pieces directly via
/hub install <name>or/store install <name>. - Clean File Placement: Tools install cleanly as single
.pyfiles intotools/, while plugins, skills, and integrations install as self-contained folders intoplugins/,skills/, andintegrations/. - Contribution & Publishing: Author custom capabilities with
/hub publishor contribute directly by opening pull requests tokuroLabs-ai/hub.
🏗️ Building Standalone Binaries
KURO includes a build pipeline to compile a standalone executable distribution:
# Build standalone console application (dist/KuroConsole/KuroConsole.exe)
python build/build_exe.py
# Package Windows Installer via Inno Setup (requires ISCC installed)
build\build_installer.bat
The resulting binary runs without requiring Python to be installed on the host machine, cleanly separating application binaries from user data in %APPDATA%\Kuro.
🧪 Testing & Verification
Run the test suite across units, integrations, and capabilities:
# Run complete test suite
pytest -v
# Run targeted test suites
pytest tests/test_advanced_capabilities.py
pytest tests/test_evolution.py
pytest tests/test_store_marketplace.py
📄 License & Credits
Distributed under the MIT License. See LICENSE for details.
- Created by: Akira Omran
- Architecture: KURO 2.0 Level 2 Autonomous System Assistant
- Repository: https://github.com/kurolabs-ai/KuroCodeAgent
Metadata
Release files for kurocode 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| kurocode-0.2.1.tar.gz | 180.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kurocode-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 389.0 kB
Release files / kurocode-0.2.1.tar.gz
| Download URL | kurocode-0.2.1.tar.gz |
|---|---|
| Size | 180.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49cc484a8eadf8034a371dd583a3f8a0c0a0964e190d258037fdb3fe7fb12f6a
|
|
BLAKE2b-256 checksum How to use checksums |
d2a86b513f0d2aea5d468754b039d1df8d7cad2887d57ee0df8297d9214c7ee4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 16, 2026.
Transparency logRelease files / kurocode-0.2.1-py3-none-any.whl
| Download URL | kurocode-0.2.1-py3-none-any.whl |
|---|---|
| Size | 208.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d6b9a2d39d7d18d513e20144246477da2d2a202bec149863e79911330f489a0
|
|
BLAKE2b-256 checksum How to use checksums |
6015d36f4689feea3d7adae5845fc58c374a7e8f147310390eac3614bc376576
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 16, 2026.
Transparency log