Skip to main content
Nika is not another agent. It is the workflow file your agents already run — checked before, verified after. Integration therefore means two small things: teach your agent the language, and wire the read-only oracle.

Minute 0-2 · install the CLI

This 10-minute loop uses the CLI (nika init, nika wire, nika compile). The later commands on this page require a nika binary on PATH.
No key needed yet — mock/echo and local providers run without one. Driving Nika from Node instead of a shell? That is a different door: npm install @nika-open/nika@0.124.5 inside a project bundles the engine for your app and gives you ./node_modules/.bin/nika, but does not add nika to your PATH. Do not type npx nika outside such a project: the unscoped npm name nika belongs to an unrelated package. Follow the SDK quickstart (run() admits, run.result() settles, run.events() yields normalized kinds).

Minute 2-5 · teach the repo

One command writes the agent surface: AGENTS.md (read natively by Codex, Claude Code, Cursor, OpenCode, Hermes, Jules and every AGENTS.md-aware tool), CLAUDE.md, the Cursor rules and subagents, the Copilot instructions, the repo-level agent skill, the .vscode schema wiring, a commented nika.yaml and a starter workflow. It also writes project MCP configs (.mcp.json, .cursor/mcp.json, .agents/mcp_config.json) and Claude Code and Cursor hooks: shell scripts those clients run at session start, after an edit and before a shell command. Read them before you commit them (every file nika init writes). Existing files are skipped.

Minute 5-7 · wire the oracle

nika wire --help lists every target on this binary. Clients with no target (goose, Open WebUI, AnythingLLM, Cherry Studio, Jan) take the same two-field stanza — copy it from per-client wiring. What the oracle exposes (and refuses to): Nika as an MCP server.

Minute 7-10 · prove the loop

Ask your agent:
Create a workflow from the chain template that summarizes ./notes.md into ./out/brief.md, check it, then run it with the mock model.
The agent previews (nika compile chain --json — incomplete questions stay questions; no file is written), answers them with repeatable --answer KEY=JSON_LITERAL, writes a Ready destination, audits (nika check — plan, cost floor, permits, before any token is spent), runs on the mock model (--model mock/echo: no key, no model call), and the receipts land in .nika/traces/ (nika trace verify → exit 0: bare, it reads the latest trace; the run card prints each trace’s path on its trace: line).

Then: CI receipts

Put the GitHub Action on the repo — every PR that touches a .nika gets a sticky comment with the check verdict, the honest cost floor, required secrets and the DAG. Check-only, zero secrets, by default.

The per-tool pages

  • OpenCode — native skills + AGENTS.md + MCP; zero packaging needed.
  • Hermes — the delegation pattern: Hermes orchestrates, Nika runs the repeatable work with receipts.
  • GitHub Actions — plan with receipts on every PR.
  • Everything MCP-capable — Cursor · Claude Code · Codex · Zed · Gemini CLI · Windsurf · Continue · Cline · Aider, one stanza each.