feat(agent): [2/5] conversational agent tool config [PRODEV-1742]

[ionmincu]

PR stack (PRODEV-1742), merge in this order

1. [1/5] UiPath/Agents#6529: storage schema: conversationalAgent tool type, plus its process binding in the packager. Wait for the @uipath/agents-storage-schemas 1.44.0 and @uipath/tool-agent 2.2.0 (packager) releases.
2. [2/5] feat(agent): [2/5] conversational agent tool config [PRODEV-1742] #1931: runtime model: AgentToolType.CONVERSATIONAL_AGENT and AgentConversationalAgentToolResourceConfig. Wait for the uipath 2.14.37 PyPI release. ← this PR
3. [3/5] feat(a2a): [3/5] call UiPath conversational agents as A2A tools [PRODEV-1742] uipath-langchain-python#1139: runtime tool: resolve the release and call AgentHub a2a/{folderKey}/{releaseId} over A2A. Run uv lock first, then wait for the uipath-langchain 0.18.34 release.
4. [4/5] UiPath/uipath-agents-python#800: runtime graph: build the A2A tool for conversationalAgent tools (never a job tool), bump dependencies. Run uv lock first, then deploy the runtime.
5. [5/5] UiPath/flow-workbench#4734: Flow: pick conversational agents as tools, write the conversationalAgent tool resource. Can merge any time after [1/5] is released, with the flag off. First bump @uipath/agents-storage-schemas to ^1.44.0 and @uipath/tool-agent to ^2.2.0 (older packagers emit no process binding for this tool), and set the flag default back to false.

Turn on the Flow flag canvas.nodes.agent-tool-conversational-a2a only after [4/5] is deployed.

Adds a conversationalAgent tool type so an agent can call an existing UiPath conversational agent.

• Storage schema: UiPath/Agents#6529
• Flow side: UiPath/flow-workbench#4734
• The tool is built in feat(a2a): [3/5] call UiPath conversational agents as A2A tools [PRODEV-1742] uipath-langchain-python#1139.

Why a tool type, not an a2a variant

An a2a resource without a slug makes older runtimes reject the whole agent (AgentA2aResourceConfig requires slug, and _normalize_resources keeps a2a). An unknown tool type goes through TOOL_MAP.get(t.lower(), "Unknown"), so older runtimes skip just that tool. A tool type also gets the solution process.<processName> binding from the packager, so @resource_override(process, process_name) takes effect. Precedent: AgentToolType.FLOW / FUNCTION.

Design

• AgentToolType.CONVERSATIONAL_AGENT = "ConversationalAgent" and the TOOL_MAP entry "conversationalagent", so any casing normalizes.
• New class AgentConversationalAgentToolResourceConfig(BaseAgentToolResourceConfig) with type: Literal[CONVERSATIONAL_AGENT], properties: AgentConversationalAgentToolProperties (processName optional so a record without it still loads and the runtime reports it at call time, folderPath and cachedAgentCard optional, plus the base exampleCalls / requireConversationalConfirmation), outputSchema, settings and argumentProperties (defaults to {}). location and guardrail are extras, as for other tools. The storage schema (UiPath/Agents#6529) defines this tool as a standalone object with no argumentProperties, entryPointPath or job-retry settings, so the contract fixture omits them; the model needs no change for that (extra="allow" tolerates a leftover key and argumentProperties defaults to {}). It is a separate class, not another literal on AgentProcessToolResourceConfig.type, so langchain's tool_factory cannot route it to the job-start path.
• It is added to the ToolResourceConfig union nested on type. The a2a code is back to main.

Tests

Mixed agent.json (agent tool, remote a2a, conversational agent tool) parses into the right classes; by-alias round trip keeps type; case variants normalize; optional properties may be missing or null; missing processName still loads the agent; the cross-repo contract fixture (exactly the storage schema's shape, so no argumentProperties) parses with every field preserved; an unknown tool type still goes to Unknown.

Packager parity

No cli_pack.py change is needed. generate_bindings_content() returns an empty Bindings, and cli_pack only copies a pre-written bindings.json; nothing in uipath-python derives bindings from agent.json tool resources, so there is no agent / flow / function binding handling to mirror. The process.<processName> binding comes from the TypeScript packager (and, for the C# /bindings path, the C# generator) in UiPath/Agents#6529, which carries the parity explanation.

Version bumped to 2.14.37 in packages/uipath (pyproject and uv.lock).

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[uipathepixa-dogfood]

Epixa-Dogfood Review

Review unavailable: required_pr_review_evidence_unavailable

Not reviewed: packages/uipath/pyproject.toml, packages/uipath/src/uipath/agent/models/agent.py, packages/uipath/tests/agent/models/test_agent.py +1 more

Not read: 4 files that could not be fetched.

What this PR does

The pull request author describes the intended change as follows: feat(agent): [2/5] conversational agent tool config [PRODEV-1742]

This review did not reuse a local review of this change. Set up Epixa local review.

Full review: 69fd8e5 0 findings

[github-actions]

🚨 Heads up: uipath-integrations cross-tests are FAILING 🚨

Your changes may break one or more integrations in uipath-integrations-python:

• uipath-openai-agents
• uipath-google-adk
• uipath-agent-framework
• uipath-llamaindex
• uipath-pydantic-ai

⚠️ These checks are NOT enforced by branch protection rules. Please review the failures before merging.

🔍 Inspect the failed run →

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🚨 Heads up: uipath-langchain cross-tests are FAILING 🚨

Your changes may break the uipath-langchain-python integration.

⚠️ These checks are NOT enforced by branch protection rules. Please review the failures before merging.

🔍 Inspect the failed run →