Axint is an AI-generated Swift code proof gate tool for the Apple platform. The core problem it solves is this: an AI-written Swift patch looking reasonable does not mean it can compile, pass tests, or conform to platform contracts. Apple software is a graph composed of many contracts—SwiftUI state, App Intents, Siri and Shortcuts metadata, widgets, Entitlements, privacy declarations, concurrency, build settings, tests, and runtime behavior must all be consistent with one another. Axint puts static analysis and Apple's official toolchain into the same fix loop; static checks are responsible for finding leads, while Xcode build and test output is responsible for confirming, adding context to, or suppressing those leads. The final result stays compact enough for the next round of AI agents to use, while full logs and artifacts remain on disk.
Main capabilities include: for existing projects, Axint discovers the Xcode project and schemes, inspects existing Swift code, runs available builds and tests, reconciles check results, and writes the proof to the .axint/proof directory. By default it runs locally without an account or configuration, does not modify Swift code, does not upload source code, does not install project instructions or memory/MCP configuration, and does not automatically apply fixes or rewrite the project. When a failure requires another round, Axint returns a Fix Packet: containing findings, potentially affected files, the exact next action, and the rerun command. It also writes a Receipt without source code: a signed proof file containing evidence, results, hashes, and fix information, but no project source code. The --fix option optionally adds 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 uses a hosted signing key.
In terms of usage, axint prove can be run with Xcode on a macOS runner for pull request workflows; see the GitHub Actions setup for a starter workflow and signed Receipt output. Proving requires real Apple toolchain evidence; missing tests or an unavailable build will not be silently reported as passing. Axint provides entry points such as Generate, Check, Run, Team, Cloud, and they share the same set of contracts: verdict, evidence, findings, next actions, and artifact paths. For existing projects, generation is optional; when a feature is easier to describe with a smaller contract, Axint can generate plain Swift as well as the companion metadata required by the chosen Apple interface. TypeScript, Python, JSON IR, and the experimental .axint authoring interface degrade to inspectable Apple-native output; the TypeScript pipeline also supports views, widgets, apps, Live Activities, App Enums, UnionValue schema, App Shortcuts, and extension scaffolding.
Axint provides an MCP server compatible with standard MCP hosts, and axint.status and axint.activate can be called to verify that the server and compiler are connected; the hosted endpoint is located at https://mcp.axint.ai/mcp，同时支持既有 MCP clients and the current stateless protocol version. For orchestrators that need to delegate persistent tasks between agents, Axint also provides an authenticated A2A server: MCP exposes a single tool, while A2A exposes the complete inspection, diagnosis, proof, and repair planning task, with support for status, streaming updates, cancellation, and source-free result artifacts. The Agent Card is located at /.well-known/agent-card.json; loopback use requires no setup, while non-loopback deployments require bearer authentication by default.
The available tools cover startup, recovery, and inspection (such as axint.status, axint.activate, axint.upgrade, axint.doctor, axint.session.start, axint.context.memory, axint.context.docs, axint.workflow.check), generation and discovery (such as 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), inspection and repair (such as axint.xcode.guard, axint.xcode.write, axint.fix-packet, axint.cloud.check, axint.repair, axint.feedback.create, axint.swift.validate, axint.swift.fix), coordination and execution (such as axint.agent.install, axint.agent.advice, axint.agent.claim, axint.agent.release, axint.run, axint.run.status, axint.run.cancel), as well as the built-in prompts axint.quick-start, axint.project-start, axint.context-recovery, axint.create-widget, axint.create-intent.
Applicable scenarios include: setting up proof gates for AI-generated Swift code in PRs or CI, validating App Intents, SwiftUI views, WidgetKit widgets, and complete apps, checking Apple platform compatibility, accessibility label proofs, and integrating with agent orchestration workflows via MCP or A2A. In terms of limitations: Xcode builds, tests, simulators, and runtime proofs require macOS and a compatible Xcode toolchain; Swift generation can run anywhere Node runs; locally signed Receipts do not constitute an externally trusted identity unless the signer is pinned. The project uses the Apache-2.0 license, and the Axint name and visual identity are protected.
