@uipath/skills 1.204.0-preview.1149 → 1.204.0-preview.1160

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/skills",
-  "version": "1.204.0-preview.1149",
+  "version": "1.204.0-preview.1160",
   "description": "UiPath agent skills for Claude Code, Codex, Cursor, Copilot, Gemini and OpenCode — RPA, UI automation, UI testing, coded agents/apps/workflows, and troubleshooting. Distributed as the UiPath Claude Code plugin.",
   "author": {
     "name": "UiPath"

package/skills/uipath-agents/references/authentication.md

@@ -21,11 +21,8 @@ uip login status --output json
 # Production cloud (one-shot browser sign-in, org/tenant pre-selected — see Critical Rules for who runs it)
 uip login --organization "<ORG>" --tenant "<TENANT>" --output json
 
-# Staging
-uip login --authority "https://staging.uipath.com/identity_" --organization "<ORG>" --tenant "<TENANT>" --output json
-
-# Alpha
-uip login --authority "https://alpha.uipath.com/identity_" --organization "<ORG>" --tenant "<TENANT>" --output json
+# Non-default host (Automation Suite, dedicated, or other custom authority)
+uip login --authority "<AUTHORITY_URL>" --organization "<ORG>" --tenant "<TENANT>" --output json
 
 # Service principal (unattended)
 uip login --client-id "<ID>" --client-secret "<SECRET>" --base-url "<URL>" --output json
@@ -34,12 +31,12 @@ uip login --client-id "<ID>" --client-secret "<SECRET>" --base-url "<URL>" --out
 ## Critical Rules
 
 - **`uip login status --output json` once per invocation.** Reports `Status`, `Organization`, `Tenant`, `Expiration Date`. When the user has not asked to connect to a specific org/tenant, trust one `Logged in` result — the wrapper auto-refreshes tokens on forwarded cloud calls. No `uip login refresh` subcommand exists. Re-auth only on a real `401`.
-- **If the user supplied environment + organization + tenant, connect with those exact values.** First run/capture `uip login status --output json` if requested or required, then use the matching one-shot command from the Quick Reference (`uip login --organization "<ORG>" --tenant "<TENANT>" --output json`, plus `--authority` for staging/alpha) — see the next rule for who runs it. Do this even if the status check reports an existing `Logged in` session, because the active session may point at a different org/tenant. Do not ask another auth question when all three values are already present.
+- **If the user supplied environment + organization + tenant, connect with those exact values.** First run/capture `uip login status --output json` if requested or required, then use the matching one-shot command from the Quick Reference (`uip login --organization "<ORG>" --tenant "<TENANT>" --output json`, plus `--authority` for any non-default host) — see the next rule for who runs it. Do this even if the status check reports an existing `Logged in` session, because the active session may point at a different org/tenant. Do not ask another auth question when all three values are already present.
 - **Interactive sign-ins belong in the user's own terminal.** Every `uip login` without `--client-secret` is a browser sign-in: it blocks until the person completes it, and run from your shell tool it shows them nothing while your tool's timeout can kill it mid-wait. Prefer asking the user to run the one-shot command themselves (in Claude Code, prefix it with `!` so it runs inside the session); if you do run it, first tell the user a browser window is about to open and the command will wait for them. **Never pass `--no-browser` for a human sign-in** — that flag is for automation that opens the printed URL programmatically; relaying the URL by copy/paste is fragile (a line-wrapped or truncated copy is rejected by the identity server with an opaque browser-side error).
 - **NEVER run `uip login` without `--tenant`.** The interactive tenant picker cannot be driven from Claude's Bash tool.
 - **When auth is needed and the user did not supply all values, ask one question, then stop.** If the status check shows the user is not logged in and any of environment / organization / tenant is missing, your entire response must be exactly this question — no headers, no bullets, no next-steps:
 
-  > What is your UiPath **environment** (cloud / staging / alpha), **organization name**, and **tenant name**?
+  > What is your UiPath **environment** (cloud, or your custom host URL), **organization name**, and **tenant name**?
 
   Wait for the reply, then follow the interactive-sign-ins rule above: give the user the exact one-shot command from the Quick Reference to run in their own terminal (or, if you run it, first tell them a browser window is about to open), and confirm with `uip login status --output json`.
 
@@ -48,10 +45,7 @@ uip login --client-id "<ID>" --client-secret "<SECRET>" --base-url "<URL>" --out
 | User says | Flag to use |
 |-----------|-------------|
 | cloud (default) | no `--authority` flag |
-| staging | `--authority "https://staging.uipath.com/identity_"` |
-| alpha | `--authority "https://alpha.uipath.com/identity_"` |
-
-For on-premise Automation Suite, use `--authority <identity-url>` pointing at your instance.
+| A custom host URL (Automation Suite, dedicated, other) | `--authority "<AUTHORITY_URL>"` — the URL the user gave, pointing at their instance |
 
 ## Unattended (Service Principal)
 

package/skills/uipath-agents/references/coded/quickstart.md

@@ -45,10 +45,10 @@ Use `uip codedagent <cmd>`, not `uv run uipath <cmd>`. The wrapper injects sessi
 - **Runtime captures only the last node's delta as output.** `Annotated[list, operator.add]` reducers accumulate inside the graph but vanish from `--output-file` JSON and eval trajectories. Carry aggregate fields forward in each node's return (`{"items": [*state.get("items", []), x]}`) — see [frameworks/langgraph-integration.md](frameworks/langgraph-integration.md) § Runtime Output Quirk.
 - **Verify the JSON, not the streamed display.** After `uip codedagent run --output-file out.json`, inspect `out.json` — the streamed view shows per-node deltas; the JSON is the runtime's actual final result. Mismatches expose the runtime quirk above.
 - **Use `uip codedagent deploy` for packaging/publishing.** `uip codedagent pack` and `uip codedagent publish` are filtered by the wrapper.
-- **NEVER run `uip login` without `--tenant`.** The interactive tenant picker does not work from Claude's Bash tool. Use the one-shot form `uip login --organization "<ORG>" --tenant "<TENANT>"`, mapping staging/alpha to `--authority` (see [../authentication.md](../authentication.md)).
+- **NEVER run `uip login` without `--tenant`.** The interactive tenant picker does not work from Claude's Bash tool. Use the one-shot form `uip login --organization "<ORG>" --tenant "<TENANT>"`, adding `--authority` for a non-default host (see [../authentication.md](../authentication.md)).
 - **Auth MUST be an interactive question only when needed and values are missing.** If the session check fails and the user did not provide all of environment / organization / tenant, your ENTIRE response must be a single direct question. Do NOT wrap it in bullet points, "Next Steps" headers, or status summaries. Just ask and stop:
 
-  > What is your UiPath **environment** (cloud/staging/alpha), **organization name**, and **tenant name**?
+  > What is your UiPath **environment** (cloud, or your custom host URL), **organization name**, and **tenant name**?
 - **In a flow, coded agents are referenced via the `agent` plugin (uipath-maestro-flow skill)** — node type `uipath.core.agent.{key}`, `Orchestrator.StartAgentJob`. See [flow-integration.md](flow-integration.md) for the three patterns: in-solution sibling folder, Orchestrator-published, tool resource.
 
 ## Lifecycle Stages
@@ -110,7 +110,7 @@ Steps 8 and 9 are mandatory stops **for greenfield**: always ask the user, even
 4. **Bindings** — Sync `bindings.json` with the code using [lifecycle/bindings-reference.md](lifecycle/bindings-reference.md).
 5. **Auth (one-shot)** — Run `uip login status --output json` once. If the user supplied environment + organization + tenant, have them run the matching one-shot login command from [../authentication.md](../authentication.md) in their own terminal, using both `--organization` and `--tenant` in the same `uip login` command (a browser sign-in — if you run it yourself, first tell the user a browser window is about to open). Do this even when `Status: Logged in`, because the existing session may be for a different tenant. If no credentials were supplied and `Status: Logged in`, trust the wrapper for the rest of the run (it auto-refreshes tokens). Otherwise ask for credentials — output ONLY this question as your entire response:
 
-> What is your UiPath **environment** (cloud/staging/alpha), **organization name**, and **tenant name**?
+> What is your UiPath **environment** (cloud, or your custom host URL), **organization name**, and **tenant name**?
 
 Then STOP and wait. On reply, hand the user the matching one-shot login from [../authentication.md](../authentication.md) to run in their own terminal (maps environment → `--authority`), then confirm with `uip login status --output json`. Never run `uip login` without `--tenant`.
 6. **Run** — Re-run `uip codedagent init` first whenever any of these changed since the last init, **or** when `has_entry_points == false`:

package/skills/uipath-api-workflow/assets/templates/connector-call-example.json

@@ -77,7 +77,7 @@
                 "bodyParameters": {
                   "authentication": "manual",
                   "method": "GET",
-                  "url": "https://catfact.ninja/fact",
+                  "url": "https://api.example.com/facts/random",
                   "headers": {}
                 }
               },

