by microsoft
An open-source Digital Worker platform for reliable execution and continuous co-evolution.
# Add to your Claude Code skills
git clone https://github.com/microsoft/SicoLast scanned: 7/16/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-07-16T06:18:51.750Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}Sico is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by microsoft. An open-source Digital Worker platform for reliable execution and continuous co-evolution. It has 103 GitHub stars.
Yes. Sico passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/microsoft/Sico" and add it to your Claude Code skills directory (see the Installation section above).
Sico is primarily written in Python. It is open-source under microsoft on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh Sico against similar tools.
No comments yet. Be the first to share your thoughts!

Sico: an infrastructure for symbiotic intelligence, where humans and Digital Workers co-evolve.
Overview · Quick Start · Technical Report · Agentic Evolution · Development · Contributing · Roadmap
Sico — Symbiotic Intelligence for CO-evolution— is an open-source platform for building, managing, and evolving Digital Workers: structured AI labor units that co-evolve with human operators through real production work, particularly in BPO (Business Process Outsourcing) scenarios.
The idea behind Sico emerged from large-scale operational challenges observed in Microsoft’s internal environments, especially across BPO-style workflows such as black-box testing.
Through real production workloads, Sico achieved closed-loop validation for Digital Workers operating under continuous execution, evaluation, and human supervision. Through this process, we observed that reliability emerged not from static automation alone, but from the continuous co-evolution between human operators and Digital Workers.
In Sico, four core roles define how work gets done:
At the center of this system, a Digital Worker is not just a model or an agent, but a structured, executable capability unit.
Its anatomy consists of:
Human operators supervise execution quality, intervene when necessary, and guide capability improvement.
This creates a practical Co-Evolution loop where humans and Digital Workers continuously improve together through real work.
For a comprehensive survey of this direction, refer to Agentic Evolution: From Self-Improving Agents to Co-Evolving Human–AI Systems
Learn more: What is Sico.
Sico is primarily designed for:
Many real-world workflows, especially in BPO scenarios such as black-box testing, data processing, customer support, and content moderation, require continuous, stable execution at scale.
BPO is a natural environment for Digital Workers:
• structured evaluation signals are continuously produced
• feedback loops naturally exist
• execution and supervision responsibilities can be clearly separated
Traditional automation approaches rely on static scripts or predefined workflows. However, production environments continuously change:
As a result, automation often becomes brittle and requires repeated manual adjustment.
Digital Workers approach this problem differently. Instead of treating execution as a fixed process, Sico treats execution as an evolving capability.
As Digital Workers take on execution, human roles shift from doing tasks to guiding evolution through the Operator role.
Each completed task contributes signals that help Digital Workers adapt to real environments, enabling organizations to scale execution capacity while continuously increasing reliability.
| Pain point | Sico's approach |
|---|---|
| Agents are thin wrappers around a model and a toolbox | A structured Cortex / Action / Memory architecture with project-level knowledge |
| AI repeats the same mistakes task after task | Execution experience captured as training signals for continuous improvement |
| Full autonomy is unreliable; humans can't easily intervene | The Operator role: human-in-the-loop collaboration with clear responsibility boundaries |
| GUI automation is flaky and hard to reproduce | Sandbox execution with isolated environments, step-level traces, and replayable runs |

Frontend (React) ──HTTP/SSE──▶ Nginx ──▶ Backend (Go / Gin)
│ ▲
gRPC │ │ reverse gRPC
▼ │
Core (Python / asyncio)
On top of this runtime, Sico organizes work into three loops that together form the co-evolution cycle between Operators and Digital Workers:
Deep dive: Sico Technical Report
makegit clone https://github.com/microsoft/Sico.git
cd Sico
cp .env.example .env # edit values as needed
Before starting the stack, configure at least one