[GH-ISSUE #262] BUG : can't resume graph on generic/custom interrupts #233

Open
opened 2026-06-05 16:36:22 -04:00 by yindo · 0 comments
Owner

Originally created by @geoffreyp on GitHub (Apr 3, 2026).
Original GitHub issue: https://github.com/langchain-ai/agent-chat-ui/issues/262

When a LangGraph backend uses interrupt() with a custom/generic payload (i.e. not the standard HumanInterrupt schema with action_request / config), the chat input always sends the user's response as a new run.

This causes the graph to restart from START, re-triggering the interrupt() node in an infinite loop instead of resuming execution.

Only interrupts matching the isAgentInboxInterruptSchema format (with action_requests and review_configs) were properly handled via Command(resume=...) through the ThreadView / agent-inbox components. Any other interrupt format — like a simple {"type": "human_input_request", "message": "..."} — was displayed read-only via GenericInterruptView with no way to resume the graph from the chat input.

Originally created by @geoffreyp on GitHub (Apr 3, 2026). Original GitHub issue: https://github.com/langchain-ai/agent-chat-ui/issues/262 When a LangGraph backend uses interrupt() with a custom/generic payload (i.e. not the standard HumanInterrupt schema with action_request / config), the chat input always sends the user's response as a new run. This causes the graph to restart from START, re-triggering the interrupt() node in an infinite loop instead of resuming execution. Only interrupts matching the isAgentInboxInterruptSchema format (with action_requests and review_configs) were properly handled via Command(resume=...) through the ThreadView / agent-inbox components. Any other interrupt format — like a simple {"type": "human_input_request", "message": "..."} — was displayed read-only via GenericInterruptView with no way to resume the graph from the chat input.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/agent-chat-ui#233