[checkpoint] Continue langgraph_agent at typed node boundaries

Open
#3,255 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
ai, backend, distributed-systems

Research direction

Start in responses_api_agents/langgraph_agent/ and map the supported graph schemas, typed node states, and shared whitebox participant/versioned boundary records. Trace prepare, commit, process replacement, restore, and resume before implementing anything. Done means all listed acceptance criteria hold, including exact-once application, safe retries, fail-closed validation, and no replay of completed work.

Written by the indexing model from the issue text.

Description

area:agent feature

Parent

Child of #3220 and #3024. No additional resource child.

State owner

responses_api_agents/langgraph_agent/ owns compiled graph state, concrete graph schema, messages, cookies, and next node for orchestrator, parallel-thinking, reflection, and ReWOO graphs.

Adapter requirements

Use the shared whitebox participant and versioned boundary records. Persist output items, usage, cookies, last model-call identity, resource revisions, remaining budgets, and typed agent-specific state. Commit only after all effects of an operation are durable. On attempt N+1, skip reseeding and do not repeat completed model, tool, verifier, or judge work.

Acceptance criteria

  • Every supported graph serializes a typed node state and resumes at that node without replaying completed branches.
  • Prepare/commit/process replacement/restore/resume succeeds at every supported boundary.
  • Saved model responses, usage, cookies, and pending actions are applied exactly once.
  • Checkpoint refusal retries without advancing history or the operation cursor.
  • Resource revision mismatch, stale attempt, duplicate restore, and corrupt state fail closed.
  • Completed-unacknowledged results cannot also be published as resumable work.
Dominant language
Python
Stars
1.2k
Forks
349
Avg merge
1d 21h
Merged PRs (30d)
318

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA-NeMo/Gym

All issues in NVIDIA-NeMo/Gym

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.