Skip to content

feat: workspace persistence across conversational exchanges via content-parts#145

Open
radu-mocanu wants to merge 1 commit into
mainfrom
feat/conversational-advanced-workspace
Open

feat: workspace persistence across conversational exchanges via content-parts#145
radu-mocanu wants to merge 1 commit into
mainfrom
feat/conversational-advanced-workspace

Conversation

@radu-mocanu

Copy link
Copy Markdown
Collaborator

Summary

  • add ConversationalWorkspaceRuntime: hydrates the workspace from the file content-parts of the last assistant message in the conversation history, and on a successful exchange emits one content-part per workspace file (attachment uri + metaData {fileKind: workspace, sha256}) before the final assistant endMessage
  • unchanged files (sha256 match) are relinked to the current job instead of re-uploaded
  • add cas_uri helpers for urn:uipath:cas:file:orchestrator:{id} and WorkspaceHydrator.hydrate_files for registry-less hydration from history

Why

conversational agents run one job per exchange, so the deepagents workspace (plan/todo/memory files) is lost between turns. per the contract agreed with the CAS team, the workspace now travels through job attachments referenced by file content-parts on the last assistant message.

Copilot AI review requested due to automatic review settings July 6, 2026 14:49
@radu-mocanu radu-mocanu requested a review from a team as a code owner July 6, 2026 14:49
@sonarqubecloud

sonarqubecloud Bot commented Jul 6, 2026

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
86.7% Coverage on New Code (required ≥ 90%)

See analysis details on SonarQube Cloud

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new runtime wrapper to persist a workspace across conversational exchanges by hydrating from the last assistant message’s file content-parts and (on success) emitting workspace files back as content-part attachments.

Changes:

  • Introduces ConversationalWorkspaceRuntime to hydrate from conversation history and dehydrate workspace files as file content-parts before the final assistant endMessage.
  • Adds CAS URI helpers (build_cas_uri, parse_attachment_id) and WorkspaceHydrator.hydrate_files to support registry-less hydration from history.
  • Adds comprehensive tests for hydration/dehydration behavior and bumps package version to 0.12.2.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
uv.lock Bumps locked package version to 0.12.2.
pyproject.toml Bumps project version to 0.12.2.
src/uipath/runtime/workspace/hydrator.py Adds hydrate_files() to download attachments and build a registry without a preexisting registry.
src/uipath/runtime/workspace/conversational.py Adds ConversationalWorkspaceRuntime that hydrates from history and emits workspace content-parts on success.
src/uipath/runtime/workspace/cas_uri.py Adds helpers to build/parse CAS attachment URIs used by conversational workspace persistence.
src/uipath/runtime/workspace/init.py Exposes the new conversational runtime and CAS URI helpers from the workspace package.
src/uipath/runtime/init.py Re-exports ConversationalWorkspaceRuntime from the top-level runtime package.
tests/workspace/test_conversational_workspace.py Adds tests covering ordering, hydration rules, relinking vs reupload, and disposal behavior.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +95 to +98
async for event in self.stream(
input,
options=UiPathStreamOptions(resume=options.resume if options else False),
):
Comment on lines +25 to +33
# The UUID is the last segment after the final colon
parts = uri.rsplit(":", 1)
if len(parts) != 2 or not parts[1]:
return None

try:
return str(uuid.UUID(parts[1]))
except (ValueError, AttributeError):
return None
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