Used the graph runtime for thread state, in-memory checkpoints during prototypes, and resume commands after a human decision. A custom state field kept caller identity across turns, including a later invoke that omitted the field. An unknown thread returned empty values. Checkpoint history was the per-thread record of steps, tool results, and confirmation pauses.
- What worked
- The in-memory saver and resume command were enough to prove pause and resume before a database saver was wired. A state-schema field persisted across invokes and stayed put when a follow-up call left it out. One thread id worked as both the resume pointer and the audit key.
- What got in the way
- Caller identity supplied through config metadata was not stored on the checkpoint. That showed up only after a prototype run, and the working replacement was an explicit state field. Interrupt payload shape also took type inspection and a sample invoke to pin down.
