Skip to main content
Nika lets you put AI workflows in an application, describe their permitted effects, and inspect what happened after a run. This page separates what you can use in 0.124 from the earlier plan the project keeps as a record.

Start with what is available

The CLI and npm package have separate release channels. Read Current status for the exact documentation targets and Releases for published changes. Source on main, a closed issue, or an accepted design does not by itself mean a package shipped. Known limits in 0.124 lists what the release does not do.

What does “Compile” mean here?

Offline, with no model, nika compile writes exact skeletons (nika compile --list names them), bounded support intents and conservative edits of an existing file (--base with --change). An intent it cannot settle stays incomplete and asks its questions; it never writes a substitute. For a request in your own words, open the terminal Session (nika) or run nika compile "<request>" --authoring-model <provider/model>. A model you choose writes the candidate, and Nika checks it, and rehearses it where it can, before anything is saved or run. Authoring with a large model can take minutes, and a rehearsal skips model steps: Known limits in 0.124 lists what to expect. Start with the offline authoring path. The engine roadmap and public engine issues track the maintenance work.

What happens after 0.124?

0.124 is the current release line. Work stays focused on maintenance, security and the media capabilities workflows need; native video is planned for 0.125. The 0.123.x line is the previous one. No 1.0 release is planned. The engine roadmap and the specification keep the conditions once set for a 1.0 release as the record of that plan, not as a commitment:
  • Release and user experience qualification: installation, documentation, editor setup and supported execution paths must work together.
  • The contract system: everything that crosses a boundary carries a declared contract (types, errors, effects and bounds), and unknown information stays visible instead of being reported as success.
  • Long-term compatibility: conformance, archives, deterministic checking, a compatibility promise and succession are launch conditions.
  • Design-partner release candidates: the plan placed these before a launch.
Memory, retrieval and cognition were never a single launch condition: the former Connectome umbrella, which required the whole memory subsystem before 1.0, was retired on 2026-10-08. These were conditions, not delivery dates or claims of completion. The owning engine roadmap and the specification’s timeline carry the detailed decisions. Timeline and evidence explains how to read them without confusing a proposal with a shipped feature.

Follow the work without losing the product story

If you are evaluating Nika, begin with one small workflow in your application. Use its output and trace to judge the available product; use the roadmap to understand its direction.