This solution has been AI generated
You're hitting a known issue: loadAgentState currently returns all non-message state, including internal keys. This is due to missing filtering in the runtime implementation; the open PR proposes limiting the response to user-facing state.
What’s happening
In the runtime’s loadAgentState (LangGraph path), the code does not filter internal fields:
const { messages, ...stateWithoutMessages } = state;
return {
threadId: threadId || "",
threadExists: true,
state: JSON.stringify(stateWithoutMessages),
messages: JSON.stringify(copilotkitMessages),
};
Fix (as proposed in PR #2125)
Return only the user-facing portion of state:
const { messages, ...fullStateWithoutMessages } = state;
const userFacingState = fullStateWithoutMessages.userFacing || {};
return {
threadId: threadId || "",
threadExists: true,
state: JSON.stringify(userFacingState),
messages: JSON.stringify(copilotkitMessages),
};
Workarounds for 1.10.3
- Client-side filtering (quickest):
const res = await loadAgentState(...);
const full = JSON.parse(res.state || "{}");
const safe = full.userFacing ?? {};
- Server-side patch (preferred if possible): fork/patch the runtime to apply the filtering above before returning
state.
Notes
- This primarily affects the LangGraph agent runtime path; the Python backend isn’t the source of the exposure.
- Once the PR is merged and a new runtime is published, updating should resolve the issue.
Was this helpful?
If this solution worked for you, please click on the appropriate option below to help us improve:
prime island
cloud coyote