Which Bugs AI Agents Fix Better With Traffic
A second run of our AI bug-fixing benchmark shows where captured traffic lifts agents toward 90%, why service maps barely help, and which bugs still fail.
Posts about developer tools
Browse 55 posts in this category
Beware of PII in Testing Data: The Security Iceberg and Where PII Actually Hides
Using 'production-similar' data in pre-production is a major security risk. Learn why traditional masking fails, where hidden PII hides, and how to fix it.
Fixing 403 auth errors when you replay traffic
Replay an authenticated flow and the protected calls fail with 403. Here is how proxymock recommendations fix the expired bearer token in one click.
Capture once, test forever
Production traffic is the most complete record of what your system does, and most teams throw it away. One capture powers reproduce, validate, and sandbox.
Logs told me something broke. Traffic showed me what.
Capture production traffic and store it in your own Elasticsearch with Speedscale BYOC. Pull it locally with es-gather.py and reproduce bugs with proxymock.
Your AI agent is fixing the wrong service
I tested 100 bugs across 240 microservices the model has never seen. Alert only: 51% pass rate, wrong service 34% of the time. Traffic captures: 77%.
The Kubeshark Workflow That Doesn't Stop at the Dashboard
A Kubeshark alternative that goes beyond observability. Stream live cluster traffic into proxymock, then replay or mock it locally from your laptop.
WireMock alternatives: pick the one that fits your problem
A 2026 take on WireMock alternatives. Keep WireMock for what it's good at; add Microcks (now CNCF Incubating) or proxymock for the gaps. The honest map.
Anatomy of the AI Software Factory: The Context Layer
Explore the technical architecture of the AI Software Factory, focusing on tool convergence and the Unified Context Layer.