Rockxy is not your typical HTTP proxy. It’s a native macOS app built with Swift that intercepts HTTPS traffic, lets you inspect and mock API responses, and even debug WebSocket and GraphQL connections. But what really sets it apart is its integration with AI assistants like Claude, allowing you to query live network traffic directly from chat — turning network debugging into a conversational observability layer.
what rockxy does and how it’s built
At its core, Rockxy is an open-source HTTP debugging proxy designed specifically for macOS. It’s written entirely in Swift, leveraging SwiftNIO for the proxy engine, SwiftUI and AppKit for the UI, and incorporates several macOS-specific technologies like OSLog and XPC for security and process correlation.
Rockxy works as a man-in-the-middle (MITM) proxy, dynamically generating TLS certificates per host to intercept HTTPS traffic securely. It supports CONNECT tunneling for HTTPS and handles WebSocket and GraphQL protocols, enabling deep inspection and manipulation of live API traffic.
The UI combines SwiftUI with AppKit’s NSTableView to efficiently display 100,000+ requests with zero lag using virtual scrolling, a practical choice for handling large volumes of network data without compromising responsiveness.
Key architectural components include:
- SwiftNIO proxy engine: Handles asynchronous network I/O and proxy logic, including TLS interception and CONNECT tunnels.
- Sandboxed JavaScriptCore plugin system: Enables users to write custom plugins to inspect or mock traffic, with execution timeouts and strict input validation.
- OSLog correlation: Maps intercepted requests back to originating macOS processes, helping identify which app generated which network call.
- XPC helper: Enforces security by validating certificate chains and sandboxing critical operations.
- MCP server: Bundled with Rockxy, this server enables AI assistants like Claude CLI to query live traffic, proxy rules, and status programmatically.
The project targets macOS 14.0+ and requires Xcode 16+ and Swift 5.9, which reflects its use of the latest Apple platform features.
technical highlights and tradeoffs
What distinguishes Rockxy is the depth of integration with macOS internals combined with modern Swift concurrency and UI paradigms.
The proxy engine is built on SwiftNIO, a low-level asynchronous networking framework. This choice enables high concurrency and performance but demands careful management of async flows and error handling. Rockxy also implements MITM TLS interception with auto-generated per-host certificates, a complex, security-sensitive feature requiring careful certificate chain management and user trust setup.
The UI’s use of NSTableView with virtual scrolling for 100k+ requests is a pragmatic tradeoff. SwiftUI’s List lacks the maturity or performance for such large datasets, so the blend with AppKit components achieves scalability without sacrificing native UI feel.
The sandboxed JavaScriptCore plugin system is another smart design. Plugins can manipulate or mock traffic but run under strict 5-second timeouts and input validation boundaries to avoid hangs or security issues. This balances extensibility with safety.
Security is enforced through an XPC helper that validates certificate chains and isolates privileged operations. This design keeps the main app sandboxed and reduces attack surface.
The OSLog correlation feature is a valuable addition for macOS developers, linking network requests back to originating processes. This is often missing in generic proxies and helps in real-world debugging.
The MCP server integration is particularly interesting. It exposes Rockxy’s live traffic and proxy state to AI assistants like Claude, turning the proxy into a queryable observability backend. This integration could pave the way for AI-assisted network debugging workflows.
Limitations and tradeoffs include:
- macOS 14+ requirement limits users on older systems.
- Native Swift and SwiftNIO stack means no cross-platform support.
- Complexity of TLS interception setup (root CA installation) might be a barrier for casual users.
- Plugin system timeout and sandboxing might restrict more complex or long-running scripts.
quick start
git clone https://github.com/RockxyApp/Rockxy.git
cd Rockxy
open Rockxy.xcodeproj
Build and run in Xcode. The Welcome window guides you through root CA setup, helper installation, and proxy activation.
Requirements: macOS 14.0+, Xcode 16+, Swift 5.9
If you want to connect Rockxy to Claude after installation, see the MCP Integration guide.
verdict
Rockxy is a solid, macOS-native HTTP debugging proxy that brings together modern Swift concurrency, native UI components, and AI integration in a unique package. Its architecture is well thought out, emphasizing security, scalability, and extensibility through sandboxed plugins.
It’s particularly relevant for developers and power users on macOS who need deep network inspection, especially when working with APIs that use WebSocket or GraphQL. The OSLog correlation and AI query capabilities add practical value.
That said, it’s not a cross-platform tool, and the reliance on macOS 14+ plus Xcode 16+ means it’s targeting a relatively recent Apple ecosystem. The TLS interception setup is typical for proxies of this class but requires some user investment.
If you’re looking for a native macOS proxy with an eye toward AI-assisted observability and don’t mind the platform constraints, Rockxy is worth exploring.
→ GitHub Repo: LocNguyenHuu/Rockxy ⭐ 372 · Swift