Releases

Changelog

What changed in each release of Akev, newest first.

Every release of Akev, newest first. Downloads and checksums for each are on GitHub; updates explains how to install a new one.

Unreleased / 0.1.0

The first public release.

Getting started

  • A three-step setup on first launch: trust the certificate, pick what to capture, see the first request arrive. Settings → General opens it again (getting started).
  • Settings → AI agents (MCP): copyable setup for Claude Code, Claude Desktop, Cursor and VS Code (MCP).
  • Settings → Shortcuts: rebind any shortcut, with conflict warnings and reset (shortcuts).
  • In a browser, the UI remembers its access for each Akev address, so new tabs and bookmarks work until Akev restarts with a new token.

Capture

  • HTTP/1.1, HTTP/2, WebSockets, server-sent events and gRPC, streamed live, with a unique certificate authority per installation, which Settings → Certificates can add to your system's trust store in one click. The CA lasts 10 years; Akev warns well before it expires and never replaces it on its own (certificates).
  • Who can connect: on your network, the proxy serves this computer and private networks by default (or only listed devices, or anyone), with a block list, an optional username and password (HTTP 407 and SOCKS5), no access to this computer's localhost for other devices unless you allow it, PROXY protocol only when you trust it, and a New device connected notice with a Block button. Docker containers get the credentials in their env files (who can connect).
  • Over the network, the UI and API are served over HTTPS with a certificate from Akev's CA; plain HTTP stays for this computer (API).
  • One-click setup for Chromium-family browsers and Firefox, new and existing terminals, Android over ADB, Docker containers, Electron apps and the system proxy, plus a setup page for phones and other devices (connect clients).
  • Android: on rooted devices and emulators, the CA is also trusted as a system CA until the device restarts, Android 14's Conscrypt store included, so release apps trust it too (systemTrust: false opts out). Tested with emulators, not yet with physical phones (system trust).
  • iOS Simulator (macOS): one click trusts the CA in booted simulators; they reach Akev through the system proxy (iOS Simulator).
  • HTTP/3 over QUIC, opt-in: to servers, and from clients that talk to Akev's QUIC listener directly (HTTP/3).

Inspect

  • Formatted and decoded bodies: JSON, XML, HTML, images, protobuf and gRPC without a schema, MessagePack, CBOR and JWT.
  • One filter language for the traffic list, the CLI, the API and AI agents.
  • Timings, TLS details, client fingerprints (JA3/JA4) and the process that sent each request.
  • Compare two exchanges side by side.
  • In Traffic: a hosts and apps sidebar (click to filter, pin hosts), up to 8 request or response header columns, and a timeline: a zoomable waterfall of the visible or selected exchanges.
  • The Connection tab shows the server's whole certificate chain and why Akev trusted it (built-in roots, the system's, or your own trusted CA), or that errors are ignored.

Modify

Keep and automate

  • Sessions and autosave, on by default (the newest 20,000 exchanges or 256 MB); HAR import and export; Charles (.chlsj), mitmproxy and Fiddler (.saz) import.
  • HAR and session exports can redact secrets (on by default for HAR; akev export --redact), and AI agents see secrets as [redacted] and can only read and write files in known folders (MCP safety).
  • Bounded by default: 200,000 exchanges, 4 GB of bodies on disk, a 120 s response timeout and a 5 min body idle timeout, a memory budget for rule bodies (larger ones pass through untouched, with a notice) and breakpoint limits (limits).
  • A command line with headless capture for CI: akev capture -o traffic.har -- npm test runs the command through the proxy with the capture's own CA, writes the HAR when it exits and exits with its status (--ca-out writes that CA for anything else). Also a live tail (akev tail), akev update, and an HTTP and WebSocket API, with batched header and timing reads (POST /api/exchanges/headers, /timings) and streamed repeats (POST /api/send/repeat).
  • A built-in MCP server for AI agents: reading and searching traffic is free.

Help and updates

  • Settings → About → Copy diagnostics and Report a problem, a log file (logs/akev.log), crash reports (crashes/) and GET /api/diagnostics, all on your computer (troubleshooting).

  • A daily check for new releases while the UI is open (a small file from GitHub; turn it off in Settings → About; headless runs never check). The desktop app installs an update only when you click Update, after checking its signature (updates).

  • On Windows, the data directory is %LOCALAPPDATA%\akev (not the roaming profile), and the CA key is readable only by your account. Uninstalling with Delete the application data ticked also removes the data directory and the CA from your account's certificate store (uninstall).

Akev Pro

$49 once with a year of updates, then $25 for each further year, optional; a 14-day trial once per computer; licence keys checked offline (licensing). Pro adds script rules, TLS fingerprint impersonation, WireGuard mode, transparent capture on Linux, attaching to running JVMs, protobuf schemas, the LLM traffic lens (OpenAI, Anthropic, Gemini, Ollama, Amazon Bedrock and OpenAI-compatible APIs) and the MCP write tools.

Known limits

  • WireGuard mode hasn't been tried on a physical phone yet.
  • Release packages aren't code-signed yet: macOS and Windows ask before the first launch (see download).

Type to search guides, the CLI and the API.