Project History (cmdai to caro)
Relevant source files
The following files were used as context for generating this wiki page:
This document outlines the historical evolution of the project, from its initial conception as cmdai to its current identity as caro. The project's core mission—to convert natural language into safe POSIX shell commands using local LLMs—has remained consistent throughout this transition. The name change occurred in the very early stages of development, reflecting a refinement of the project's branding rather than a change in its fundamental goals or architecture.
The project began under the name cmdai, with initial documentation and development artifacts reflecting this identity. It was quickly rebranded to caro, a name that is now used across all current specifications, documentation, and user-facing materials. The mascot, also named Caro, was introduced as part of this new identity.
The cmdai Era
The project was originally named cmdai. The initial vision for cmdai was a "Natural Language to Shell Command CLI Tool" built with Rust, focusing on performance, single-binary distribution, and safety. This is evidenced by early session logs where a README.md file was generated for the project under this name.
Sources: exports/session-logs/2025-09-13-readme.txt:12-15
Initial Features and Vision
The core features planned for cmdai are nearly identical to those of the current caro project, emphasizing the consistency of the project's vision.
| Feature | Description |
|---|---|
| Instant startup | Single binary with <100ms cold start. |
| Local LLM inference | Optimized for Apple Silicon with MLX. |
| Safety-first | Dangerous commands blocked by default. |
| Zero dependencies | Self-contained binary. |
| Multiple backends | Support for MLX, vLLM, and Ollama. |
| Smart caching | Hugging Face model management. |
| Cross-platform | Support for macOS, Linux, and Windows. |
Sources: exports/session-logs/2025-09-13-readme.txt:20-28
Proposed cmdai Architecture
The initial architectural plan for cmdai was modular, with a clear separation of concerns. This structure laid the groundwork for the current caro architecture.
The diagram below illustrates the proposed project structure for cmdai.
cmdai Contributor Handbook
A "cmdai Contributor Handbook" was created, outlining the project's mission and core values. This document reinforces the project's foundational principles, which have been carried over to caro. The mission was stated as: "cmdai exists to make terminal access safer and more accessible for everyone."
Sources: HANDBOOK.md:11
The Transition to caro
The transition from cmdai to caro happened early in the project's lifecycle. Evidence suggests the name change was decided upon between the initial scaffolding and the formal planning phase.
A key piece of evidence is the CONTRIBUTING.md file. While this document is for the caro project, it contains a direct reference to the old name in its mission statement: "cmdai is building the safety layer for AI-to-terminal interactions." This shows a direct lineage and continuity of purpose.
Sources: CONTRIBUTING.md:40
Further evidence of the early change is found in the first formal implementation plan, which is titled for caro and outlines the creation of the caro CLI tool, not cmdai. This indicates that by the time of structured planning, the new name was already in use.
Sources: specs/001-create-a-comprehensive/plan.md:1-4
The caro Identity
The project is now consistently referred to as caro. This new identity is reflected in all recent documentation, presentations, and development roadmaps. A mascot, also named Caro, was introduced to give the project a friendly and approachable persona.
Sources: presentation/slides.md:21-25
caro Architecture
The architecture of caro remains true to the initial vision of cmdai but is more refined. The core components of safety validation, backend routing, and command generation are central to the design.
The diagram below shows the current architecture for caro.
Sources: presentation/slides.md:88-112
caro Roadmap
The project's future is planned under the caro name, with a clear roadmap for releases and new features. The roadmap is divided into major milestones, including core improvements, a website launch, and advanced features.
The timeline below visualizes the major milestones for caro in 2026.
The development plan includes specific commands under the new name, such as caro daemon start and caro shell install, solidifying the caro identity in the tool's functionality.
Sources: specs/007-caro-shell-integration/milestones.md:21
Conclusion
The project's evolution from cmdai to caro was a strategic rebranding that occurred early in its development. This change solidified the project's identity and branding with the introduction of a mascot and a more memorable name. Importantly, the core mission, architecture, and safety-first principles established under the cmdai name have been fully retained and continue to guide the development of caro. The transition was seamless, with the project's vision and technical foundation remaining consistent.