Agents can write Swift. Axint makes them prove it.

The proof and repair layer for Apple coding agents.

Axint checks the Swift your agent wrote, runs the real Xcode build and tests,
reconciles findings with Apple tooling, and returns signed proof with the exact repairs to make next.
No project rewrite. No source upload.

Prove a project · Try in browser · Connect an agent · Docs · Examples · Contribute

_{Local by default. Open source. Ordinary Swift.}

A plausible patch is not proof.

Apple software is a graph of contracts. SwiftUI state, App Intents, Siri and Shortcuts metadata, widgets, entitlements, privacy declarations, concurrency, build settings, tests, and runtime behavior all have to agree. Code that looks right can still fail to compile, miss an interaction, or violate a platform contract.

Axint puts static analysis and Apple tooling into one repair loop. Static checks identify leads; Xcode build and test output can confirm, contextualize, or suppress them. The result stays compact enough for the next agent turn while full logs and artifacts remain on disk.

Prove an existing project

npx -y -p @axint/compiler axint prove --dir /path/to/MyApp

Axint discovers the Xcode project and scheme, checks existing Swift, runs the available build and tests, reconciles the findings, and writes proof under .axint/proof.

The default local run requires no account or configuration. It does not change Swift, upload source, install project instructions, install memory or MCP configuration, apply fixes, or rewrite the project.

When a failure needs another turn, Axint returns a Fix Packet: a compact repair artifact with the finding, likely files, exact next action, and rerun command. It also writes a source-free receipt: a signed proof file containing evidence, results, hashes, and repair information without project source.

axint prove --dir /path/to/MyApp --fix
axint receipt verify /path/to/MyApp/.axint/proof/latest.proof.json

--fix opts into supported deterministic rewrites and reruns the proof loop. Receipt verification checks payload integrity and the embedded Ed25519 signer. A locally signed receipt does not establish an externally trusted identity unless CI or the receiving team pins the signer fingerprint or a managed signing key.

One proof contract

Generate, Check, Run, Team, and Cloud are different entry points into the same contract: verdict, evidence, findings, next actions, and artifact paths.

Generate when it helps

Generation is optional for existing projects. When a feature is easier to describe as a smaller contract, Axint can emit ordinary Swift and the companion metadata required by the selected Apple surface.

import { defineIntent, param } from "@axint/compiler";

export default defineIntent({
  name: "CreateCalendarEvent",
  title: "Create Calendar Event",
  description: "Creates a calendar event for the user.",
  domain: "productivity",
  params: {
    title: param.string("Event title"),
    date: param.date("Event date"),
    duration: param.duration("Event duration"),
    location: param.string("Location", { required: false }),
  },
  perform: async ({ title, date }) => ({
    success: true,
    message: `Created ${title} on ${date}`,
  }),
});

axint compile create-calendar-event.ts --out ios/Intents/

TypeScript, Python, JSON IR, and the experimental .axint authoring surface lower into inspectable Apple-native output. The TypeScript pipeline also supports views, widgets, apps, Live Activities, App Enums, UnionValue schemas, App Shortcuts, and extension scaffolds; see the coverage map for the implementation and proof boundary of each surface.

Connect your agent

Axint ships an MCP server for standards-compatible hosts:

{
  "mcpServers": {
    "axint": {
      "command": "npx",
      "args": ["-y", "-p", "@axint/compiler", "axint-mcp"]
    }
  }
}

Start a fresh tool session, then call axint.status and axint.activate to verify that the server and compiler are connected.

Public proof

• Live product metrics are regenerated from the codebase.
• The real, CI-gated brownfield benchmark publishes labeled precision, recall, and abstention cases.
• Coverage maps supported surfaces to implementation, tests, and proof boundaries.
• Architecture explains the compiler, proof, MCP, Python, and runtime boundaries.
• Release notes record shipped behavior and compatibility changes.
• Security documents reporting, supported releases, telemetry, and dependency policy.

Ecosystem

Contribute

The highest-value contributions improve existing-project precision, Xcode evidence, repair quality, Apple API coverage, and reproducible examples.

• Start with a good first issue.
• Pick up a help wanted problem.
• Read the contribution guide.
• Ask, propose, or show your work in Discussions.

Requirements and license

The JavaScript package follows the Node.js engine declared in package.json. Swift generation runs anywhere Node runs. Xcode build, test, simulator, and runtime proof require macOS with a compatible Xcode toolchain.

Axint is Apache-2.0 licensed. Fork it, extend it, and ship with it. The Axint name and visual identity remain protected; see NOTICE and TRADEMARKS.md.