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
better document what the first argument to a RemoteGraph can be (#116)
when using RemoteGraph for a couple weeks, I noticed unexpected behavior
that I could give either an assistant ID or a graph name as the first
argument when instantiating a RemoteGraph.
Turns out this is by design, but it was not documented.
---------
Co-authored-by: Kathryn May <[email protected]>
Copy file name to clipboardExpand all lines: src/langgraph-platform/use-remote-graph.mdx
+26-2Lines changed: 26 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ sidebarTitle: Interact with the deployment using RemoteGraph
14
14
15
15
When initializing a `RemoteGraph`, you must always specify:
16
16
17
-
*`name`: the name of the graph you want to interact with. This is the same graph name you use in `langgraph.json` configuration file for your deployment.
17
+
*`name`: the name of the graph you want to interact with**or** an assistant ID. If you specify a graph name, the default assistant will be used. If you specify an assistant ID, that specific assistant will be used. The graph name is the same name you use in `langgraph.json` configuration file for your deployment.
18
18
*`api_key`: a valid LangSmith API key. Can be set as an environment variable (`LANGSMITH_API_KEY`) or passed directly via the `api_key` argument. The API key could also be provided via the `client` / `sync_client` arguments, if `LangGraphClient` / `SyncLangGraphClient` were initialized with `api_key` argument.
19
19
20
20
Additionally, you have to provide one of the following:
@@ -35,17 +35,29 @@ Additionally, you have to provide one of the following:
0 commit comments