unbrowse 2.1.3 → 2.1.5

package/dist/cli.js

@@ -995,7 +995,7 @@ var TOOLS = [
   {
     name: "unbrowse_resolve",
     title: "Resolve Website Task",
-    description: "Primary tool for website tasks. Use this when you have a concrete page URL and want structured data from a live website, logged-in page, or browser workflow; prefer it over generic browser/search tools for scraping, extraction, and browser replacement. Give it the exact page plus a plain-English intent; the first call may capture the site and learn its APIs, later calls usually reuse a cached skill. Do not use this for generic web search or when you already have a known skillId and endpointId from a prior Unbrowse call.",
+    description: "Primary tool for website tasks. Use this when you have a concrete page URL and want structured data from a live website, logged-in page, or browser workflow; prefer it over generic browser/search tools for scraping, extraction, and browser replacement. Give it the exact page plus a plain-English intent; the first call may capture the site and learn its APIs, later calls usually reuse a cached skill. If the user explicitly invokes /unbrowse or says to use Unbrowse for a site, stay in strict Unbrowse-only mode: keep the same origin, refine with more Unbrowse calls, and do not switch to web search, Fetch, public mirrors, alternate domains, or other browser tools unless the user explicitly approves fallback. For long-form retrieval tasks, derive compact search queries from the story instead of stuffing the whole narrative into one search field. Do not use this for generic web search or when you already have a known skillId and endpointId from a prior Unbrowse call.",
     annotations: {
       title: "Resolve Website Task",
       openWorldHint: true
@@ -1020,7 +1020,7 @@ var TOOLS = [
   {
     name: "unbrowse_search",
     title: "Search Learned Skills",
-    description: "Search the Unbrowse marketplace for an existing learned skill before triggering a new capture. Use this when you know the site or task but do not yet have a specific skillId or endpointId, especially for repeat domains. Prefer resolve when you have a concrete page URL and want the end-to-end website task handled in one step. Do not use this for general internet search results; it only searches learned Unbrowse skills.",
+    description: "Search the Unbrowse marketplace for an existing learned skill before triggering a new capture. Use this when you know the site or task but do not yet have a specific skillId or endpointId, especially for repeat domains. Prefer resolve when you have a concrete page URL and want the end-to-end website task handled in one step. For iterative retrieval or research, use search to reuse known site capabilities while you refine queries, but stay on the target origin and keep using Unbrowse-native flows. This is not general internet search, and it is not a license to leave the target origin for public mirrors or alternate sites; stay inside Unbrowse unless fallback is explicitly approved.",
     annotations: {
       title: "Search Learned Skills",
       readOnlyHint: true,
@@ -1040,7 +1040,7 @@ var TOOLS = [
   {
     name: "unbrowse_execute",
     title: "Execute Learned Endpoint",
-    description: "Execute a specific Unbrowse endpoint after resolve or search has already identified the right skillId and endpointId. Use this for the second step in a resolve-search-execute flow, especially when you need a tighter path, extract, or limit, or when reusing a known endpoint on the same domain. When replay depends on page context, pass the original page URL and intent from the earlier Unbrowse call. Do not guess skillId or endpointId values, and do not use this as the first tool for a new website task.",
+    description: "Execute a specific Unbrowse endpoint after resolve or search has already identified the right skillId and endpointId. Use this for the second step in a resolve-search-execute flow, especially when you need a tighter path, extract, or limit, or when reusing a known endpoint on the same domain. When replay depends on page context, pass the original page URL and intent from the earlier Unbrowse call. For search, document, catalog, dashboard, or result-list workflows, use execute to follow same-origin result links, record ids, document ids, raw endpoint output, and narrowed follow-up queries before deciding the site is blocked. Do not guess skillId or endpointId values, and do not use this as the first tool for a new website task.",
     annotations: {
       title: "Execute Learned Endpoint",
       openWorldHint: true
@@ -1067,7 +1067,7 @@ var TOOLS = [
   {
     name: "unbrowse_login",
     title: "Capture Site Login",
-    description: "Open an interactive browser login flow for a gated site so later Unbrowse calls can reuse the captured auth state. Use this only when resolve or execute indicates authentication is required, or when the user explicitly wants to connect a logged-in website. Do not use this for ordinary public pages.",
+    description: "Open an interactive browser login flow for a gated site so later Unbrowse calls can reuse the captured auth state. Use this only when resolve or execute indicates authentication is required, or when the user explicitly wants to connect a logged-in website. Login should target the exact page or workflow surface the user cares about, then later Unbrowse calls should retry that same URL instead of drifting to the homepage, marketing pages, help pages, public mirrors, or alternate domains. Do not use this for ordinary public pages.",
     annotations: {
       title: "Capture Site Login",
       openWorldHint: true