Where AX comes from in this material The term shows up in Every's discussion of Proof, their collaborative editor built for humans and agents to work in together. Kieran frames it directly: AX (agent experience) is as important as UX [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@1031]. The idea is that when your product is meant to be used by agents — not just by people — you must design deliberately for how agents encounter, understand, and operate in it. How AX gets designed for in practice Proof's team treats agent experience as something you can actively improve: - Ask the agents. You can optimize AX simply by asking the agents what confused them — agents themselves can tell you where your product's agent-facing design breaks down [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@1031]. - Keep onboarding low-friction. Proof's agent onboarding is copy-paste a snippet to your agent — no skill or account needed [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@999]. - Prefer external, context-rich agents. Dan found an embedded internal agent weak: what you actually want is your own Claude — the one that already knows you — in the document as a co-author [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@593]. The takeaway AX sits alongside UX as a first-class design concern for agent-native products. Designing for it means making it trivially easy for agents to connect, giving them room to act, and iterating on their experience the same way you iterate on a human's. - AX (agent experience) is treated in this channel's material as as important as UX for agent-native products [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@1031]. - A surprising optimization technique: ask the agents what confused them [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@1031]. - Proof keeps agent onboarding deliberately low-friction — copy-paste a snippet, no skill or account [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@999]. - Design favors the user's own context-rich external agent over a weak embedded internal one [^6fa3b152-7803-5980-8bf0-36fdcc722a1c@593].