Kujo is a Rust-built, VM-first programming language for AI-native software, local-first automation, agentic workflows, and application scripting. It is designed for work where deterministic behavior, native capabilities, and practical ergonomics need to coexist.
Why Kujo exists
Automation languages often force a choice between small scripts and dependable systems. Kujo keeps the scripting loop direct while making files, processes, network access, databases, async work, crypto, AI operations, and security capabilities explicit.
What it provides
- A VM-first runtime with an interpreter available as a deliberate fallback and debugging path.
- Deterministic package manifests, lockfiles, nested module layouts, and frozen installs.
- Native AI request hashing, record/replay cassettes, streaming callbacks, multimodal messages, token budgeting, vector math, and JSON Schema validation.
- Trusted and untrusted execution modes with capability-specific filesystem, process, network, and AI egress controls.
- Machine-readable CLI contracts, diagnostics, documentation generation, tests, and release gates.
- A growing ecosystem of SDKs, workflow tools, publishing systems, QA tools, and local-first applications.
Start from source
```text
cargo build
./target/debug/kujo run examples/hello.kujo
```
Current boundary
Kujo 1.0 is released. The VM-first language and runtime, source build, tagged artifacts, documented CLI contracts, and release gates now define the stable supported baseline, while environment-specific production proof and future ecosystem expansion remain ongoing work.