The questions everyone asks
Can I run Nika today?
Can I run Nika today?
install.sh,
then run nika check and nika run locally. 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. A
grammar change ships with its nika check --fix migration.How are the language and the engine versioned?
How are the language and the engine versioned?
nika check --fix)
and a refusal that names the move. The engine follows semver. 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 roadmap keeps the earlier long-range
plans as history.
Same model as SQL or GraphQL: the contract is stable, implementations
iterate.Is fetch a verb?
Is fetch a verb?
infer · exec ·
invoke · agent), locked forever. Fetching a URL is calling a
tool: invoke: { tool: "nika:fetch" }. If you see fetch: as a
verb anywhere, it’s the pre-spec legacy dialect.Which providers work offline?
Which providers work offline?
nika itself
(nika model serve). Point
model: ollama/llama3.2:3b at your machine and the infer step stays
on the machine. “Zero cloud” is about model
inference: nika:fetch, MCP, and other declared tools can still
call the network if permits allow them. mock/echo infers with
nothing at all.Do I write {{ }} or ${{ }}?
Do I write {{ }} or ${{ }}?
${{ … }}: what’s inside is CEL. A bare {{ … }} is not a
reference: it stays literal text, and the run writes the braces.
nika check names it with a [silent-literal] hint and the reference it
meant: {{ name }} points to ${{ with.name }} when the task binds
name, otherwise to ${{ inputs.name }}. Same rule: there are no
template filters (| upper, | truncate): transforms are jq, in
extract: bindings or nika:jq.My YAML is valid, so why does nika check still fail?
My YAML is valid, so why does nika check still fail?
tasks.* references live at the boundary only (with: ·
after: — a body reference is NIKA-VAR-021, hoist it into
with:), when: must be a CEL boolean over local namespaces,
nika:done only inside an agent’s tool list, exactly one verb per
task. The error names the exact rule. Fix that rule, nothing else,
re-check.Errors you’ll hit, decoded
Caught before anything runs. nika check stops a pull-request reviewer on two mistakes: a misspelled task name, with the right one suggested, and a value read outside the task’s with: boundary (NIKA-VAR-021, in the table below). Each finding names its fix; after the fix, the same check says the file is ready to run. Output captured from the real CLI on nika 0.121.0.
transient
flag (error model). The frequent ones:
When it breaks, in order
Read the code, not the message
NIKA-<NAMESPACE>-<NNN>, or a numeric runtime code such as
NIKA-1709, is stable and greppable, and nika explain <code> teaches
it. The catalog gives the namespace’s
contract.Check transient
transient: true → retry can help (declare retry: with backoff).
transient: false → the input or the file is wrong; retrying burns
money.Recover structurally
on_error: recover: substitutes a fallback value ·
on_error: on_codes: scopes recovery to specific codes (recover the
not-found, still fail loudly on permission-denied).Ask with context
nika welcome
is the perfect diagnostic attachment — it prints key presence,
never values. For everything else,
Discussions is
the fastest lane. Security findings: security@supernovae.studio,
never public issues.