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 AI-written Swift before merge: Xcode-backed verdicts, exact Fix Packets, and signed receipts for PRs and CI.
2026-11-16
Yıldızlar
18
Araçlar
—
Çalışma süresi
—
Evidence class
What it means
Confirmed
Deterministic analysis or matching compiler, build, or test evidence supports the finding.
Probable
Strong static evidence identifies a likely problem, but decisive Apple-tooling evidence is incomplete.
Advisory
A heuristic identifies a quality, accessibility, privacy, interaction, design, or runtime concern for review.
Suppressed
Stronger evidence or a project-local review contradicts the finding; it remains in the receipt without blocking the result.
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.
--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.
Mode
Role in the proof loop
Check
Validate generated or existing Swift with evidence-aware diagnostics and appropriate abstention.
Run
Orchestrate resumable build, test, runtime, and .xcresult evidence on a local or your own Mac runner.
Generate
Compile smaller contracts into inspectable App Intents, SwiftUI views, widgets, Live Activities, app shells, metadata, and tests.
Team
Preserve project context, sessions, file claims, repair packets, and handoffs across agents.
Cloud
Run hosted checks and preserve shared proof history when local Apple tooling is unavailable.
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.
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:
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.
The Agent Card is served at /.well-known/agent-card.json. Loopback use works
without setup; non-loopback deployments require bearer authentication by
default.
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.
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.
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Sorular
Axint nasıl kurulur?
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için http yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Axint için API anahtarı gerekiyor mu?
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Axint hangi aktarımı kullanıyor?
Axint sunucusuna HTTP üzerinden ulaşılır.
Axint en son ne zaman kontrol edildi?
Son kontrol: 2026-11-16. Prove AI-written Swift before merge: Xcode-backed verdicts, exact Fix Packets, and signed receipts for PRs and CI.