langchain-ai/langgraph
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraph.git synced 2026-07-15 12:35:43 -04:00
Code Issues 314 Packages Projects Releases 17 Wiki Activity

[PR #5405] change[langgraph]: clean up Interrupt interface for v1 #4415

New Issue
Closed
opened 2026-02-20 17:50:09 -05:00 by yindo · 0 comments
yindo commented 2026-02-20 17:50:09 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langchain-ai/langgraph/pull/5405

State: closed
Merged: Yes

Fixes https://github.com/langchain-ai/langgraph/issues/5016

This PR introduces a few changes to the Interrupt interface to prepare for the v1 release. Users only need to be exposed to an interrupt's:

  • value
  • id

Eventually, we'll add response_schema as well (think, MCP elicitation). See https://github.com/langchain-ai/langgraph/issues/5027.

Renaming / public deprecation:

  • interrupt_id -> id
  • NodeInterrupt - users can just use interrupt which is more modern and flexible

Private deprecations:

  • when - always 'during', so this doesn't have much value
  • resumable - always True, so doesn't have much value
  • ns - largely internal information, id can be used for mapping interrupt -> resume value

New convenience methods

  • Interrupt.from_ns coerces a checkpoint ns string -> an interrupt id

Notes

  • Considered removing the tuple wrapper around all interrupts, but this is a breaking change of low value, so not planning on implementation for now.
  • Tests are added to confirm that old style interrupts can be rehydrated into new ones :)
**Original Pull Request:** https://github.com/langchain-ai/langgraph/pull/5405 **State:** closed **Merged:** Yes --- Fixes https://github.com/langchain-ai/langgraph/issues/5016 This PR introduces a few changes to the `Interrupt` interface to prepare for the v1 release. Users only need to be exposed to an interrupt's: * value * id Eventually, we'll add `response_schema` as well (think, [MCP elicitation](https://modelcontextprotocol.io/specification/draft/client/elicitation)). See https://github.com/langchain-ai/langgraph/issues/5027. ## Renaming / public deprecation: * `interrupt_id` -> `id` * `NodeInterrupt` - users can just use `interrupt` which is more modern and flexible ## Private deprecations: * `when` - always `'during'`, so this doesn't have much value * `resumable` - always `True`, so doesn't have much value * `ns` - largely internal information, `id` can be used for mapping interrupt -> resume value ## New convenience methods * `Interrupt.from_ns` coerces a checkpoint ns string -> an interrupt id ## Notes * Considered removing the tuple wrapper around all interrupts, but this is a breaking change of low value, so not planning on implementation for now. * Tests are added to confirm that old style interrupts can be rehydrated into new ones :)
yindo added the pull-request label 2026-02-20 17:50:09 -05:00
yindo closed this issue 2026-02-20 17:50:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
awaiting author revision
bug
change
chat models
checkpointer
ci
code quality
code quality
dependencies
documentation
drawing
duplicate
enhancement
good first issue
help wanted
invalid
maintainer
meta
missing information
not maintained by langchain
open-swe-auto
open-swe-max
open-swe-max-auto
pending
performance
pull-request
Mirrored from GitHub Pull Request
 question
requires design
sdk
server
stale
studio
tests
type checking
usage question
v0.5
v1.1
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraph#4415
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?