…Mo#306) ActionResult(context_updates=...) is the supported way to write a slot back into the conversation context, but no page named it. NVIDIA-NeMo#306 asks how an action sets a dialogue-state variable that a later flow can read. Adds an "ActionResult and Context Updates" section to Creating Actions with a Colang 2.0 and a Colang 1.0 tab, a cross-turn section to Extract User-provided Values, and pointers from Action Parameters and the Colang 2.0 Python actions reference. The Colang 2.0 text records that a ContextUpdate event placed in ActionResult.events is attached to the ActionFinished event and never applied, so context_updates is the only path that works there. The Colang 1.0 tab warns about returning a module-level mutable object, which silently drops every slot after the first. Covered by two tests that pin the published snippets: the Colang 2.0 test asserts the slot survives a second turn, the Colang 1.0 test asserts the value renders in a bot message. Dropping context_updates= from the 2.0 action fails with 'Hello None'. Closes NVIDIA-NeMo#306 Claude-Session: https://claude.ai/code/session_019EfkfVe6VsQH5HfL5SU7He Signed-off-by: ChethanUK <chethanuk@outlook.com>

Uh oh!

How to manage dialogue state at custom action file ? #306

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions