Skip to content
axint docs

Cloud Check Loop

Axint and Cloud should not feel like two unrelated products.

The loop is:

  1. Build with Axint
  2. Read the check
  3. Fix what failed
  4. Rerun
  5. Ship when the result is clean

What Axint does

Axint is the local compiler + validator loop.

It gives you:

  • generated Swift
  • Apple-facing diagnostics
  • a lightweight Axint Check summary
  • a richer Fix Packet with the AI-ready repair brief

That is the fast local path.

What Cloud adds

Cloud is the saved-report layer on top of that loop.

Use Cloud when you want:

  • a free hosted check before you keep going
  • a saved report
  • a shareable result
  • a history of checks
  • a Pro repair prompt you can give back to your AI

So the mental model is:

  • Axint runs the check
  • Cloud Check gives the hosted verdict
  • Cloud Pro keeps the report and exposes the repair prompt when you sign in

The practical flow

Local-first

Terminal window
axint compile intents/LogWorkout.intent.ts --out ios/Intents/LogWorkoutIntent.swift

Axint emits:

  • .axint/fix/latest.check.json
  • .axint/fix/latest.check.md
  • .axint/fix/latest.json
  • .axint/fix/latest.md

Xcode-first

Terminal window
axint xcode packet --kind validate
axint xcode packet --kind validate --format prompt

The first command gives you the latest result plus the top repair context.
The second gives you the full repair prompt.

Cloud when you want the durable layer

Use Cloud when you want the result to become a report instead of staying only a local artifact.

That is where:

  • the result becomes shareable
  • the history becomes durable
  • the signed-in repair prompt becomes copyable
  • the loop is easier for teammates to follow

Feedback when Axint caused or missed something

When Cloud Check finds a non-passing result, the report also includes a privacy-preserving learningSignal. That signal is not the source code. It is the small bug report Axint needs in order to improve:

  • stable fingerprint
  • likely owner
  • priority
  • diagnostic codes
  • source/output shape
  • suggested engineering action

Agents can print just that signal:

Terminal window
axint cloud check ios/Intents/LogWorkoutIntent.swift --feedback

Or through MCP:

axint.cloud.check({ sourcePath: "ios/Intents/LogWorkoutIntent.swift", format: "feedback" })

Use the repair prompt to fix the current project. Use the feedback signal to turn repeated Axint failures into fixtures, generator fixes, validator rules, or docs updates.

Keep the loop simple

The right user experience is not:

  • read a wall of diagnostics
  • manually figure out what matters
  • copy random fragments around

The right user experience is:

  • read the latest packet
  • see pass / needs review / fail
  • copy one repair prompt
  • rerun

move from docs to workflow

Use the next step that matches what you need

If you just need a result, run Cloud Check. If the next agent run needs the exact repair prompt, sign in for Cloud Pro. If you need public examples or package-level status, use the examples guide and Registry compatibility page.

Run Cloud Check Start with the free result. Sign in there when you need Pro repair checks. Examples Use the examples guide when you need public product references outside this page. Registry compatibility Open package-level compatibility details when you need more than example copy. Axint site Use the main site when you want the current product overview outside the docs.