Skip to content
Axint

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 durable report layer on top of that loop.

Use Cloud when you want:

  • a saved report
  • a shareable result
  • a history of checks
  • a clearer report for teams or repeat runs

So the mental model is:

  • Axint runs the check
  • Cloud keeps the report

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 check --kind validate
axint xcode packet --kind validate --format prompt

The first command answers “did it pass?”
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 verdict becomes shareable
  • the history becomes durable
  • the loop is easier for teammates to follow

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:

  • run the check
  • see pass / needs review / fail
  • copy one repair prompt
  • rerun