Reference

How builds work

The pipeline

  1. Queue. Your message becomes a build job in the database.
  2. Claim. A build machine (an Apple-silicon Mac) claims the oldest queued job. Follow-ups go to the machine that holds your project's source.
  3. Write code. Claude Code writes or edits SwiftUI source in your project.
  4. Compile. swift build -c release. Compile errors are fed back to the AI to fix, up to two times.
  5. Package. The executable is assembled into a .app bundle with an Info.plist and ad-hoc signed.
  6. Upload. The bundle is zipped and stored, and the download link appears in your chat.

What a project is

A Swift package with one executable target, App, whose source lives in Sources/App/. There is no Xcode project file. See How silicondevkit.com builds your app with Swift Package Manager.

What is recorded

For each build we record the prompt, how long each stage took, the AI token usage and cost, the request's IP address, your browser or app type, and a log of the build stages and compiler errors. This is used to run the service and plan usage limits.

More

The overview post: How silicondevkit.com works.