Repository navigation
Conversation
Add AgentA2aConversationalResourceConfig and route a2a resources with agentType == "conversational" to it through a nested discriminator. Remote A2A records keep using AgentA2aResourceConfig. An a2a record with an unrecognised agentType falls back to the Unknown resource. Co-Authored-By: Claude Opus 5.5 <[email protected]>
github-actions
Bot
added
test:uipath-langchain
…ODEV-1742] Co-Authored-By: Claude Opus 5.5 <[email protected]>
ionmincu
changed the title
…f an a2a variant An a2a resource without a slug makes older runtimes reject the whole agent, while an unknown tool type is skipped on its own and also gets the solution process binding. Drop AgentA2aConversationalResourceConfig and add AgentToolType.CONVERSATIONAL_AGENT with AgentConversationalAgentToolResourceConfig. Co-Authored-By: Claude Opus 5.5 <[email protected]>
ionmincu
changed the title
…ecord does not reject the agent Also add the cross-repo contract fixture test. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
🚨 Heads up:
|
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR stack (PRODEV-1742), merge in this order
conversationalAgenttool type, plus itsprocessbinding in the packager. Wait for the@uipath/agents-storage-schemas1.44.0 and@uipath/tool-agent2.2.0 (packager) releases.AgentToolType.CONVERSATIONAL_AGENTandAgentConversationalAgentToolResourceConfig. Wait for the uipath 2.14.37 PyPI release. ← this PRa2a/{folderKey}/{releaseId}over A2A. Runuv lockfirst, then wait for the uipath-langchain 0.18.27 release.conversationalAgenttools (never a job tool), bump dependencies. Runuv lockfirst, then deploy the runtime.conversationalAgenttool resource. Can merge any time after [1/5] is released, with the flag off. First bump@uipath/agents-storage-schemasto^1.44.0and@uipath/tool-agentto^2.2.0(older packagers emit noprocessbinding for this tool), and set the flag default back tofalse.Turn on the Flow flag
canvas.nodes.agent-tool-conversational-a2aonly after [4/5] is deployed.Adds a
conversationalAgenttool type so an agent can call an existing UiPath conversational agent.Why a tool type, not an
a2avariantAn
a2aresource without aslugmakes older runtimes reject the whole agent (AgentA2aResourceConfigrequiresslug, and_normalize_resourceskeepsa2a). An unknown tooltypegoes throughTOOL_MAP.get(t.lower(), "Unknown"), so older runtimes skip just that tool. A tool type also gets the solutionprocess.<processName>binding from the packager, so@resource_override(process, process_name)takes effect. Precedent:AgentToolType.FLOW/FUNCTION.Design
AgentToolType.CONVERSATIONAL_AGENT = "ConversationalAgent"and theTOOL_MAPentry"conversationalagent", so any casing normalizes.AgentConversationalAgentToolResourceConfig(BaseAgentToolResourceConfig)withtype: Literal[CONVERSATIONAL_AGENT],properties: AgentConversationalAgentToolProperties(processNameoptional so a record without it still loads and the runtime reports it at call time,folderPathandcachedAgentCardoptional, plus the baseexampleCalls/requireConversationalConfirmation),outputSchema,settingsandargumentProperties.locationandguardrailare extras, as for other tools. It is a separate class, not another literal onAgentProcessToolResourceConfig.type, so langchain'stool_factorycannot route it to the job-start path.ToolResourceConfigunion nested ontype. Thea2acode is back tomain.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; missingprocessNamestill loads the agent; the cross-repo contract fixture parses with every field preserved; an unknown tool type still goes to Unknown.Version bumped to 2.14.37 in
packages/uipath(pyproject and uv.lock).🤖 Generated with Claude Code