Skip to content

Finished enough to maintain

Nika 0.123.0 became the open-source reference release: what it did, the limits it listed in plain words, and what maintenance turned out to mean.

Someone who runs workflows on a tool needs a few plain answers from it: which version to pin, what will still be fixed next month, and whether a hosted service is coming.

On 23 October 2026, Nika answered in its release notes. v0.123.0 opens with this paragraph:

Nika 0.123 is the open-source reference release of Nika: the Rust engine, the nika command line and its terminal workspace, and a TypeScript SDK (@supernovae-st/nika 0.123.0) that runs .nika workflows from an application. After this release the project is maintained: security fixes, bug fixes and compatibility. No hosted service is planned.

A reference release is the version others are meant to build on and compare against.

What it does, in five lines #

The notes list five claims, each under a short heading:

  • Say it once, keep it as a file. You describe an outcome in the terminal workspace. Nika "asks only for what is missing", writes a .nika workflow, checks it and, where it can, "rehearses it on a copy of your files before you save or run anything" (the rehearsal of 0.122.0, told in Tried on a copy before you say yes).
  • Audited before it runs. nika check reads the whole file first: the effects it may perform (permits:), where secrets go, literal credentials, cost estimates and a dangerous combination of permissions the notes call "the lethal trifecta". It "names the repair where it knows one".
  • Metered and recorded while it runs. --max-cost-usd caps a run, every run is recorded under .nika/traces/, and a run paused at a human gate resumes with the person's answer.
  • Scheduled by your own machine. nika arm emits launchd or systemd units, with an env file for the provider keys a scheduled run needs.
  • Your choice of model. "The workflow file names its model, and Nika never substitutes another one silently."

The README at the release tag shows the loop on a file as an "offline lesson" that "needs no provider":

terminal
nika compile hello hello.nika
nika check hello.nika
nika run hello.nika
nika trace verify

The README is careful about what these four commands prove. "hello always uses mock/echo, a stand-in model that echoes the prompt, even when provider keys are present. It proves that the workflow runs, not that a model answered." And about the last line: "nika trace verify checks the latest trace's integrity, not the truth of an AI answer."

What it says it does not do #

The notes link a page of known limits, "each with a way around it", and sum it up in one sentence:

In short: a rehearsal does not call models and replays only plain GETs of pages already observed; writing a workflow with a large model can take minutes; the terminal mixes English and French lines; the VS Code extension stays at 0.120; scheduled runs need your keys in an env file.

In plain terms: a trial run on copies does not call a model, so it does not show what a model will say. Asking a large model to write a workflow can take minutes. The terminal interface does not stay in one language. The editor extension was not brought up to this release. A schedule needs your provider keys written in an env file.

The README at the tag adds limits that hold for every workflow: "A clean check is not a true answer. It describes a file's structure and boundary; it does not prove that model output is right." The README of that tag also stated how far the conversational Session was tested: it "was qualified on six synthetic tasks with one macOS installation of an identified development build, not the released binary", and "That is not a general reliability claim." That sentence left the README the next day, in the first maintenance commit, and is not in the README of v0.123.1.

For a reader, the list of limits is the most useful part of the notes, because it tells you where to put your own checks.

What "maintained" committed the project to #

The day after the release, the repository's policy files said what maintenance means. SECURITY.md listed the 0.123.x line as maintained, main as the maintenance branch and every version older than 0.123 as unsupported, with security fixes landing on main and shipping "as 0.123.x patch releases". CONTRIBUTING.md named the work that helps most: 0.123 is "now maintained with security fixes, bug fixes and compatibility, so contributions of that kind help most."

Compatibility had a concrete meaning in the release itself. The engine reports machine protocol 2, the version of the interface that the SDK in your application talks to. An older SDK that cannot read it refuses the engine at connect, "before any job is admitted, never in the middle of a run." The upgrade advice is one line: "upgrade the SDK first, then the engine."

The release closed with what its last fix commit calls a "finite list of fixes". In one of them, a key pasted into a header used to get through, because "SECRETS read « no declared secret reaches an effect » and the run sent the key." nika check now refuses a literal Bearer token, names the argument, and asks you to declare the credential under secrets: and write Bearer ${{ secrets.<name> }}. The token itself is never printed.

The specification recorded the same moment from its side. Its changelog marks the exact spec commit the engine embeds, and notes that nika check --json "reports it offline as spec_sha". The spec has no release tags: "the commit is the identity".

Two days later, the first correction #

v0.123.1 shipped on 25 October as "the first maintenance release of the 0.123 reference line". Its most telling fix was about what the product said: "the welcome screen no longer advertises a hosted Nika Cloud, which does not exist". Hints and access errors now name commands that exist, nika init --example copies the files its lesson reads, and a new project keeps the nika serve token and job state out of Git. It also carried one dependency security update. The notes add: "The workflow language, the file format and the SDK protocol are unchanged."

A maintenance release that removes the mention of a service that does not exist is a fair picture of what maintenance is for.

What happened next #

This section is later than the story. On 27 October, four days after it, v0.124.0 opened a 0.124 line with media capabilities. The SECURITY.md of the v0.124.0 tag, in a paragraph still the same on main when this post was written in November, reads: "0.124 is the current release line. Work stays focused on maintenance, security and the media capabilities workflows need". It adds: "The 0.123.x line is the previous one and receives no further patches." If you pinned 0.123.x for its security fixes, its table now says "previous line: upgrade to 0.124.x".

What held is the posture of the first paragraph. The README on main in November says "there is no hosted service", and the stated focus is still maintenance and security, now with media work beside them.

Why it matters #

A release you can build on needs three things written down: what it does, what it does not do, and what will happen to it. Version 0.123.0 wrote all three, in its notes and, the next day, in its policy files. Its first maintenance release then corrected the product where it said more than was true. The limits are part of the release, in the same place as the claims.

What it does not do #

  • No hosted service. The notes say: "No hosted service is planned."
  • No speed or reliability promise. Writing a workflow with a large model "can take minutes", and the README of the tag called the Session's qualification "not a general reliability claim".
  • No proof that answers are right. A clean check describes structure and boundary. nika trace verify checks a record's integrity, not the truth of an answer.
  • Mixed languages in the terminal. The release lists that "the terminal mixes English and French lines".
  • No current editor extension. The VS Code extension "stays at 0.120".
  • No more 0.123.x patches. Since v0.124.0, SECURITY.md says the 0.123.x line "receives no further patches"; the maintained line is 0.124.x.

Read the v0.123.0 release, the v0.123.1 release and the engine's SECURITY.md, or continue with The run keeps its receipt.