Support
Need a hand with Charlotte? Read the user manual, check the FAQ below, or send us a message — we read every email and reply as soon as we can.
Contact us
Email us with the Charlotte version, your operating system, and what you were trying to capture. The button opens your default email app.
Email supportFrequently asked questions
What are the system requirements?
Charlotte is available for Windows through the Microsoft Store and for macOS through the Mac App Store. Both are native desktop apps with the same debugging workflow, feature set, and interchangeable session files.
How do I decrypt HTTPS traffic?
In Settings, generate a Charlotte root CA (or import your own), then install and trust that certificate on the device whose traffic you want to inspect. Charlotte's Device Setup walks you through it, including a QR code for physical devices.
Why can't Charlotte read some traffic (QUIC / HTTP/3)?
Charlotte cannot decrypt QUIC. It can detect hosts that advertise HTTP/3 and optionally force an HTTP/2 fallback so they stay interceptable. Certificate-pinned apps on excluded hosts are blind-tunnelled so they keep working.
Where is the user manual?
The user manual covers both apps step by step: the root certificate, capturing from this computer, phones, simulators and emulators, filters, tools, sessions, the command line, and troubleshooting.
Sign-in fails for an intranet app that uses Active Directory (Kerberos / NTLM)
From Charlotte 2.1 for macOS and 2.2 for Windows, Charlotte keeps NTLM and Negotiate (Kerberos) handshakes on one connection automatically. If the server still rejects a complete ticket, it is enforcing Extended Protection (channel binding), which ties the ticket to the server's certificate. The flow's Overview says so and offers two fixes: let Charlotte sign in to that host for you, or stop decrypting it. On earlier versions, add the host to SSL Proxying → Exclude hosts. See Active Directory, Kerberos and NTLM in the manual.
Does my traffic or data get sent anywhere?
No. Captured traffic is processed locally on your machine. Optional AI features run locally when available, and the MCP server is loopback-only and disabled by default. See our Privacy Policy.
How do I connect an AI agent via the MCP server?
Enable the MCP server in Settings and connect Claude, OpenAI Codex, GitHub Copilot, Cursor, or another MCP client at http://127.0.0.1:8765/. For clients that launch a subprocess, run Charlotte --mcp-stdio.
What's included in Charlotte Pro?
Pro unlocks Map Remote / Map Local / Rewrite tools, breakpoints, throttling & chaos, on-device AI, and the MCP server. You can manage your license in Settings.