Monoco
The First L3 Agentic Orchestration Platform.
Monoco is a Headless Operating System designed to shift AI development from L2 (Agents/Chatbots) to L3 (Autonomous Engineering Systems). It provides the governance, state management, and environment isolation required to turn raw LLM capabilities into a reliable, verifiable, and autonomous workforce.
🚀 Beyond the "Chat" Paradigm: The L3 Leap
While traditional AI tools (L2) focus on turn-based chat and "helpful assistants," Monoco orchestrates Autonomous Sessions.
| Feature | L2: AI Agents (e.g. Cursor, Claude Code) | L3: Autonomous Systems (Monoco) | Value |
|---|---|---|---|
| Interaction | HITL: Human-In-The-Loop (Step-by-step) | HOTL: Human-On-The-Loop (Batch/Async) | 10x Productivity |
| Quality | Subjective satisfaction (Chat-based) | Objective DoD (Tests, Lints, Invariants) | Reliability |
| State | Ephemeral context (Chat History) | Persistent Identity (Issue Tickets) | Traceability |
| Environment | Shared / Volatile | Isolated / Sandboxed (Worktrees) | Non-Interference |
🌩️ The "Distro" Metaphor
Monoco acts as a Distribution, bridging the gap between raw intelligence and industrial-grade engineering.
- LLM Kernel: The raw reasoning engine (Kimi, Gemini, Claude).
- Monoco Distro: The orchestration layer providing the Init System (Issue Lifecycle), Package Manager (Skills), and Security Policy (Guardrails).
- Client/DE: Your IDE (VSCode, Zed) interacting via standard protocols (LSP, ACP).
🛡️ Core Pillars
1. Objective Definition of Done (DoD)
In Monoco, a task is not "finished" when the AI says so. It is finished when the System Invariants are met: all tests pass, the linter is silent, and the implementation matches the Issue's acceptance criteria.
2. Issue-Driven Development (TDD for Agents)
Monoco treats Issues as Units of Work. Just as systemd manages system units, Monoco manages the lifecycle of an engineering task—from open to close, ensuring no "freelancing" and absolute traceability.
3. Isolated Sovereignty
Monoco creates dedicated, isolated environments (Branches/Worktrees) for every task. This ensures the AI never pollutes your local state or clashes with human developers.
4. Governance as Code
Policies are not just prompts; they are governed by code. Monoco enforces Git hooks, CI/CD gates, and automated audits to ensure the workforce adheres to your project's technical standards.
🏁 Quick Start
1. Install the Distro
pip install monoco-toolkit
2. Initialize Workspace
Transform any repository into a Monoco-managed autonomous engineering environment.
monoco init
3. Sync Policies
Inject your project's governance and standards into the Agent's constitution.
monoco sync
4. Orchestrate
Start the daemon to monitor the collaboration bus and schedule agent tasks.
monoco session start
🛠️ Architecture
- State Engine: Markdown/YAML-based persistence (No heavy DB required).
- Communication: Event-driven architecture via local file system events.
- Protocols: Native support for LSP (Language Server) and ACP (Agent Client Protocol).
📄 License
MIT © IndenScale
1 maintainer
Metadata
1 maintainer
Release files for monoco-toolkit 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| monoco_toolkit-0.4.2.tar.gz | 9.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| monoco_toolkit-0.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.7 MB
Release files / monoco_toolkit-0.4.2.tar.gz
| Download URL | monoco_toolkit-0.4.2.tar.gz |
|---|---|
| Size | 9.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46c9e574ff1014c3995c4d108c6f8ec828f6ac3b44fdf763e917b3465c4abcd3
|
|
BLAKE2b-256 checksum How to use checksums |
239d9f23e30cf39141d60e4bf16b3d696450041381dc9777bb51da90e622b072
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 8, 2026.
Transparency logRelease files / monoco_toolkit-0.4.2-py3-none-any.whl
| Download URL | monoco_toolkit-0.4.2-py3-none-any.whl |
|---|---|
| Size | 471.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3ec5356d465584b683d2fa3d760781e402ea9454bc694e7c6da547a4b07aa556
|
|
BLAKE2b-256 checksum How to use checksums |
fb8d608d877f4f028ebe9cbda7b3c8e89fa80eb75825848bb7650a720db77cba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 8, 2026.
Transparency log
