Repository navigation
feat(uipath-agents): Maestro Flow as a low-code agent tool - #4751
ionut-mihalache-uipath wants to merge 1 commit into
Conversation
The agents skill documented four process-tool subtypes and had nothing on `type: "flow"`, so an agent asked to use a Maestro Flow as a tool had no contract to follow. - process.md: `flow` in the Subtypes table and every other subtype list, plus a "Maestro Flow as a Tool" section: what `uip solution resources list` returns for a deployed Flow and for a Flow project in the same solution, where the input/output contract comes from in each case, and what `uip solution resources refresh` writes. - A local Flow project exposes no schema through `resources get`; the contract is read from its variables: `in` variables bound to the start trigger are inputs, `out` variables are outputs, `inout` is neither. - Registry and routing rows, the subtype lists in the sibling references, and the `uipath.agent.resource.tool.flow.<release-key>` node type for inline agents. - New integration task `solution_flow_tool` with a fixture solution holding a Flow project. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136ibA39NTYe4XHq5Z2Ch32
|
Claude finished @ionut-mihalache-uipath's task in 45s —— View job Coder-eval task lint (advisory)1 task YAML changed. Verdicts: 0 Critical, 0 High, 0 Medium, 0 Low, 1 OK. There is also one PR-level High: no claim of a passing run. Rubric: .claude/commands/lint-task.md. This check is advisory and never blocks merge. Evidence of passing run
Per-task lint
|
|
Claude finished @ionut-mihalache-uipath's task in 1m 27s —— View job SummaryAdds Change-by-Change Review1.
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | OK | Unchanged |
| E2E Tests | Issue | New integration task looks sound, but there is no passing-run claim and no deployed-Flow task |
| Skill Body | OK | Routing rows are slightly redundant (Low) |
| References & Assets | OK | Flow type mapping is only partly specified (Low). All links and anchors resolve (agent-definition.md#file-attachments-job-attachment, #maestro-flow-as-a-tool) |
| Repo Hygiene | OK | No secrets or personal paths. Fixture GUIDs are synthetic. Scoped to uipath-agents |
Issues for Manual Review
- Whether the canvas node type
uipath.agent.resource.tool.flow.<release-key>matches what the Flow registry emits. The PR verified the agent-levelresource.json, but not an inline agent wired to a Flow tool. - Whether
uip maestro flow variables listreturnsDirection/TriggerNodeId/Typein PascalCase, as the doc assumes, for the fixture's camelCasevariables.globals. - Whether the "Deployed Flow" entry-point note (
process.md:319, which says top-levelInputArgumentsSchemaV2describesEntryPointName, not inline-agent entries) holds for Flows that have several triggers.
Conclusion
Approve once a coder-eval run passes. The documentation is accurate as far as this review can check, consistent across files, and flavor-safe. The type-mapping sentence and the stricter schema assertions are optional improvements.
What
Documents
type: "flow"— a Maestro Flow used as a tool of a low-code agent — in theuipath-agentsskill. The skill listed four process-tool subtypes and had nothing on Flows, so an agent asked to use one had no contract to follow.Changes
capabilities/process/process.md:flowin the Subtypes table and every other subtype list, plus a Maestro Flow as a Tool section covering whatuip solution resources listreturns for a deployed Flow and for a Flow project in the same solution, where the input/output contract comes from in each case, and whatuip solution resources refreshwrites.SKILL.md,lowcode.md), the subtype lists in the sibling references, and theuipath.agent.resource.tool.flow.<release-key>node type ininline-in-flow.md.tests/tasks/uipath-agents/lowcode/solution_flow_tool/, with a fixture solution that holds a Flow project.Decisions a reviewer cannot get from the diff
typeis lowercase"flow". A deployed Flow is listed withType: "Flow"; copying that verbatim failsuip agent validatewithInvalid input.resources get. Its contract is read from the Flow's variables:invariables bound to the start trigger are inputs,outvariables are outputs,inoutvariables are in neither. That mirrors how the Flow is packed, and the fixture carries aninoutvariable so the checker guards it.Verification
Ran:
resource.jsonthroughuip agent refreshanduip agent validate(uip 1.205.0); the binding isprocesswith subTypeflow.uip solution resources list/get/refreshfor a deployed Flow and for a local Flow project, to take the documented field names and output paths from real output.npm run skills:validate,skills:check-links,scripts/check-sensitive-content.py,scripts/check-skill-status.py: pass.npm run skills:test: 471 pass, 1 fail. The failure isthe built studioweb flavor mentions no new command the browser bundle cannot run(uipath-coded-apps), which fails the same way on an untouchedmain.Not run:
coder-evalon the new task, so there is no passing-run claim yet.skill-lint(not available locally).🤖 Generated with Claude Code
https://claude.ai/code/session_0136ibA39NTYe4XHq5Z2Ch32