Axint

AI wrote the Swift. Prove it builds before you merge.

A proof gate for AI-written Swift in your PR or CI pipeline.

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 · GitHub Actions setup · Try Cloud Preview · 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.

Use it in a pull request

Run axint prove on a macOS runner with Xcode. For a starter workflow and the signed-receipt output, see GitHub Actions setup. A pass needs real Apple-tooling evidence; missing tests or an unavailable build are not silently reported as proof.

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.

The hosted endpoint at https://mcp.axint.ai/mcp supports both established MCP clients and the current stateless protocol generation. Compatibility is continuously checked with official SDK clients; see the protocol compatibility contract.

For orchestrators that delegate durable work between agents, Axint also ships an authenticated A2A server. MCP exposes individual tools; A2A exposes complete check, diagnosis, proof, and repair-planning tasks with status, streaming updates, cancellation, and source-free result artifacts.

npx -y -p @axint/compiler axint-a2a --project-root /path/to/MyApp

The Agent Card is served at /.well-known/agent-card.json. Loopback use works without setup; non-loopback deployments require bearer authentication by default.

MCP tool and prompt inventory

Start, recover, and inspect

axint.status · axint.activate · axint.upgrade · axint.doctor · axint.session.start · axint.context.memory · axint.context.docs · axint.workflow.check

Generate and discover

axint.feature · axint.project.pack · axint.project.index · axint.project.syncVersion · axint.suggest · axint.registry.search · axint.scaffold · axint.compile · axint.validate · axint.tokens.ingest · axint.schema.compile · axint.templates.list · axint.templates.get

Check and repair

axint.xcode.guard · axint.xcode.write · axint.fix-packet · axint.cloud.check · axint.repair · axint.feedback.create · axint.swift.validate · axint.swift.fix

Coordinate and run

axint.agent.install · axint.agent.advice · axint.agent.claim · axint.agent.release · axint.run · axint.run.status · axint.run.cancel

Built-in prompts

axint.quick-start · axint.project-start · axint.context-recovery · axint.create-widget · axint.create-intent

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.
• Apple platform compatibility tracks current Xcode, Swift, Siri, App Intents, Foundation Models, SwiftUI, UIKit, and App Store changes against implemented checks and canaries.
• Accessibility-label proof turns common-task accessibility evidence into a reviewable App Store readiness report.
• MCP compatibility documents the hosted server's dual-era transport contract and verification path.
• A2A documents durable agent-to-agent proof delegation, authentication, task isolation, and the local execution boundary.
• Architecture explains the compiler, proof, MCP, A2A, Python, and runtime boundaries.
• Release notes record shipped behavior and compatibility changes.
• Security documents reporting, supported releases, telemetry, and dependency policy.

Ecosystem

| [PyPI](https://pypi.org