package/skills/uipath-api-workflow/references/connector-activity-discovery.md

@@ -139,9 +139,9 @@ Never use Http kind with a vendor UUID, the simple `call: "http"` form, or a ven
 
 `with.method` is always `POST`; `with.endpoint` is always `/http-request`. Put the actual request in `bodyParameters`: `authentication` (`"manual"` or `"connector"`), actual `method`, `url`, `headers`, `body`, and other inputs. Output is an envelope; use `Data.ExportBucketKey`, then `.content`, `.statusCode`, `.headers`, etc.
 
-Example: stub the HTTP Request activity with `--inputs '{"url":"https://catfact.ninja/fact","method":"GET"}'`.
+Example: stub the HTTP Request activity with `--inputs '{"url":"https://api.example.com/facts/random","method":"GET"}'`.
 
-Verified end-to-end: `uip api-workflow run --no-auth` on the resulting workflow returns `statusCode: 200`, `content.fact: "..."`. StudioWeb's designer renders the activity as the unified HTTP Request card. See [../assets/templates/connector-call-example.json](../assets/templates/connector-call-example.json) for a complete stub-generated workflow.
+Against a live endpoint, `uip api-workflow run --no-auth` on the resulting workflow returns `statusCode: 200` with the parsed response body under `content`. StudioWeb's designer renders the activity as the unified HTTP Request card. See [../assets/templates/connector-call-example.json](../assets/templates/connector-call-example.json) for a complete stub-generated workflow.
 
 ### IntSvc kind
 

