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

arXiv: https://arxiv.org/abs/2604.02544 · HTML: https://mlsanity.com/paper/2604.02544/

## Key facts

- Cited by 1 papers in the map (data through 14 Oct 2026).
- Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use.
- Builds on 6 of its 26 references that are in the map.
- First posted on arXiv 2 Apr 2026.

## Placed in

- LLM agents and tool use / [Software engineering coding agents](https://mlsanity.com/agents/software-engineering-coding-agents/)

## Builds on (most cited first, 6 of 6)

- [Dated Data: Tracing Knowledge Cutoffs in Large Language Models](https://mlsanity.com/paper/2403.12958/) (2024)
- [Somesite I Used To Crawl: Awareness, Agency and Efficacy in Protecting Content Creators From AI Crawlers](https://mlsanity.com/paper/2411.15091/) (2024)
- [Developer Interaction Patterns with Proactive AI: A Five-Day Field Study](https://mlsanity.com/paper/2601.10253/) (2026)
- [Developers' Experience with Generative AI -- First Insights from an Empirical Mixed-Methods Field Study](https://mlsanity.com/paper/2512.19926/) (2025)
- [Towards a Science of Developer eXperience (DevX)](https://mlsanity.com/paper/2506.23715/) (2025)
- [Toward an AI-Native Internet: Rethinking the Web Architecture for Semantic Retrieval](https://mlsanity.com/paper/2511.18354/) (2025)

## Built on by (most cited first, 1 of 1)

- [Identifying AI Web Scrapers Using Canary Tokens](https://mlsanity.com/paper/2605.13706/) (2026)

## Abstract (arXiv)

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, GitHub Copilot (VS Code agent mode), 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, making traditional engagement metrics - session depth, time-on-page, click path, and bounce rate - unreliable indicators of actual documentation consumption. We discuss practical adaptations for developer portal teams, including tokenomics-aware documentation design, adoption of emerging machine-readable standards (AGENTS.md, llms.txt, skill.md, agent-permissions.json), MCP server-based feedback channels, and analytics instrumentation for AI referral traffic.