blitz-mac

blitzdotdev/blitz-mac is ranked 3,788 among these 8 peers; wwbin2017/bailing is ranked 3,783.

Blitz Native macOS App Store Connect tool with MCP. Submit iOS apps, manage IAPs, and automate App Store submission with AI agents. It gives Claude Code (or any MCP client) full control over the iOS development lifecycle: running simulators, configuring in-app purchases, uploading screenshots, and triggering App Store review submissions, all from a single native macOS GUI. If you are fighting App Store Connect to get your app submitted, Blitz automates the painful parts. Auto-installed, shared auth, available

in every Blitz agent session | Download Blitz Download from blitz-mac. We launched **teeny CLI**, a CLI that lets your agent define a complete backend in one TypeScript file and deploy to Cloudflare's infra. Your agent handles everything: **Auth**: sign-up/sign-in users in with Google, GitHub, Discord, or email/password **Database**: store and query your app's data with row-level security so users only see their own **File storage**: upload and serve files from Cloudflare R2, serve up

to 10GB of content to your customers **Server logic**: write arbitrary endpoints to handle Stripe payments, rate limits, and custom business logic your app needs You get up to 5 free backends you can deploy when you register in the terminal via . Each free backend gives you: 1M requests/month (Cloudflare Worker) 100MB SQLite database (Cloudflare D1) 10GB file storage (Cloudflare R2) That's enough to cover 5 apps with 1K daily active users without paying a cent. Install with Then

tell your agent Build Blitz from source **Requirements:** macOS 14+ · Xcode 16+ · Node. 26+ For signed builds, copy to and fill in your Apple Developer credentials, then run: The ASC helper binary bundled into the app is built from the pinned submodule at . If you need to override that source during development or CI, set or point at a prebuilt compatible helper binary. Verify a release binary Every GitHub release includes with checksums of the CI-built binary. To verify

: **Option 1: Check a downloaded binary against release checksums** **Option 2: Build from source and compare** This builds the app locally and compares the main executable checksum against the release. CI builds use ad-hoc signing, so checksums match when you build with the same toolchain. **Option 3: Inspect the CI build yourself** All release binaries are built by the public GitHub Actions workflow. Security and privacy **Minimal telemetry in official releases only. ** GitHub release builds may embed a build

-time analytics endpoint and token and send anonymous product telemetry. Source builds, forks, and debug builds stay off by default unless you explicitly embed analytics config while bundling. ** App launches, Blitz project type inventory/create/import events, and MCP/App Store Connect tool usage events. Each event includes an anonymous device ID stored at , app version, OS version, event name, timestamp, and when applicable ( or ), normalized command type, success, and duration. **What official telemetry never records. ** No project names, paths

, bundle IDs, CLI args, App Store Connect form values, file names, prompts, terminal contents, or user content. ** If you enable