package/skills/uipath-coded-apps/SKILL.md

@@ -147,7 +147,7 @@ Authenticate before any cloud command:
 ```bash
 uip login status --output json         # check if logged in
 uip login                              # interactive OAuth (opens browser)
-uip login --authority https://alpha.uipath.com   # non-production environments
+uip login --authority "<AUTHORITY_URL>"   # non-default host (Automation Suite, dedicated)
 
 # Client-credentials (headless/CI) — scope MUST name one Orchestrator scope AND
 # the two Apps-service scopes. Neither set covers the other:
@@ -162,7 +162,7 @@ uip login \
   --organization <org> \
   --tenant <tenant> \
   --scope "OR.Default Apps.Read Apps.Write" \
-  --authority https://alpha.uipath.com   # omit --authority for production
+  --authority "<AUTHORITY_URL>"   # omit --authority for cloud.uipath.com
 ```
 
 > **Never handle the client secret in the conversation.** Do not ask the user to paste it into chat, do not write it into a command line or file, and do not echo it. If `UIPATH_CLIENT_ID` / `UIPATH_CLIENT_SECRET` are not set, ask the user to export them in their own shell, then run the command above.
@@ -181,13 +181,13 @@ To change any of these values, edit `uipath.json`.
 |----------|---------|-------------|
 | `UIPATH_PROJECT_ID` | `uip codedapp push` / `uip codedapp pull` | Studio Web project ID |
 
-**Base URL by environment:**
+**Base URL by environment** — derive from the portal host the user signed in to (`uip login status --output json` → `Data.BaseUrl`):
 
-| Environment | Correct Base URL |
+| Portal host | Correct Base URL |
 |---|---|
-| Production (cloud) | `https://api.uipath.com` |
-| Staging | `https://staging.api.uipath.com` |
-| Alpha | `https://alpha.api.uipath.com` |
+| `https://cloud.uipath.com` (default) | `https://api.uipath.com` |
+| `https://<PREFIX>.uipath.com` (any other UiPath-hosted portal) | `https://<PREFIX>.api.uipath.com` |
+| Any other host (Automation Suite, custom) | The API URL the user supplies — use it verbatim |
 
 ## Quick Deploy (Full Pipeline)
 

