axint cloud · hosted validation + repair packets
axint cloud runs hosted Apple-native validation and returns a Fix Packet with verdict, findings, confidence, and an AI-ready repair prompt your coding agent can act on.
A Fix Packet is the repair contract between your coding agent, axint, and Xcode. Free Cloud Check ships today, Pro adds the full repair workflow, Teams adds shared history. Open-source compiler stays Apache-2.0 — Cloud is additive, not a paywall around the core.
what cloud writes
axint cloud
.axint/cloud/report.json
the cloud loop
01
Swift, project, or axint output
02
204 hosted diagnostics
03
verdict + repair prompt
04
agent reads, applies, reruns
what cloud does
Cloud Check is the hosted half of the Fix Packet pipeline. The compiler runs locally; Cloud runs the validation + proof + repair-prompt generation in one round trip, writing files your agent can read on the way out.
Upload Swift, attach an Xcode project, or pipe compiled output straight from axint compile. Agents do this through MCP — humans drop a folder.
189 Apple-specific diagnostics run against your code: concurrency, accessibility, modifier order, cross-file types, plist correctness, entitlement coverage, signing assumptions, App Review heuristics.
Pass / Needs review / Fail with confidence. Top finding named precisely. Repair prompt your agent can paste into its next run. Xcode checklist for humans. Evidence trail for both.
the three verdicts cloud emits
ready_to_ship
All checks passed with high confidence. Build evidence captured. Run console written. Safe to push to App Review.
fix_required
Diagnostics caught issues your agent can correct. Cloud writes the Fix Packet — verdict, findings, file, line, repair prompt, Xcode checklist. The next agent run reads it and patches.
evidence_required
Static checks pass but runtime proof is missing. The focused UI test never ran, or the build artifact is stale. Cloud refuses ready_to_ship until the gap closes.
proof
Cloud runs the same 204 Apple-specific diagnostics that ship in the open-source compiler — but on hosted infrastructure with median sub-3-second packet generation, and zero retention by default.
Apple-specific rules running on every check
one MCP install across the stack
verdict + Fix Packet returned in seconds
by default · saved history is opt-in per project
the privacy promise
By default, checks are ephemeral: code is processed for validation and not retained unless you enable history or team workflows. Free tier never retains anything past the response.
data + privacy
The Swift, plist, and entitlement files you submit. Nothing else from your project leaves your machine unless you explicitly upload it.
On Free, nothing — checks are ephemeral. On Pro and Teams, saved reports live in your private workspace. You can purge any check or workspace from the dashboard.
Verdict, findings, AI-ready repair prompt, Xcode checklist, evidence trail. All written to .axint/cloud/report.json — agent-readable, human-skimmable, exportable as JSON or markdown.
pricing
Free Cloud Check stays free forever — that's the minimum signal an agent needs to gate the next step. Pro ships the full Fix Packet loop for daily agent-driven development. Teams adds shared history and org-level visibility for engineering organizations.
Run one hosted check. Get a verdict and packet preview. Upgrade only when you need the full repair workflow.
free · forever
Best for trying hosted validation.
best for
core value
the daily repair workflow
Best for daily agent repair loops.
best for
core value
shared history · pilot
Best for shared packet history and team workflows.
best for
core value
No surprise billing. Free Cloud Check has a generous monthly quota. Pro is a flat seat price. Teams pricing is bespoke during pilot. The open-source compiler stays Apache-2.0 forever — Cloud is additive, not a paywall around the core.
integrations
Cloud is reachable from every MCP-speaking host through the same 35 MCP tools the compiler ships with. One install command. Your agent calls axint.cloud.check and reads the verdict on the way out.
01 · agents · coding tools
Agent runtimes that call axint Cloud directly. One MCP install command and your agent has the Fix Packet contract in its toolbelt.
claude mcp add axint -- npx -y -p @axint/compiler axint-mcp
codex mcp add axint -- npx -y -p @axint/compiler axint-mcp
cursor mcp add axint -- npx -y -p @axint/compiler axint-mcp
claude_desktop_config.json · mcpServers.axint
windsurf mcp add axint
MCP-compliant host
02 · editors · IDEs
Editor and IDE integrations for humans driving the loop. The Cloud verdict surfaces inline; the Fix Packet writes to a file you can open.
MCP extension · axint server
Source Editor Extension · notarized
MCP plugin · axint
context server · axint
mcp.nvim · axint
Generic MCP host? Run npx -y -p @axint/compiler axint-mcp and Cloud is reachable. Same 35 tools, same 5 prompts, same Fix Packet contract.
try the loop
Drop in Swift or a full project check. axint Cloud returns a hosted verdict and Fix Packet your agent can act on immediately.
No signup for the free tier. The Fix Packet writes itself, the agent reads it, and the loop closes — no copy-paste, no chat back-and-forth. Open-source compiler stays Apache-2.0.