Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (codemachine) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
npm i -g codemachine
CodeMachine is a CLI-native Orchestration Engine that runs coordinated multi-agent workflows directly on your local machine. It provides the runtime infrastructure to execute complex multi-agent topologies within your own environment. Designed to drive any high-level autonomous objective, it features a battle-tested Spec-to-Code blueprint—transforming your terminal into a factory for production-ready software. ⚡️
✨ CodeMachine Built Itself
90% of this entire codebase was generated by CodeMachine from a single specification file.
This isn't a demo—it's proof. CodeMachine engine orchestrated its own architecture, planning, implementation, and testing—creating a massively scalable codebase ready for continuous updates and improvements.
⚠️ Early Development Notice: This project is in early development and is not yet ready for production use. Features may change, break, or be incomplete.
Join our growing Discord and Reddit communities of developers building with CodeMachine!
Why CodeMachine?
- Customizable, End-to-End Workflows: Architect sophisticated orchestration pipelines for any scale, from executing simple scripts to managing multi-day, complex development cycles.
- Strategic Multi-Agent Collaboration: Leverage a heterogeneous multi-agent system by assigning specialized models to specific tasks—for instance, using Gemini for planning, Claude for implementation, and another model for code review.
- Massively Parallel Execution: Achieve significantly accelerated output by deploying sub-agents that operate simultaneously on different components of a task.
- Persistent, Long-Running Orchestration: Execute workflows for extended durations—hours or even days—to autonomously accomplish complex, long-term development goals.
🚀 Quick Start
Installing and running CodeMachine CLI
First, install the command-line tool globally:
npm install -g codemachine # or bun/pnpm/yarnThen, simply run codemachine in your project directory to get started:
codemachine # or cmInitializing a Project
CodeMachine initializes a .codemachine/ workspace. To start add your specs to the inputs/specifications.md file, then run /start and watch the magic happen, CodeMachine will:
- Architect a complete system blueprint from your requirements.
- Formulate detailed, step-by-step execution plans.
- Engineer clean, production-grade code for every component.
- Generate essential automation for testing and deployment.
- Integrate rigorous validation checks across every phase of execution.
Supported AI Engines
CodeMachine requires at least one CLI-based AI engine to handle the primary roles of planning and writing code, and is designed to orchestrate multiple engines to collaborate within a single workflow.
| CLI Engine | Status |
|---|---|
| Codex CLI | ✓ Supported |
| Claude Code | ✓ Supported |
| CCR (Claude Code Router) | ✓ Supported |
| OpenCode CLI | ✓ Supported |
| Cursor CLI | ✓ Supported |
| Auggie CLI | ✓ Supported |
| Gemini CLI | ⊙ Coming Soon |
| Qwen Coder | ⊙ Coming Soon |
Production Validation:
CodeMachine has been battle-tested on the Sustaina Platform a full-stack ESG compliance system spanning 7 microservices, 500+ files, and 60,000+ lines of code across Python, TypeScript, React, FastAPI, and NestJS.
| Services Generated | 7 microservices (AI/ML + CRUD APIs) |
| Codebase Scale | ~500 files, 60K+ Line of code |
| Tech Stack | React 18, FastAPI, NestJS, PostgreSQL, MongoDB, Redis, Kubernetes |
| Time to MVP | ~8 hours of autonomous orchestration |
CodeMachine vs Regular AI Agents
We conducted a real-world comparison by monitoring development work on a project of identical scope and complexity using the most powerful AI agent tools (Claude Code, Cursor, Copilot) with manual orchestration and human review, versus CodeMachine's autonomous multi-agent orchestration.
| Aspect | Regular AI Agents (Manual Orchestration + Human Review) |
CodeMachine (Autonomous Orchestration) |
|---|---|---|
| Architecture Planning | 4-6 hours of manual prompting | Automated (30 min) |
| Service Implementation | 140-200 hours (7 services × 20-30h each) Manual prompting, context switching |
Parallel execution (5 hours) |
| Integration & Testing | 30-50 hours Manual coordination, debugging |
Automated validation (2 hours) |
| Deployment Setup | 8-12 hours Scripts, configs, orchestration |
Auto-generated (30 min) |
| Code Consistency | Inconsistent patterns across services Different coding styles per session |
Unified architecture & patterns Consistent across all components |
| Quality Control | Manual review required Errors compound over time |
Built-in validation at each step Automated sanity checks |
| Context Retention | Lost between sessions Repeated explanations needed |
Full project context maintained Cross-service awareness |
| Total Developer Time | ~200-300 hours | ~8 hours |
| Efficiency Gain | Baseline | 25-37× faster |
Real-world comparison: One developer manually prompting AI coding assistants vs CodeMachine's autonomous multi-agent orchestration
Want to see how CodeMachine built this?
Explore the complete case study showing the detailed path CodeMachine took to create this project—every step, decision, and workflow tracked from specification to production.
📊 View Complete Case Study & Development Track →
⭐ Contributors
CodeMachine is built with contributions from amazing developers. Special thanks to everyone who has helped shape this project.
Found a bug or have a feature idea? Check our Contributing Guide to get started.
📖 References
|
📚 Documentation Complete guides and CLI reference |
📝 Specification Schema Learn how to write specifications |
📊 Case Study Real-world production example |