@conscience-technology/nora-sdk is the TypeScript client for the Nora platform. Agents are defined in Nora (via UI / MCP / CLI); the SDK is where your app code calls them, watches them, and feeds results back. It can’t change agent definitions — that path stays UI / MCP / CLI → approval → new version — but it can invoke, read decisions, capture feedback, and drive the improvement queue from inside your product.
Status (2026-09-06): implemented and typechecks in the platform repo at
0.0.1. Publish to a public npm scope is in progress; the contract is stable — swap install URL when the public publish lands without changes.When to reach for the SDK
Three ways to talk to Nora from code, each right for a different caller:
The SDK is the right choice when your app already runs Node/TS and you want typed results, per-call idempotency,
onBehalfOf audit trails, and the improvement loop embedded in your admin surface.
Server-side only
The client carries PATs and trigger secrets, so initialising in the browser throws — silent operation is the worst failure mode. If end-user screens need to trigger runs, proxy through your server.Get started
- Install —
npm install @conscience-technology/nora-sdk, prerequisites (Node 18+, ESM), version pinning. - Auth — mint PAT + trigger secret, pick the right scopes.
- Client options — full
ClientOptionsreference (base URL, retries, logging, custom fetch, trigger header).
Surfaces
Each surface is a category of methods. Same split as the CLI’s command groups.See also
nora flows run— the CLI equivalent offlows.run, useful while the SDK is pre-publish.nora feedback— CLI counterpart tofeedback/signals.report.nora approvals— approval workflow the improvement queue shares with the platform.