Developer Experience with AI Coding Agents: HTTP Behavioral Signatures in Documentation Portals
Oleksii Borysenko

TL;DR
This study analyzes HTTP request signatures of AI coding agents and assistants accessing developer documentation, revealing behavioral patterns that impact documentation engagement metrics and suggesting practical improvements for developer portals.
Contribution
It provides the first empirical analysis of HTTP signatures of AI coding agents and proposes practical adaptations for documentation portals based on these insights.
Findings
AI agents compress multi-page navigation into few requests
Traditional engagement metrics are unreliable for AI-driven documentation access
Practical recommendations include new documentation standards and analytics tools
Abstract
The rapid adoption of AI coding agents and AI assistant web services is fundamentally changing how developers discover, consume, and interact with technical documentation. This paper studies that transformation across three interconnected dimensions: documentation accessibility, content analytics, and feedback systems. We present an empirical study of HTTP request fingerprints from nine AI coding agents (Aider, Antigravity, Claude Code, Cline, Cursor, Junie, OpenCode, VS Code, and Windsurf) and six AI assistant services (ChatGPT, Claude, Google Gemini, Google NotebookLM, MistralAI, and Perplexity) accessing a live developer documentation endpoint, revealing identifiable behavioral signatures in HTTP runtime environments, pre-fetch strategies, User-Agent strings, and header patterns. Our study shows that AI agent access compresses multi-page navigation into a single or two requests,…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
