From 74d50cd30cbb5a707843de99c46b0ff82b022a1b Mon Sep 17 00:00:00 2001
From: "tembo[bot]" <208362400+tembo[bot]@users.noreply.github.com>
Date: Tue, 18 Aug 2026 13:05:14 +0000
Subject: [PATCH] docs: clarify free-plan sessions stop immediately on credit
 limit

---
 resources/pricing.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/resources/pricing.mdx b/resources/pricing.mdx
index 0930800..d6fce49 100644
--- a/resources/pricing.mdx
+++ b/resources/pricing.mdx
@@ -99,11 +99,11 @@ Tembo Gateway and VM compute are metered while Tembo runs work such as:
 
 What happens when your balance reaches zero depends on your plan and overage setting:
 
-- **Free**: new sessions are blocked until you upgrade or add prepaid balance.
+- **Free**: new sessions are blocked until you upgrade or add prepaid balance. A running session is also stopped immediately if it exceeds the free allowance mid-session, with a message in the chat explaining why.
 - **Pro or Max with overages enabled**: sessions continue and are billed as overage after the included allowance and prepaid balance are used, up to the maximum overage limit you set. Once that limit is reached, new sessions are blocked.
 - **Pro or Max with overages disabled**: new sessions are blocked as soon as the included allowance and prepaid balance are exhausted.
 
-When work is blocked, the request is rejected immediately rather than queued. Work that has already started can continue its current session so its compute and inference are accounted for correctly.
+When work is blocked, the request is rejected immediately rather than queued. On Pro and Max, work that has already started can continue its current session so its compute and inference are accounted for correctly. On Free, a running session is stopped as soon as it exceeds the allowance, rather than continuing to completion.
 
 ## Usage bursts