You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/website/content/docs/choosing-an-adapter/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,9 +123,9 @@ AWS Strands and Microsoft Agent Framework both read the protocol-standard top-le
123
123
The LangGraph bridge reads `forwardedProps.command.resume`.
124
124
You pass one neutral `submit({ resume })`, and the adapter derives the wire shape from how the interrupt arrived.
125
125
126
-
**The Mastra row was measured, but not in the hosted demo.**
126
+
**The Mastra row is hosted on its own lane.**
127
127
Its cells come from a real Mastra server driven with live model calls, and its transcripts are committed and replayed like the others.
128
-
Unlike the Strands and Microsoft Agent Framework rows, it is not yet running in the hosted demo deployment.
128
+
Unlike the Strands and Microsoft Agent Framework rows, it is not served by the shared FastAPI deployment: upstream ships no plain AG-UI HTTP endpoint, so its backend is a separate Node service.
129
129
130
130
**Subagents are red for every third-party runtime, and none of those reds are a bug.**
131
131
The three runtimes do not fail to implement one thing; they model delegation three different ways.
0 commit comments