You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Use proper fixture naming and declaration convention
- Avoid possessive 's with inanimate objects
- Hardcoded name breaks consistency with emit_thought_start and emit_thought_chunk
- Assert the END events in the concurrent lifecycle test.
- Drop the unused make_intermediate_step fixture fom tests
- Instantiate the profiler callback per request, or protect state mutations with locks and add cleanup
Signed-off-by: Patrick Chin <8509935+thepatrickchin@users.noreply.github.com>
Copy file name to clipboardExpand all lines: docs/source/build-workflows/workflow-configuration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ The `functions` section contains the tools used in the workflow, in our example
75
75
76
76
Agent responses in the NeMo Agent Toolkit UI include a thought process display which shows a step-by-step view of what the workflow is doing.
77
77
78
-
To customize the text shown for a function in the thought process display, set `thought_description` in that function's configuration. Unlike `description`, which provides the tool's help text that the agent uses to decide when and how to call the tool, `thought_description` only affects the label shown in the thought process display. For example:
78
+
To customize the text shown for a function in the thought process display, set the `thought_description` attribute. Unlike `description`, which provides help text that the agent uses to decide when and how to call the tool, `thought_description` only affects the message shown in the thought process display UI as well as in observability traces. For example:
0 commit comments