Mezzo: Making Network Responses Something I Could Control
Request interception, recording, profiles, and a GUI turned mocking into a tool I could work with directly.

By spring 2022, Mezzo was becoming a practical tool for controlling the network behavior around application development.
The project’s public description covers a headless and GUI mocking client/server with network interception. The April-to-June commits show that description becoming more concrete: filtering, URL-backed search, recording, local and global profiles, and a React Native interceptor exposed through a Reactotron plugin.
A response is part of the development environment
When an interface depends on a service, developing it also means arranging the right service behavior. A successful response is one case. A pending request, a different payload, or an error can be just as important.
Mezzo gave those cases a place to live outside the component being built. The GUI made them inspectable; the client/server pieces made them usable by an application.
The history includes plenty of work around that central idea: selected-request highlighting, pending-request display, profile selection fixes, and mock-file path corrections. These are the details that turn a capability into a tool someone can navigate.
The broader developer-tools retrospective describes the project in the context of my work. This entry focuses on the implementation period itself. The feature commits are evidence of what I was building, without needing to turn them into a new claim about adoption or productivity.
From the project archive · Q2 2022. Written in September 2026 from repository history; the date above marks the project work, not the original publication of this retrospective. Cover art is an illustration. Source: mezzo.