Skip to content

feat: export resolved conversation_id to UIPATH_CONVERSATION_ID env var#114

Open
maxduu wants to merge 3 commits into
mainfrom
feat-set-conversation-id-in-env
Open

feat: export resolved conversation_id to UIPATH_CONVERSATION_ID env var#114
maxduu wants to merge 3 commits into
mainfrom
feat-set-conversation-id-in-env

Conversation

@maxduu
Copy link
Copy Markdown
Contributor

@maxduu maxduu commented May 27, 2026

Summary

At the end of UiPathRuntimeContext.with_defaults(), export the resolved conversation_id which comes from fpsProperties.conversationalService.conversationId`` to os.environ["UIPATH_CONVERSATION_ID"]` so downstream tool implementations can read it. This is the simplest method as it does not need the runtime context plumbed through every call site.

The conversation id is resolved from fpsProperties.conversationalService.conversationId in uipath.json (and any override applied via kwargs), then exported once. Only set when present — no-op when missing.

Motivation

A follow-up change in uipath-langchain-python auto-injects the conversation id into Orchestrator/Maestro tool calls whose input schemas declare a UIPATH_RESERVED_CONVERSATIONID argument. Those tools need a low-friction way to access the conversation id at execution time.

Test plan

  • tests/test_context.py::test_with_defaults_exports_conversation_id_to_env — verifies a config-supplied conversation id ends up in os.environ
  • Existing with_defaults() / from_config() tests still pass

@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants