If you build iOS apps with AI, you've probably hit a wall the second you leave your text editor. Writing logic is fast. Getting the agent to manage simulators, configure a local database, and push a build to App Store Connect is a nightmare of brittle shell scripts.

Blitz fixes that deployment gap. It is a native macOS app built specifically to hand the iOS lifecycle over to your agents. You can grab the source straight from their GitHub repository.

The app requires macOS 14 or later and wires directly into Xcode. The real magic comes from its built-in Model Context Protocol server. You boot up Blitz, and clients like Claude Code ...

Anthropic's Claude Max dashboard gives you a vague "weekly utilization" percentage. It's a frustratingly opaque metric when you're trying to figure out if the subscription is actually saving you money compared to just hitting the API.

Someone finally ran the numbers. A recent Reddit post and experiment tracked 80 autonomous coding tasks, simultaneously measuring the per-task API-equivalent cost and the change in that elusive weekly percentage. The resulting math gives us a concrete dollar value for a full weekly limit.

Here is what the limits are actually worth in API pricing:

• Max 5x ($100/mo): A full week is worth about $523. That's roughly 20x ...

While testing Theo 6.0, our Swift driver for Neo4j, I made an interesting discovery: Theo works with Memgraph out of the box!

The Discovery

Memgraph is a high-performance graph database that implements the Bolt protocol - the same binary protocol that Neo4j uses for client communication. Since Theo communicates with Neo4j using the Bolt protocol (versions 3.0 through 5.6), I was curious to see if it would work with Memgraph.

Testing Setup

I spun up a Memgraph container using Docker:

docker run -d --name memgraph \
  -p 7696:7687 \
  memgraph/memgraph:latest \
  --bolt-server-name-for-init="Neo4j/"

The --bolt-server-name-for-init flag is important - it ...

Following on from the Bolt-swift 6.0 release, Theo has also been modernized for Swift 6. Theo is the high-level Neo4j client library that sits on top of Bolt-swift, providing a more convenient API for working with graph data in Swift.

The name comes from the combination of "Neo" (as in Neo4j) and "Thomas" (Thomas Anderson being Neo's real name in The Matrix). It's been around since 2016, originally created by Cory Wiles, and I've been maintaining it since version 3.

The Swift 6 update brings the same concurrency improvements as Bolt-swift. The library now properly supports Swift's strict concurrency checking, with Sendable conformances throughout. This means you can use Theo safely in concurrent code without worrying about data races.

Here's ...

It's been a while since Bolt-swift got some love. The library has been quietly working away for many users, but Swift has evolved significantly since the last major release, and Neo4j has moved on, so it was time for an update.

The main driver for this release was getting the library to work with modern Neo4j versions. I kept getting reports that connections to Neo4j 5.x were failing. Now the library works across the full spectrum from Neo4j 3.5 all the way to Neo4j 2025.12.1.

While I was in there, I took the opportunity to modernize the codebase for Swift 6. The library now uses Swift's structured concurrency with async/await, which makes for much cleaner code than the old EventLoopFuture-based approach. You can now write queries like this:

let connection = try await Connection.connect(
  ...