fix(cli): add --type and --agent-framework options to uipath new

[vldcmp-uipath]

Problem

When uipath-langchain is installed, its entry-point middleware claims uipath new unconditionally (should_continue=False in all cases), so the base function scaffold is unreachable — uipath new <name> always produces a LangGraph agent project with no uipath.json. Fixes #1543.

Changes

• uipath new gains --type auto|function|agent (default: auto, shown in --help). auto preserves today's implicit behaviour: an installed agent framework claims the scaffold, otherwise the base function project is created; several installed integrations error and ask for an explicit choice instead of resolving by middleware registration order. function/agent request one explicitly — callers that need a guaranteed function project (e.g. the uip functions-tool passthrough) should pass --type function.
• uipath new gains --agent-framework claude-sdk|google-adk|langchain|llamaindex|microsoft-agent-framework|openai-agents|pydantic-ai, valid only together with --type agent. When omitted, it resolves to the framework whose integration package is installed (a single installed integration wins; several installed require an explicit --agent-framework; none installed errors with the list of frameworks and their integration packages — there is no hardcoded default framework).
• Both values are forwarded to the middleware chain as enums: Middlewares.next("new", name, project_type=..., agent_framework=...).
• If --type agent is requested but no installed integration claims the scaffold, the command errors and names the exact package to install (e.g. uipath-pydantic-ai) instead of silently falling back to a function project.
• AgentFramework.<member>.claims_scaffold(project_type, agent_framework) is the gate the integrations' new middlewares share: auto is claimed by whichever integration is installed, agent only by the framework it names, function by none. The rule is identical for every framework, so it lives here instead of being repeated (and drifting) in each integration repo.
• New ProjectType and AgentFramework StrEnums live in uipath._cli.models.project_types / uipath._cli.models.agent_frameworks so framework integrations can import them; AgentFramework.<member>.package returns the integration's PyPI package name (note: microsoft-agent-framework ships as uipath-agent-framework).
• Version bumped to 2.14.15.

Behaviour

Command	Result
uipath new my-fn (or --type auto)	agent project when one framework integration is installed, function project when none (default); pick-one error when several
uipath new my-fn --type function	function project (explicit)
uipath new my-agent --type agent	agent for the single installed framework's integration; pick-one error when several; install-a-framework error when none
uipath new my-agent --type agent --agent-framework pydantic-ai	pydantic-ai integration if installed, otherwise actionable error
uipath new x --agent-framework langchain	error: only valid with --type agent

Compatibility

• Old integrations that don't accept the new kwargs hit the existing legacy-signature fallback in Middlewares.next (kwargs trimmed + "Install the latest version for uipath packages" warning), so behaviour with an outdated uipath-langchain is unchanged until it updates — companion PR in uipath-langchain-python gates its middleware on these values.
• The enums subclass str, so middlewares comparing plain strings keep working.

Testing

• 27/27 in tests/cli/test_new.py (19 new cases), mypy and ruff clean.
• Verified end-to-end in a venv with both packages installed editable: default/function/agent/uninstalled-framework/misuse/invalid-value paths.

🤖 Generated with Claude Code

Development Packages

uipath

[project]
dependencies = [
  # Exact version (copy-paste ready):
  "uipath==2.14.15.dev1018867616",

  # Any version from this PR (uncomment to use a range instead):
  # "uipath>=2.14.15.dev1018860000,<2.14.15.dev1018870000",
]

[[tool.uv.index]]
name = "testpypi"
url = "https://test.pypi.org/simple/"
publish-url = "https://test.pypi.org/legacy/"
explicit = true

[tool.uv.sources]
uipath = { index = "testpypi" }

[Copilot]

🟢 Approval recommended

The behavior change is well-covered by tests and the remaining feedback is limited to minor CLI help/UX clarity rather than functional correctness.

Pull request overview

This PR updates the uipath CLI’s new command to make function vs agent scaffolding explicit, preventing third-party integrations (e.g., uipath-langchain) from unconditionally claiming uipath new and making the base function scaffold unreachable.

Changes:

• Added --type function|agent (default function) and --agent-framework ... (valid only with --type agent) to uipath new, forwarding both as enums through the middleware chain.
• Introduced shared StrEnum models (ProjectType, AgentFramework) for integrations to import, including framework→package name mapping.
• Expanded CLI test coverage for the new option matrix and bumped version to 2.14.13.

File summaries

File	Description
packages/uipath/src/uipath/_cli/cli_new.py	Adds --type / --agent-framework, resolves defaults, validates combinations, forwards enums to middleware, and errors when an agent scaffold isn’t claimed.
packages/uipath/src/uipath/_cli/models/project_types.py	New ProjectType StrEnum for integrations and middleware dispatch.
packages/uipath/src/uipath/_cli/models/agent_frameworks.py	New AgentFramework StrEnum with .package mapping and default framework constant.
packages/uipath/tests/cli/test_new.py	Adds tests verifying defaulting, forwarding, validation, and “missing integration” error behavior.
packages/uipath/pyproject.toml	Bumps uipath version to 2.14.13.
packages/uipath/uv.lock	Updates lock metadata and bumps locked uipath version to 2.14.13.

Review details

• Files reviewed: 5/6 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[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 →

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud