The first public package releases landed in early April 2026

AINative was created on April 3, 2026. Within the same day, the client runtime and Node server adapter hit npm as v0.1.1. The CLI followed on April 4 as v0.2.0. Here is what those early releases included and how we got there so fast.

v0.1.1 — client and server-node

useStream hook with automatic reconnect on network failure.
Delta accumulation — partial tokens are held until a full word boundary.
Tool-call lifecycle: pending → streaming → resolved → error states.
TypeScript types exported from package root.
CommonJS and ESM dual build via tsup.

bash

npm install @hari7261/ainative-client@0.1.1
npm install @hari7261/ainative-server-node@0.1.1

Install the first stable releases

v0.2.0 — CLI

The CLI skipped 0.1.x because we wanted to align the minor version with the feature set: v0.2 ships with the `doctor` command, which checks your environment for required dependencies and prints a clear diagnosis.

bash

$ ainative doctor
✓  Node.js  v20.11.0
✓  npm      10.2.4
✓  OPENAI_API_KEY  set
✗  ANTHROPIC_API_KEY  not set (optional)
✓  Ollama   not running (optional)

All required dependencies satisfied.

ainative doctor output

What 0.1.x → 0.2.x would mean for you

In practice, the 0.1.1 → 0.2.0 upgrade for the CLI is purely additive — the doctor command was new, nothing was removed. We plan to keep the pre-1.0 lifecycle short: the goal is a 1.0 release before the end of Q2 2026.