Install
Axint ships as a single scoped npm package: @axint/compiler. It bundles
the CLI, the MCP server, and the authoring SDK in one install.
Global install
npm install -g @axint/compilerpnpm add -g @axint/compileryarn global add @axint/compilerbun add -g @axint/compilerAfter install, the axint binary is on your path:
axint --version # → 0.2.2axint --helpPer-project install
If you’d rather pin Axint to a specific project, install it locally and invoke it through your package manager:
npm install --save-dev @axint/compilernpx @axint/compiler compile intents/SendMessage.intent.tsPinning to an exact version is recommended while the compiler is pre-1.0 — the IR schema is stable but diagnostic codes are still growing.
{ "devDependencies": { "@axint/compiler": "0.2.2" }}Using it as a library
You can also import compileSource() and the SDK directly from your own
TypeScript code — this is how axint.ai powers its in-browser playground.
import { compileSource } from "@axint/compiler";import { defineIntent, param } from "@axint/compiler/sdk";
const intentSource = `import { defineIntent, param } from "@axint/compiler/sdk";
export default defineIntent({ name: "LogWorkoutIntent", title: "Log Workout", description: "Records a workout session.", domain: "health", params: { activity: param.string("Activity type") },});`;
const result = compileSource(intentSource, "log-workout.ts");console.log(result.output?.swiftCode);Deprecated: the unscoped axint package
Version 0.2.0 and earlier published to the unscoped axint name on npm. That
package is permanently deprecated — it will not receive updates. If you see:
npm install -g axint # ← deprecated, do not usein older tutorials, replace it with the scoped name.