axint cloud · the repair brain

The brainyour agent calls.

Cloud is the hosted Apple-native validator. Your agent sends code, Cloud sends back a Fix Packet, the agent acts on it. You log in once.

Most usage runs straight from the terminal — axint cloud check inside Claude Code, Codex, Cursor, or any agent that writes Apple code. The web is here for two reasons: connect your terminal, and a manual playground for the rare case you want to paste code by hand.

Connect your terminalTry the playground

Limited preview — log in once and the full Repair Loop is free. Saved packet history, larger checks, agent handoff, all of it.

how agents use cloud

One login.Every agent. Every session.

The compiler is open source on npm and PyPI. Install once, log in once, and any agent that drives a terminal can call Cloud forever.

step 01

install.

$ npm i -g @axint/compiler
or pipx install axint

Compiler ships on npm and PyPI. Same CLI, both runtimes. Open-source on github.com/agenticempire/axint.

step 02

connect.

$ axint login

Opens a browser, you authorize with GitHub, the CLI stores a token. Cloud now answers every call this machine makes.

step 03

agent runs check.

$ axint cloud check intent.ts

Or any agent that drives the terminal. Cloud returns a Fix Packet — verdict, findings, repair prompt, next command.

limited preview

Log in once. Get the full Repair Loop — free, on every agent session, for every project.

what cloud returns

A Fix Packet,not a wall of logs.

The Fix Packet is a structured artifact your agent reads to repair the code. Verdict for the human, findings for context, repair prompt for the next agent turn, and a single next command — so the loop continues without human intervention.

verdict — ready_to_ship · fix_required · evidence_required — one of three protocol states the agent dispatches on

findings — every Apple-native diagnostic the validators surfaced, with location and code

repair_prompt — the exact instruction your agent feeds back to its model on the next turn

next_command — the literal CLI to run after the agent applies the fix — keeps the loop closed

fix_packet.json

what the agent receives
{
  "verdict": "fix_required",
  "confidence": 0.91,
  "findings": [
    {
      "code": "AX781",
      "message": "Optional argument mismatch on EntityQuery",
      "file": "intents/create-event.ts:42"
    }
  ],
  "repair_prompt": "EntityQuery requires non-optional...",
  "next_command": "axint xcode check",
  "agent_message": "Apply repair_prompt then re-run"
}

free check · in this browser

Or paste it here.Same engine, no terminal.

For the rare case you want to see Cloud without your agent. Paste Apple code, upload a file, or pull a registry package — same Fix Packet comes back.

Run free check

One signed-in account unlocks the full Repair Loop — packet history, larger checks, agent handoff, reruns. Free during limited preview.

the repair loop

One check. Four moves. Run → packet → repair → rerun → ship. The free check stops at the verdict — Pro keeps the loop running until the build is clean.

01step 01

Read source

02step 02

Validate output

03step 03

Generate Fix Packet

04step 04

Return next command

run cloud check

One input. One run. If something fails, Cloud returns a Fix Packet you can copy straight back into your agent.

Start from a built-in example, or replace it with your own code and run the check from the same screen.
run this check
Use the current sample, or replace it with your own code and open the result right away.
You are one step away from the result

16 lines · App Intent · TypeScript

Cloud save is off. Creating a public URL or private workspace save will ask you once to confirm what gets stored. .

Preview runs stay in this browser. Saving creates a private workspace record, and creating a link makes a public URL on purpose.

Need a quick example?
These built-in examples are here to help you see the flow fast, not to get in the way of your own code.