From aceda56a5f3aa65144bef18278d739f3ce779e36 Mon Sep 17 00:00:00 2001
From: Kurtis Van Gent <31518063+kurtisvg@users.noreply.github.com>
Date: Tue, 14 Apr 2026 18:06:35 +0000
Subject: [PATCH] fix: update decision with outcome

---
 docs/sessions-vs-sessionless-decision.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/sessions-vs-sessionless-decision.md b/docs/sessions-vs-sessionless-decision.md
index a5c2373..efd43db 100644
--- a/docs/sessions-vs-sessionless-decision.md
+++ b/docs/sessions-vs-sessionless-decision.md
@@ -252,4 +252,10 @@ deploy_vm(vm)
 
 * **Breaking Change:** If applications are using sessions today for application
   state, it would require developers to update their tools and clients to use
-  explicit state handles instead. 
+  explicit state handles instead.
+
+## **Decision**
+
+This decision was discussed at the [Core Maintainer's Meeting on
+4/1](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/2536)
+and the decision was made to move forward with the "no-session" proposal.