fix(langchain/agent): re-enable support for LangGraph #9016
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
| return new Proxy(agent, { | ||
| get(target, prop) { | ||
| /** | ||
| * access graph properties if not a `createAgent` function | ||
| */ | ||
| if ( | ||
| !agentMethodNames.has(prop as string) && | ||
| target.graph[prop as keyof typeof target.graph] | ||
| ) { | ||
| const value = target.graph[prop as keyof typeof target.graph]; | ||
| return typeof value === "function" ? value.bind(target.graph) : value; | ||
| } | ||
|
|
||
| const value = | ||
| target[ | ||
| prop as keyof ReactAgent< | ||
| StructuredResponseFormat, | ||
| ContextSchema, | ||
| TMiddleware | ||
| > | ||
| ]; | ||
| return typeof value === "function" ? value.bind(target) : value; | ||
| }, | ||
| }); |
There was a problem hiding this comment.
do we foresee any collisions between ReactAgent properties and CompiledStateGraph?
There was a problem hiding this comment.
This is why have a !agentMethodNames.has(prop as string) check to ensure the methods we expose from ReactAgent will be called in favor of what StateGraph exposes.
There was a problem hiding this comment.
Hmm so in that hypothetical case ReactAgent would only partially implement state graph?
There was a problem hiding this comment.
If a function like invoke or stream is implemented in ReactAgent is will prefer that over the one implemented in state graph. With the proxy it will still reach into state graph for methods not implemented in ReactAgent which will guarantee the support for LGP.
|
Closing in favor of #9117 |
If someone tries to run a
createAgentwith LangGraph, it will fail due to the fact thatcreateAgentwraps the LangGraph graph instance to provide better type security.Rather then documenting that users can just do this:
This patch makes the
createAgentfunction return a proxy that directs access to graph properties to the right object. For the user this is totally transparent.