docs(adapters): integrate thread-loading design into existing guides#470
Merged
Conversation
Three contextual touches — no new sections.
writing-an-adapter.mdx (Agent contract, chat docs)
AgentWithHistory section already covers the structural choice. Adds a
'Hydrating from a server-stored thread' subsection naming the parallel
behavioral choice every adapter author has to make ('should
threadId-change repopulate messages from the server?') and shows how
the two reference adapters answer it differently: LangGraph yes via
client.threads.getHistory; AG-UI no because the protocol carries
events not snapshots. Cross-links both adapter docs.
ag-ui/concepts/architecture.mdx
Provider choices section now clarifies threadId is a plain string
consumed at construction (not a Signal) and names the two patterns
AG-UI consumers use to switch threads: recreate the provider via
re-injection, or use the LangGraph adapter. The existing 'History
and time-travel out of scope' bullet is expanded to explain *why*
(protocol-level, not a TODO) with a back-link to Provider choices
and a forward-link to the Writing an Adapter guide.
agent/guides/persistence.mdx
Adds a single callout at the top framing this whole guide as
adapter-defined behavior the LangGraph adapter implements because
the LangGraph protocol supports it. Cross-links to writing-an-adapter
for adapter authors who want the design context. Rest of the page
stays LangGraph-focused.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three contextual touches that explain how thread loading differs between adapters — woven into existing docs where developers are already looking, not appended as new sections.
Where this lives
Why this approach
A developer arriving at any of these three docs from a different starting point — adapter author, AG-UI consumer, LangGraph consumer — now finds the thread-loading story explained at the level they care about, with consistent cross-links between the three sources. No standalone "Thread loading" doc that competes with any of them.
Test plan
🤖 Generated with Claude Code