Open-source compiler
Live now. Axint compiles TypeScript and Python definitions into native Swift for App Intents, SwiftUI views, WidgetKit widgets, and app scaffolds. Diagnostics, MCP tools, templates, docs, and examples are available now.
Start here
This is the current live-state map for Axint.
Use it when you need to answer one of these questions cleanly:
- What should I use first?
- Which page should I send someone first?
- Where does Cloud Check fit?
- What is live, what is preview, and what should not be overstated?
Current state
Section titled “Current state”Preview .axint surface
Preview now. .axint is the compact declarative authoring surface for feature shapes. Treat it as strategic and visible, but keep docs honest about current support and examples.
Cloud Check
Live now. Run one anonymous hosted check, then sign in with GitHub for five checks each calendar month with no card. Cloud Pro is $29 per month for 50 checks and the full Fix Packet workflow; the Teams pilot is $149 per month for 500 checks and shared organization controls.
Registry and examples
Live now. Registry package pages, compatibility status, and examples show install commands, package details, compiler metadata, and public package coverage.
Assistant integrations
Live now. Claude Code, Cursor, Windsurf, VS Code, Xcode-facing workflows, JetBrains, and Neovim can use Axint through MCP. Xcode’s mcpbridge handles project/build/test access; Axint handles App Intents generation, validation, Cloud Check, and Fix Packets. The MCP docs are the current setup source.
Fix Packets
Live now. Compile, watch, and Swift validation runs write latest.check.* and latest.* files so agents can read the same repair contract as the CLI and Xcode-facing workflow.
WWDC26 watchlist
Section titled “WWDC26 watchlist”These are the Apple surfaces Axint tracks first after the Keynote and Platforms State of the Union:
- App Intents: new protocols, assistant schemas, App Entity indexing, snippets, dialogs, and visual intelligence hooks.
- Shortcuts + Apple Intelligence: model actions that compose with app actions and entities.
- Foundation Models: Swift and Python SDK changes, tool calling, guided generation, token accounting, and context-size behavior.
- Xcode MCP: external agent access through
xcrun mcpbridge, build/test tools, diagnostics, and documentation search. - SwiftUI, WidgetKit, and Live Activities: generated surface changes that may need compiler templates, validator rules, or Fix Packet updates.
Best starting points
Section titled “Best starting points”- Start with Quickstart if you want the fastest route from definition to compiled Swift.
- Open Cloud Check if you already have Apple-facing output and want a clear result.
- Open Cloud plans and billing when you need exact allowances, Stripe lifecycle details, or account-management steps.
- Read Fix Packets if you want to understand how failures become agent-readable repair instructions.
- Use Examples if you need references you can share with someone else.
- Open Registry compatibility when you want package-level validation details.
- Send The Axint Thesis when someone needs the category argument, not setup instructions.
move from docs to workflow
Pick the next step based on what you need
The cleanest flow is: quickstart for local compile, Cloud Check for hosted validation, Cloud Pro when you need the repair prompt, Fix Packets for local repair mechanics, examples for references, and Registry compatibility for package-level detail.
QuickstartStart with the shortest path from definition to compiled Swift.Run Cloud CheckUse the live check page when you want a quick result on generated Apple output. Sign in there when you need the Pro repair prompt.Fix PacketsSee how the repair artifact feeds agents, MCP clients, and Xcode-facing workflows.Examples guideSee real examples, package pages, and compatibility links outside this page.Registry compatibilityGo straight to package-level compatibility when you need exact status.Axint thesisSend this when the question is why this category exists.