Hammer vs Quota Board

Hammer is a professional HTTP and HTTPS debugging toolkit for developers, QA engineers, mobile teams, and technical users who need a clear way to inspect, analyze, and troubleshoot network traffic on iPhone and iPad. Whether you are testing an API, debugging a mobile app, checking request headers, reviewing response data, or exporting sessions for deeper analysis, Hammer helps you understand what is happening between your app, website, and backend services. Designed for local-first network inspection, Hammer keeps captured data on your device by default. Requests, responses, headers, cookies, and session history remain local unless you choose to export or share them. How Hammer Works: Hammer uses Apple's public Network Extension framework and a Packet Tunnel Provider to enable on-device traffic capture. When you tap Start and approve the iOS system configuration prompt, Hammer creates a local Packet Tunnel. Traffic included in the active capture session is routed through Hammer's local proxy process on the same device, where requests and responses can be inspected and displayed. The Packet Tunnel does not connect your traffic to a remote VPN server. Hammer does not provide anonymous browsing, change your virtual location, or hide your public IP address. iOS displays VPN-related permission text and may show a VPN status indicator because Apple manages Packet Tunnel Provider configurations through its VPN configuration infrastructure. Key Features: Live Traffic Capture Capture HTTP and HTTPS requests in real time. Review method, host, path, status code, protocol, timing, size, and request details in a clean debugging interface. Detailed Request Inspector Inspect URL parameters, request and response headers, message bodies, status codes, timing metrics, and content types. HTTPS Debugging Use optional certificate-based HTTPS inspection in development, testing, or other authorized environments. Certificate installation and trust are controlled by the user through iOS Settings. Request History Keep capture sessions organized locally so you can revisit traffic, compare results, and investigate issues after testing. Rules and Filters Manage rules for bypassing hosts, blocking traffic, rewriting requests, mapping responses, and controlling traffic during debugging. HAR Export Export captured sessions as HAR files for desktop analysis, bug reports, team collaboration, or long-term debugging records. Local Proxy Workflow Use Hammer's on-device Packet Tunnel and local proxy workflow to inspect traffic from apps, browsers, and services you are authorized to analyze. Clean Debugging Interface Work with readable request lists, structured detail views, protocol statistics, favorites, and practical tools for repeated debugging. Local-First Privacy Captured network content is processed and stored locally by default. Hammer does not require an account, and the Packet Tunnel does not upload captured traffic to a remote VPN server. Data leaves your device only when you explicitly export, share, or submit it through a user-initiated action. Hammer is useful for: • Debugging mobile app API requests • Inspecting HTTP and HTTPS traffic • Reviewing headers, cookies, and response bodies • Testing backend services and REST APIs • Checking status codes, redirects, and timing • Exporting HAR files for issue reports • Managing traffic rules during development • Investigating network behavior during QA testing Hammer is intended for legitimate development, testing, and debugging workflows. Use it only with apps, websites, services, and network traffic that you own or have permission to inspect.

Quota Board shows Claude and Codex usage for multiple accounts, each provider on its own tab and reorderable within it. It renders the limit windows each service actually returns instead of assuming every plan has the same pair. WHAT IT SHOWS • A tab for Claude and a tab for Codex, at the same level, each refreshed by pulling down • An optional automatic order that puts the account whose weekly limit resets soonest first • 5-hour, 7-day, 30-day, model-specific, and named additional windows when reported • Claude extra-usage spending and Codex reset-credit availability when reported • The age of every reading. A stale accumulating value is marked with ≥ because it is an honest lower bound, not a current fact • Unknown data as unknown — never silently converted to 0% • English and Korean • A built-in mixed-provider demo before signing in WHAT IT CANNOT DO • Send prompts, messages, or inference requests, or consume reset credits • Ask for, capture, or store a claude.ai or ChatGPT session cookie • Import credentials owned by Claude Code or Codex • Sync credentials or back them up to another device SIGNING IN Claude uses browser OAuth and asks only for profile information. Anthropic does not offer third-party client registration, so its page displays Claude Code; Quota Board explains that before opening it. Codex uses OpenAI's device-code flow. Device login may need to be enabled in ChatGPT Security or by a workspace administrator. OpenAI does not offer a usage-only Codex scope, so the credential itself is not read-only; Quota Board's shipped code has no inference or reset-consume route and reads usage only. Codex and ChatGPT Work share usage for the selected workspace. Tokens stay in the iOS Keychain. Every request uses an honest User-Agent beginning quota-board/. PRIVACY No analytics, no Quota Board account, and no servers of ours. The app talks directly to Anthropic or OpenAI. Removing an account deletes its local credential and attempts provider revocation. Quota Board is independent and is not made by, endorsed by, or affiliated with Anthropic or OpenAI. Claude, Anthropic, ChatGPT, Codex, and OpenAI are trademarks of their respective owners, used only to identify the services the app reads.