Skip to content

docs(state)!: inspect_state is a coroutine, so the graph must be awaited #134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ciaransweet merged 1 commit into from
Sep 10, 2026
Merged

docs(state)!: inspect_state is a coroutine, so the graph must be awaited #134

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/CONSUMING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -601,6 +601,13 @@ agent = create_agent(
readable; `state_keys(published)` is passed so a read that misses can say
"declared, but no tool has published it yet" instead of "no such key".

**`inspect_state` is a coroutine, so drive the graph asynchronously** —
`await agent.ainvoke(...)`, or `stream_turn`, not `agent.invoke(...)`. A tool
that reads a key as it stood at an earlier turn has to reach the host's
conversation store, and there is no synchronous way in. A graph invoked
synchronously does not fail when it is built: it fails when the model first
calls the tool, which is in front of a user.

The fourth piece is soft but do not skip it: append `SESSION_STATE_PROMPT` to
your system prompt. The machinery works without it, but the model then meets
breadcrumbs, `@state:<key>` handles and handle-only parameters with no
Expand Down