01
Preserve the complete Apple evidence
Build logs, result bundles, test attachments, and generated reports remain available for deep inspection. The model-facing packet stays small enough to use in the repair turn.
AI Swift build errors
Give the next agent turn the failure, the evidence, and the exact rerun.
Large Xcode logs are poor model context. Axint keeps the complete build and result artifacts on disk, then gives the agent a compact packet with the active finding, likely files, supporting evidence, proposed repair, and command that proves the next attempt.
proof and repair
$axint prove --dir /path/to/MyApp --fixartifact
Fix Packet
jobs
status · cancel · rejoin
evidence
build · test · runtime
02
Resume instead of restarting
Long Xcode jobs can be started, checked, canceled, and rejoined. A context interruption does not have to throw away the build state or force the agent to repeat expensive work.
03
Apply only deterministic fixes automatically
Opt-in repair applies supported mechanical rewrites, records exactly what changed, and reruns proof. Findings that require product judgment remain proposals for review rather than silent source edits.
common questions
Does a Fix Packet contain my full source code?
The source-free receipt does not. Local repair artifacts may name project-local files and excerpts as configured, while hosted workflows disclose their handling before upload.
Can an agent verify that the repair worked?
Yes. The packet carries the rerun command, and the subsequent proof reconciles the new static, build, test, and runtime evidence.
continue