Repository navigation
feat(uipath-agents): HTTP Request built-in tool for inline agents in a Flow - #4752
ionut-mihalache-uipath wants to merge 1 commit into
Conversation
…a Flow The agents skill had no walkthrough for the built-in HTTP Request tool (`type: "internal"`, `toolType: "http-request"`). - http-request.md: the tool is for inline agents in a Flow only. Agent Builder has no UI for it, so the skill never authors it on a standalone agent, even though `uip agent validate` accepts the resource there; it tells the user and offers the inline-in-flow route instead. - Builder-SDK Flow projects declare the tool through the uipath-maestro-flow skill (`compile` owns the resource); the resource shape and walkthrough here cover a JSON-authored `.flow`. - built-in-tools.md: an Argument Sources section for `argumentProperties`, the flow node type per tool in the Tool Registry (the node suffix is not the `toolType`), and the Flow SDK case in Critical Rule 5, which now cites the right rule. - The planning docs said only four `toolType` values pass validation and recommended `load-attachments`, which has no runtime implementation. - New integration task `http_request_tool`: fails when a standalone agent carries the tool. 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 1m 27s —— View job SummaryAdds an HTTP Request built-in tool walkthrough ( Change-by-Change Review1.
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | OK | Unchanged |
| E2E Tests | Issue | Negative guard only; no passing-run claim; no positive-path task |
| Skill Body | OK | One routing row added |
| References & Assets | OK | Low: stale load-attachments lines; node-suffix list in three places |
| Repo Hygiene | OK | No secrets or personal paths; api.example.com placeholder host; scoped to uipath-agents + tests |
Issues for Manual Review
- Runtime facts. Defaults (
GET, 30 s timeout,https://auto-prefix), the 5-redirect cap, the per-hop public-host check, and the failure where an entry missingisSensitivepasses validation but stops the agent loading were read from runtime source, per the PR body. A domain owner should confirm them; no live call was made. - Flow node availability.
uipath.agent.resource.tool.builtin.httprequestis described as available "on tenants that offer it". Confirm how widely it's rolled out, so agents don't hit the stop path often. - The other flow node names. Confirm
analyzefiles,createfile,summarizeandbatchtransformagainstuip maestro flow registry. They are newly documented here and not otherwise verified in the PR. - Sibling skill alignment. The Builder-SDK hand-off depends on
uipath-maestro-flow(agent-resources.mdhttpRequestkind) agreeing with this doc that compile writes the resource and deletes a hand-written one. - Link checker. I couldn't run
npm run skills:check-linksin this sandbox. I checked every new relative link and anchor by hand, and all resolve.
Conclusion
Approve, with minor follow-ups. The content is accurate to the stated sources and fits the skill's conventions. Before merge: add the coder-eval passing-run claim and consider a positive-path task. The rest is Low polish (the stale load-attachments lines and the duplicated node-suffix lists).
|
Claude finished @ionut-mihalache-uipath's task in 1m 10s —— View job Coder-eval task lint (advisory)1 task YAML changed; verdict counts: 0 Critical, 0 High, 1 Medium, 0 Low, 0 OK (plus one High finding under Evidence of passing run). Rubric: .claude/commands/lint-task.md. This check is advisory and never blocks merge. Evidence of passing run
Per-task lint
|
What
Adds the built-in HTTP Request tool (
type: "internal",properties.toolType: "http-request") to theuipath-agentsskill. The skill had no walkthrough for it.Changes
capabilities/built-in-tools/http-request.md: when to use it, the resource shape, the six arguments and how the runtime treats them, pinning arguments, output, limits and errors.built-in-tools.md: an Argument Sources section forargumentProperties(the skill had none), the flow node type per tool in the Tool Registry, and the Flow SDK case in Critical Rule 5.SKILL.md,lowcode.md,agent-definition.md,inline-in-flow.md,guardrails.md).tests/tasks/uipath-agents/lowcode/http_request_tool/.Decisions a reviewer cannot get from the diff
uip agent validateaccepts the resource on a standalone agent, so the skill states the rule itself: never author it there, tell the user, and offer the inline-in-flow route.compilewrites it and deletes a hand-written one, so the skill hands the tool to theuipath-maestro-flowskill. The resource shape and walkthrough here are for a JSON-authored.flow.toolType(http-requestishttprequest,deep-ragissummarize). Critical Rule 5 saidbuiltin.<toolType>; the Tool Registry now lists the exact node per tool. The same rule cited Critical Rule 16 for the hand-off to the flow skill; the rule it meant is 15.load-attachments: the planning docs said only fourtoolTypevalues pass validation and recommendedload-attachments. It passes validation but has no runtime implementation, so the docs now say not to use it.Verification
Ran:
resource.json, with the documented pinned arguments, throughuip agent refreshanduip agent validate --inline-in-flowon an inline agent inside a real Flow project (uip 1.205.0).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