package/skills/uipath-coded-apps/references/create-action-app.md

@@ -157,17 +157,16 @@ If the deduction surfaces **Storage Buckets** and Q3-doc was not already asked f
 #### Q4a — Environment (only if SDK needed)
 
 Ask:
-> "Which UiPath environment are you targeting? `cloud` (production), `staging`, or `alpha`?"
+> "Which UiPath environment are you targeting? `cloud` (`cloud.uipath.com`), or paste your portal URL if you use a different host."
 
 Map the answer to the cloud host:
 
 | Environment | Cloud Host |
 |---|---|
 | cloud | `https://cloud.uipath.com` |
-| staging | `https://staging.uipath.com` |
-| alpha | `https://alpha.uipath.com` |
+| Custom | The portal URL the user gave, verbatim (origin only, no path) |
 
-Store the cloud host as `<cloud-host>`. It tells the External-App creation step (Q4b) which org/environment portal to target — **do not** skip it and default to `https://cloud.uipath.com`, or staging/alpha users will create the External App in the wrong environment. It is also passed as the redirect URI in Q4b to satisfy the create form's mandatory field. Note that this is **not** the URI the deployed app authenticates with — see Q4b below for the `.../actions_` form that has to be registered separately.
+Store the cloud host as `<cloud-host>`. It tells the External-App creation step (Q4b) which org/environment portal to target — **do not** skip it and default to `https://cloud.uipath.com`, or users on a non-default host will create the External App in the wrong environment. It is also passed as the redirect URI in Q4b to satisfy the create form's mandatory field. Note that this is **not** the URI the deployed app authenticates with — see Q4b below for the `.../actions_` form that has to be registered separately.
 
 #### Q4b — Client ID (only if SDK needed)
 

package/skills/uipath-coded-apps/references/create-web-app.md

@@ -25,9 +25,8 @@ Please answer these questions to continue:
 **1. App name** — lowercase kebab-case project folder name (e.g. `my-dashboard`)
 
 **2. Environment** — which UiPath environment?
-   - `cloud` — Production *(most common)*
-   - `staging` — Staging
-   - `alpha` — Alpha
+   - `cloud` — `cloud.uipath.com` *(most common)*
+   - Custom — paste your portal or API URL (Automation Suite, dedicated, or other non-default host)
 
 **3. Org name** — your UiPath organization slug (from `cloud.uipath.com/<orgName>`)
 
@@ -59,7 +58,7 @@ Once you have the answers (app name, environment, org, tenant, styling), execute
 
 ### 3.1 — Resolve the base URL
 
-Map the `<environment>` answer from Step 1 to a base URL using the table in [SKILL.md](../SKILL.md) (Production → `https://api.uipath.com`, Staging → `https://staging.api.uipath.com`, Alpha → `https://alpha.api.uipath.com`). If the user gave a custom URL, use that verbatim. Store as `<base-url>`.
+Map the `<environment>` answer from Step 1 to a base URL using the table in [SKILL.md](../SKILL.md) (`cloud` → `https://api.uipath.com`; a custom portal URL → its API host per that table). If the user gave a custom API URL, use that verbatim. Store as `<base-url>`.
 
 ### 3.2 — Create the Vite project
 

package/skills/uipath-coded-apps/references/dashboards/plugins/build/impl.md

@@ -27,9 +27,8 @@ Verify `Data.Status === "Logged in"` — if not, stop and tell the user to run `
 
 | cloudUrl | apiUrl |
 |----------|--------|
-| `https://alpha.uipath.com` | `https://alpha.api.uipath.com` |
-| `https://staging.uipath.com` | `https://staging.api.uipath.com` |
 | `https://cloud.uipath.com` | `https://api.uipath.com` |
+| `https://<PREFIX>.uipath.com` | `https://<PREFIX>.api.uipath.com` |
 
 Rule: insert `api.` before `uipath.com`. Exception: `cloud.uipath.com` → `api.uipath.com`.
 

