Swift

I spent the last day and a half building Wispr, a macOS menu bar app for local speech-to-text transcription. The app runs entirely on-device using OpenAI’s Whisper models, captures audio via a global hotkey, and inserts transcribed text at your cursor position in any application. Here’s the thing. I didn’t write a single line of code myself. I used Kiro CLI, Amazon’s AI coding agent, to handle the entire implementation. But this wasn’t “vibe coding” where you throw prompts at an AI and hope for the best. This was a structured, spec-first development process that produced production-quality Swift code with modern concurrency patterns, proper SwiftUI architecture, and zero technical debt. ...

In my previous post, I showed how to route Xcode 26.3 coding agent through OpenRouter to reach Claude models on Amazon Bedrock. That works well for personal projects and quick demos, but it has one obvious limitation: your code, your prompts, and your AI-generated suggestions all transit through OpenRouter’s servers on their way to Bedrock and back. For many of us working on proprietary codebases, that is a non-starter. Customers who want to keep their data within the security perimeter of their own AWS account cannot use a third-party proxy, no matter how convenient it is. The data has to stay on a path you control, end to end. ...

Xcode 26.3 RC ships with a built-in coding agent. Out of the box, it supports OpenAI Codex and Anthropic Claude. You pick your provider, enter your API key, and you’re good to go. That’s great for getting started quickly. But here is the thing. When you use Claude directly through Anthropic’s API, your code, your prompts, and your context all travel through Anthropic’s infrastructure. For a personal side project, that’s probably fine. For anything related to your company’s codebase, you might want to think twice. I know I did. ...