From 5d88535f7a52d5a93276edb3c634be7b84e764e8 Mon Sep 17 00:00:00 2001
From: owenpearson <owen.pearson@ably.com>
Date: Fri, 10 Jul 2026 11:51:32 +0100
Subject: [PATCH 1/2] ait: remove technical content from getting started index

---
 src/pages/docs/ai-transport/index.mdx | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/src/pages/docs/ai-transport/index.mdx b/src/pages/docs/ai-transport/index.mdx
index 5cc184cd5a..6e2a80383b 100644
--- a/src/pages/docs/ai-transport/index.mdx
+++ b/src/pages/docs/ai-transport/index.mdx
@@ -46,10 +46,6 @@ AI Transport is for conversations between a user and an AI agent. If you are bui
 ]}
 </Tiles>
 
-<Aside data-type='important'>
-AI Transport requires one [channel rule](/docs/ai-transport/getting-started/channel-rules), **Message annotations, updates, deletes, and appends**, enabled on the namespace your conversations live on. It is a one-time setup per Ably app, and streaming fails without it.
-</Aside>
-
 ## Read next <a id="read-next"/>
 
 - [Concepts](/docs/ai-transport/concepts): the building blocks (sessions, turns, transport, codec, conversation tree, infrastructure).

From 26fd0cd752a0c23e9eaa7a773d543751845737d8 Mon Sep 17 00:00:00 2001
From: owenpearson <owen.pearson@ably.com>
Date: Fri, 10 Jul 2026 11:51:49 +0100
Subject: [PATCH 2/2] ait: add introduction to getting started authentication
 guide

---
 .../docs/ai-transport/getting-started/authentication.mdx      | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/pages/docs/ai-transport/getting-started/authentication.mdx b/src/pages/docs/ai-transport/getting-started/authentication.mdx
index cbe191dd03..97d80c756f 100644
--- a/src/pages/docs/ai-transport/getting-started/authentication.mdx
+++ b/src/pages/docs/ai-transport/getting-started/authentication.mdx
@@ -5,7 +5,11 @@ meta_keywords: "AI Transport, authentication setup, Ably JWT, authCallback, toke
 intro: "AI Transport authenticates through your existing auth: your server validates the user and signs an Ably token, and the browser's Ably client fetches it through `authCallback`and refreshes it before expiry."
 ---
 
+<Aside data-type='note'>
 This page is the practical setup. For the conceptual model (the three auth layers, capabilities, token lifecycle, cancel authorisation), see the [authentication concept](/docs/ai-transport/concepts/authentication).
+</Aside>
+
+AI Transport reuses the authentication you already have. Your server validates the user and signs a short-lived Ably JWT, scoped to the channels that user can reach. The browser's Ably client fetches that token through an `authCallback` and refreshes it before it expires, so the connection stays authenticated for the whole conversation. The steps below wire up the server endpoint, the client, and the separate POST that wakes the agent.
 
 <Aside data-type='important'>
 Never embed an Ably API key in client-side code. API keys do not expire and are not suitable for untrusted clients.