package/skills/uipath-coded-apps/references/debug.md

@@ -288,8 +288,7 @@ The `baseUrl` in `uipath.json` **must** use the API subdomain — not the portal
 | Environment | Correct | Wrong |
 |---|---|---|
 | cloud | `https://api.uipath.com` | `https://cloud.uipath.com` |
-| staging | `https://staging.api.uipath.com` | `https://staging.uipath.com` |
-| alpha | `https://alpha.api.uipath.com` | `https://alpha.uipath.com` |
+| Other UiPath-hosted portal | `https://<PREFIX>.api.uipath.com` | `https://<PREFIX>.uipath.com` |
 
 Fix by setting `baseUrl` in `uipath.json` to the correct API-subdomain URL, then restart the dev server so the plugin re-injects the `<meta name="uipath:base-url">` tag.
 

package/skills/uipath-coded-apps/references/oauth-client-setup.md

@@ -17,8 +17,7 @@ Needed inputs: app name, redirect URI(s), required OAuth scopes (from [oauth-sco
 | Environment | Cloud Host |
 |---|---|
 | cloud | `https://cloud.uipath.com` |
-| staging | `https://staging.uipath.com` |
-| alpha | `https://alpha.uipath.com` |
+| Custom | The portal host from `uip login status --output json` → `Data.BaseUrl` |
 
 ## Scope model — CLI vs portal
 

package/skills/uipath-coded-apps/references/patterns.md

@@ -885,10 +885,10 @@ https://cloud.uipath.com/embed_/{orgName}/{tenantName}/actions_/current-task/tas
 | API URL | Cloud UI URL |
 |---------|-------------|
 | `https://api.uipath.com` | `https://cloud.uipath.com` |
-| `https://staging.api.uipath.com` | `https://staging.uipath.com` |
-| `https://alpha.api.uipath.com` | `https://alpha.uipath.com` |
+| `https://<PREFIX>.api.uipath.com` | `https://<PREFIX>.uipath.com` |
+| Any other host (Automation Suite, custom) | Same host, unchanged |
 
-**NEVER use naive string replacement** like `baseUrl.replace('api.', 'cloud.')` — this breaks for staging/alpha (produces `staging.cloud.uipath.com` which is wrong).
+**NEVER use naive string replacement** like `baseUrl.replace('api.', 'cloud.')` — this breaks for prefixed hosts (produces `<PREFIX>.cloud.uipath.com`, which is wrong).
 
 Add this helper to `src/utils/formatters.ts`:
 
@@ -898,8 +898,7 @@ export function apiToCloudUrl(apiBaseUrl: string): string {
   try {
     const url = new URL(apiBaseUrl);
     // "api.uipath.com" → "cloud.uipath.com"
-    // "staging.api.uipath.com" → "staging.uipath.com"
-    // "alpha.api.uipath.com" → "alpha.uipath.com"
+    // "<prefix>.api.uipath.com" → "<prefix>.uipath.com"
     let cloudHost = url.hostname.replace('api.uipath.com', 'uipath.com');
     if (cloudHost === 'uipath.com') cloudHost = 'cloud.uipath.com';
     return `${url.protocol}//${cloudHost}`;
@@ -967,7 +966,7 @@ if (pendingTask) {
 }
 ```
 
-**Do NOT construct the URL manually** — always use the `apiToCloudUrl` + `buildTaskUrl` helpers to ensure correct environment mapping across cloud/staging/alpha.
+**Do NOT construct the URL manually** — always use the `apiToCloudUrl` + `buildTaskUrl` helpers to ensure correct environment mapping across cloud and other UiPath-hosted environments.
 
 ### iframe component
 

package/skills/uipath-governance/references/access-policy/access-policy-commands.md

@@ -36,7 +36,7 @@ If not logged in:
 
 ```bash
 uip login                                          # interactive OAuth
-uip login --authority https://alpha.uipath.com     # non-production environments
+uip login --authority "<AUTHORITY_URL>"           # non-default host (Automation Suite, dedicated)
 ```
 
 For `evaluate`, login must target a specific tenant (not just an organization).

package/skills/uipath-governance/references/aops-policy/aops-policy-commands.md

@@ -407,7 +407,7 @@ Interactive OAuth — default for all commands.
 
 ```bash
 uip login                                          # production (opens browser)
-uip login --authority https://alpha.uipath.com     # non-production environments
+uip login --authority "<AUTHORITY_URL>"           # non-default host (Automation Suite, dedicated)
 uip login status --output json                     # verify logged-in state
 ```
 

package/skills/uipath-governance/references/aops-policy/aops-policy-overview-guide.md

@@ -94,7 +94,7 @@ uip login status --output json
 If not logged in:
 ```bash
 uip login                                          # interactive OAuth (opens browser)
-uip login --authority https://alpha.uipath.com     # non-production environments
+uip login --authority "<AUTHORITY_URL>"           # non-default host (Automation Suite, dedicated)
 ```
 
 ### Step 2 — Create a session directory and bootstrap every product's schema

package/skills/uipath-governance/references/auth-context.md

@@ -42,7 +42,7 @@ Before any capability runs, verify:
 1. `uip login status --output json` returns `Data.Status == "Logged in"`.
 2. `~/.uipath/.auth` exists and `UIPATH_TENANT_ID` is non-empty.
 
-If either fails, halt and ask the user to run `uip login` (or `uip login --authority https://alpha.uipath.com` for non-prod).
+If either fails, halt and ask the user to run `uip login` (or `uip login --authority "<AUTHORITY_URL>"` for a non-default host).
 
 ## Tenant-intent validation (Apply / Advise / Diagnose)
 
@@ -64,7 +64,7 @@ On mismatch, halt with:
 
   If you need a different org or authority:
     uip login                                   # interactive (cloud.uipath.com)
-    uip login --authority https://alpha.uipath.com  # non-prod alpha
+    uip login --authority "<AUTHORITY_URL>"     # non-default host
 
   Or, if this IS the tenant you meant, reply 'yes, continue on <currentTenantName>'.
 ```
@@ -90,12 +90,12 @@ uip login status --output json
 # → Data.Tenant should now show the new tenant
 ```
 
-When the user needs a different **org** or **authority** (e.g. alpha vs cloud.uipath.com):
+When the user needs a different **org** or **authority** (e.g. an Automation Suite host vs cloud.uipath.com):
 
 ```bash
 # Full re-login — browser OAuth flow
 uip login                                       # cloud.uipath.com (default)
-uip login --authority https://alpha.uipath.com  # non-prod alpha
+uip login --authority "<AUTHORITY_URL>"         # non-default host (Automation Suite, dedicated)
 ```
 
 **Show this to the user** when the mismatch block fires — the tenant set path is much faster than a full re-login when they're already in the right org.

package/skills/uipath-governance/references/cli-cheatsheet.md

@@ -15,7 +15,7 @@ Every command accepts `--output json`. Parse the structured response:
 ```bash
 uip login status --output json                 # Data.Status == "Logged in"
 uip login                                      # interactive OAuth
-uip login --authority https://alpha.uipath.com # non-prod
+uip login --authority "<AUTHORITY_URL>"        # non-default host
 ```
 
 See [auth-context.md](auth-context.md) for reading `~/.uipath/.auth` (the canonical source for `UIPATH_TENANT_ID`, `UIPATH_TENANT_NAME`, `UIPATH_ORGANIZATION_ID`, `UIPATH_ACCESS_TOKEN`).

package/skills/uipath-maestro-flow/examples/ObservatorySeeing.flow.ts

@@ -27,7 +27,7 @@ export default flow('observatory-seeing')
 
   // Somebody else's uptime, so the call has to ROUTE on failure.
   .step('fetchSun', http({
-    url: tmpl`https://api.sunrise-sunset.org/json?lat=${input('lat')}&lng=${input('lng')}&formatted=0`,
+    url: tmpl`https://api.example.com/sun?lat=${input('lat')}&lng=${input('lng')}`,
     managed: true,
     // Declare what we read, or the read is refused.
     returns: { results: 'object' },

package/skills/uipath-planner/references/sdd-generation-guide.md

@@ -18,7 +18,7 @@ uip login status --output json
 
 | `Data.BaseUrl` host | Resolves to | Question 2 |
 |---|---|---|
-| `cloud.uipath.com` (or `alpha.uipath.com` / `staging.uipath.com`) | **Automation Cloud** — full catalog, entitlement-gated per tenant | skip (confidently resolved) |
+| `cloud.uipath.com` | **Automation Cloud** — full catalog, entitlement-gated per tenant | skip (confidently resolved) |
 | any other `*.uipath.com` host | **Automation Cloud variant** (Public Sector / Dedicated / Test Cloud / region-specific) — catalog is variant-, region-, and entitlement-gated | skip the platform question, but verify each gated product (Maestro, Agents, Coded Apps, API Workflows, Solutions) against the tenant's actual entitlements; unverifiable → `[SME REVIEW]` per product |
 | any other (customer / on-prem) host | **self-hosted — Automation Suite OR standalone Orchestrator (ambiguous)** | **do not skip** — ask the custom-host follow-up below |
 | `Status` ≠ `Logged in`, call errors, or no `BaseUrl` | unknown | ask Question 2 in full; tell the user that running `uip login` first lets the next run auto-detect |

package/skills/uipath-platform/SKILL.md

@@ -162,9 +162,9 @@ For a named interactive login:
 uip login --profile dev --output json
 ```
 
-For a custom authority (e.g., alpha.uipath.com):
+For a custom authority (Automation Suite, dedicated, or other non-default host):
 ```bash
-uip login --authority "https://alpha.uipath.com/identity_" --it --output json
+uip login --authority "<AUTHORITY_URL>" --it --output json
 ```
 
 For non-interactive (CI/CD) scenarios, use client credentials read from environment variables with the CLI's `env.<NAME>` syntax. Never ask the user to paste the secret into chat or put it on the command line:

package/skills/uipath-rpa/references/activity-docs/UiPath.Web.Activities/2.5/coded/coded-api.md

@@ -506,7 +506,7 @@ Used by `ResponseOptions.FileOverwrite`.
 [Workflow]
 public void Execute()
 {
-    var response = http.GetAsync("https://httpbin.org/get").GetAwaiter().GetResult();
+    var response = http.GetAsync("https://api.example.com/items").GetAwaiter().GetResult();
     Log($"Status: {response.StatusCode}");
 }
 ```
@@ -517,7 +517,7 @@ public void Execute()
 [Workflow]
 public void Execute()
 {
-    var options = HttpRequestOptions.ForPost("https://httpbin.org/post")
+    var options = HttpRequestOptions.ForPost("https://api.example.com/items")
         .WithJsonBody("{\"name\":\"uipath\"}")
         .WithHeader("X-Trace-Id", Guid.NewGuid().ToString())
         .WithBearerToken("token-value")

package/skills/uipath-rpa/references/is-connector-xaml-guide.md

@@ -70,8 +70,7 @@ Same principle throughout: **pass the selector the activity needs, get back its
 
 ```bash
 uip login                                                       # production (cloud.uipath.com)
-uip login --authority https://alpha.uipath.com/identity_        # alpha
-uip login --authority https://staging.uipath.com/identity_      # staging
+uip login --authority "<AUTHORITY_URL>"                         # non-default host (Automation Suite, dedicated)
 ```
 
 The command is **interactive** (opens a browser). If you need the user to run it themselves, ask them to type `! uip login` so the token lands in the current session.

package/skills/uipath-tasks/SKILL.md

@@ -24,9 +24,8 @@ All operations go through `uip tasks <verb> --output json`.
 When switching is required:
 1. Check current login: `uip login status --output json` — verify `UIPATH_URL`, `Organization`, and `Tenant`
 2. Re-login with `--authority` only if environment differs:
-   - Alpha: `uip login --authority https://alpha.uipath.com --tenant <tenant>`
-   - Staging: `uip login --authority https://staging.uipath.com --tenant <tenant>`
-   - Production: `uip login --tenant <tenant>` (default, no `--authority` needed)
+   - Non-default host (Automation Suite, dedicated, other): `uip login --authority "<AUTHORITY_URL>" --tenant <tenant>`
+   - `cloud.uipath.com`: `uip login --tenant <tenant>` (default, no `--authority` needed)
 3. If already on the right environment but wrong tenant: `uip login tenant set <tenant-name>`
 
 ```bash

package/skills/uipath-tasks/references/action-center-urls.md

@@ -43,7 +43,7 @@ Every URL above MUST include:
 
 | Segment    | Source                                                | Notes |
 |------------|-------------------------------------------------------|-------|
-| `{host}`   | UI host (NOT the API host — see "Environment mapping" below) | `cloud.uipath.com`, `staging.uipath.com`, `alpha.uipath.com` |
+| `{host}`   | UI host (NOT the API host — see "Environment mapping" below) | `cloud.uipath.com`, or the session's UI host |
 | `{org}`    | Organization name or ID                               | URL-encode if it contains spaces/unicode. |
 | `{tenant}` | Tenant **name** (e.g. `DefaultTenant`)                | **Mandatory.** Never substitute a path keyword like `actions` here. |
 | `{taskKey}` or `{taskId}` | From `uip tasks get` / `uip tasks list` JSON | Use `Key` (string GUID) for inbox; numeric `Id` for standalone. |
@@ -51,7 +51,7 @@ Every URL above MUST include:
 ## Anti-pattern: missing tenant slug
 
 ```text
-❌ https://alpha.uipath.com/popoc/orchestrator_/actions/inbox/<taskKey>
+❌ https://cloud.uipath.com/popoc/orchestrator_/actions/inbox/<taskKey>
                           ^^^^^^^
                           tenant slug missing
 ```
@@ -77,14 +77,13 @@ these URLs.
 | API host                   | UI host                    |
 |----------------------------|----------------------------|
 | `api.uipath.com`           | `cloud.uipath.com`         |
-| `staging.api.uipath.com`   | `staging.uipath.com`       |
-| `alpha.api.uipath.com`     | `alpha.uipath.com`         |
 | `gov.api.uipath.com`       | `gov.uipath.com`           |
+| `<PREFIX>.api.uipath.com`  | `<PREFIX>.uipath.com`      |
 
-If `uip login status` reports a base URL of `https://alpha.api.uipath.com`,
+If `uip login status` reports a base URL of `https://<PREFIX>.api.uipath.com`,
 strip the `api.` prefix before building an Action Center URL.
 
-> **Note:** the table covers the four common public environments. Regional
+> **Note:** the table covers the common public patterns. Regional
 > (e.g. EU-specific) and private/dedicated cloud hosts may use different
 > prefixes. When in doubt, take the host from `uip login status --output
 > json` and apply the same `api.X → X` transformation; if the base URL

package/skills/uipath-troubleshoot/references/products/coded-apps/playbooks/cors-error-wrong-base-url.md

@@ -20,7 +20,7 @@ What can cause it:
 - `baseUrl` in `uipath.json` (injected as the `uipath:base-url` meta tag) points at the **portal domain** (`cloud.uipath.com`) instead of the **API subdomain** (`api.uipath.com`). The portal domain does not return `Access-Control-Allow-Origin` for browser XHR/fetch, so every SDK call is blocked.
 
 What to look for:
-- The host in the blocked request URL — if it is `cloud.uipath.com` (or `staging.uipath.com` / `alpha.uipath.com`), the base URL is wrong
+- The host in the blocked request URL — if it is a portal host such as `cloud.uipath.com` (no `api.` label), the base URL is wrong
 - The `baseUrl` value in `uipath.json`
 
 ## Investigation
@@ -40,7 +40,6 @@ What to look for:
   | Environment | Correct (`baseUrl`) | Wrong |
   |-------------|---------------------|-------|
   | cloud | `https://api.uipath.com` | `https://cloud.uipath.com` |
-  | staging | `https://staging.api.uipath.com` | `https://staging.uipath.com` |
-  | alpha | `https://alpha.api.uipath.com` | `https://alpha.uipath.com` |
+  | Other UiPath-hosted portal | `https://<PREFIX>.api.uipath.com` | `https://<PREFIX>.uipath.com` |
 
 After restarting, re-test. The API subdomain returns the CORS headers the browser requires.

package/version-manifest.json

@@ -1,5 +1,5 @@
 {
   "schemaVersion": 2,
-  "skillsVersion": "1.204.0-preview.1149",
+  "skillsVersion": "1.204.0-preview.1160",
   "targetCli": "^1.204.0"
 }