Chloe Wu-Breshears
Events
Share this article
Chloe Wu-Breshears
Events
Share this article

This summer, documentation got a new main reader: agents now account for almost 80% of docs traffic. Docs have always been written for readers we’ll never meet, but more and more of those readers are no longer people at all.
That shift raises questions the people closest to it (technical writers, developer advocates, product and engineering leaders) are often working through alone inside their companies: How much context is enough? How do you write for people and agents at the same time? What should the docs experience look like when an agent reads first? That’s why we started Mintlify Context: a series of candid rooms where we can think and talk about them together.
![]()
![]()
Recapping the night
We kicked off our first Context event at the Letterform Archive with Han Wang (CEO @ Mintlify), Sarah Deaton (Technical Content Engineer @ Anthropic), and David Potes (Sr. Manager, Solutions Architecture: Data, Analytics and ML @ AWS). Here are some of our takeaways from the conversation:
![]()
- Nobody can predict the future, and that’s okay. The panel agreed early on that things have moved so fast lately that confident predictions age badly. So rather than forecasting, the conversation stayed with the questions people are working through right now.
- The Goldilocks problem. For most organizations, the problem is both too much context and not enough. Too little leaves people and agents guessing, and too much buries what matters. Finding “just enough” may look different for a person skimming a page than for an agent reading every word.
- The horse analogy. David offered an analogy that stuck with the room. We don’t ride horses to work anymore, but plenty of people still love riding them. Reading may follow the same path: you can choose a faster tool for everyday tasks and still value sitting down with something worth reading slowly.
- The medium keeps moving. How we take in documentation has always changed along with the tools we use to read it, and soon it may adapt to each reader. Imagine docs that shift their format to fit how you learn best, whether that’s a walkthrough, an example or a quick summary.
- Editor or Markdown? If agents increasingly read first, will people still need a polished, rendered docs experience, or will most knowledge live as plain Markdown files? The room didn’t settle it, but the tension is real.
- UX is now a docs question. Again and again, the conversation came back to user experience: how people actually find, read and act on information. Good docs depend as much on that experience as on the writing itself.
![]()
![]()
We came out of the room with both more answers and more questions. If you’re working on these questions too, we’d love to have you in the room next time. Keep an eye on our events page for what’s next.
More blog posts to read

Improved governance for your docs: reviews and expanded roles
Mintlify Enterprise now has stronger governance built into the editor. Require a review before any change goes live, and use expanded roles to control who can write, approve, and publish.
November 18, 2026David Isquick
Product Marketing

Mintlify Enterprise now supports linked billing with Claude Platform
Mintlify Enterprise customers can now link their Claude Platform organization to Mintlify. Anthropic bills Claude API usage in assistant, agent, Autopilot, and automations directly to their Claude organization. No API key to paste, store, or rotate.
November 17, 2026Kyle Finken
Engineering