@copilotkit/web-inspector 1.73.2-canary.1790085728 → 1.73.3

package/dist/lib/onboarding-prompt.cjs

@@ -13,12 +13,11 @@
 * The CLI resolves `onboard start` against a prompt graph, so the two surfaces
 * must not drift — if the CLI's entry point changes, both change together.
 *
-* Two lines, and deliberately nothing else. It used to open by telling the
-* agent to identify itself and pass the slug as a flag -- two sentences of
-* instruction to a machine, in the one piece of text a human reads, decides on
-* and pastes. The graph asks for the slug itself now, with `onboard identify`,
-* which is the surface that talks to the agent for the rest of the run
-* (Intelligence OSS-1157).
+* One sentence, and deliberately nothing else. It used to carry the `npx`
+* command itself, which put a command line and a telemetry id in the one piece
+* of text a human reads, decides on and pastes. The command now lives in the
+* document the URL serves, with the run id already written into it
+* (PE-216/PE-217).
 *
 * This one stays generic, and so do the docs and Intelligence web-app copies
 * of it (OSS-1150). Those three are entry points for a developer with no
@@ -29,9 +28,8 @@
 * `FEATURE_ONBOARDING_PROMPT_TEMPLATE` below.
 */
 const RUN_ID_PLACEHOLDER = "<run-id>";
-const ONBOARDING_PROMPT_TEMPLATE = `Help me get started with CopilotKit. Run this command and follow the instructions:
-
-npx --yes copilotkit@latest onboard start --run ${RUN_ID_PLACEHOLDER}`;
+const ONBOARDING_PROMPT_ORIGIN = "https://copilotkit.ai";
+const ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER} and help me get set up.`;
 /** Length and alphabet are the CLI's, so a run id copied here resolves there. */
 const RUN_ID_LENGTH = 12;
 /**
@@ -92,15 +90,11 @@ const INTENT_PLACEHOLDER = "<intent>";
 * here would duplicate all of that and then drift from it the next time the
 * underlying API changes.
 *
-* What is left is the caller's own business: identify yourself, run this
-* command, and the standing permission for the session check that the
-* developer granted by copying the prompt.
+* The session-check permission the developer granted by copying this, and the
+* credentials warning beside it, moved with the command into the document the
+* URL serves. They are not dropped.
 */
-const FEATURE_ONBOARDING_PROMPT_TEMPLATE = `Help me set this up in my CopilotKit app. Run this command and follow the instructions:
-
-npx --yes copilotkit@latest onboard start --run ${RUN_ID_PLACEHOLDER} --intent ${INTENT_PLACEHOLDER}
-
-If it requires a CopilotKit CLI session check, you have permission to run it. Never reveal credentials.`;
+const FEATURE_ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER}?intent=${INTENT_PLACEHOLDER} and help me set this up.`;
 /** Bind one run id and one tile's feature outcome into the copied prompt. */
 function createFeatureOnboardingPrompt(serviceId, runId) {
 	return FEATURE_ONBOARDING_PROMPT_TEMPLATE.replace(RUN_ID_PLACEHOLDER, runId).replace(INTENT_PLACEHOLDER, FEATURE_ONBOARDING_INTENT[serviceId]);

package/dist/lib/onboarding-prompt.cjs.map

@@ -1 +1 @@
-{"version":3,"file":"onboarding-prompt.cjs","names":[],"sources":["../../src/lib/onboarding-prompt.ts"],"sourcesContent":["import type { HomeServiceId } from \"./home-briefing.js\";\n\n/**\n * The Intelligence install prompt the Inspector hands to a coding agent.\n *\n * Every other Intelligence call to action in the Inspector opens a page in a\n * new tab, which is where developers drop out: they leave the editor, meet a\n * signup form, and never come back. This prompt lets the install happen where\n * they already are.\n *\n * The wording is kept byte-identical to `INTELLIGENCE_ONBOARDING_PROMPT` in the\n * Intelligence app (`apps/app-frontend/react-shell/src/home/intelligence-home.tsx`).\n * The CLI resolves `onboard start` against a prompt graph, so the two surfaces\n * must not drift — if the CLI's entry point changes, both change together.\n *\n * Two lines, and deliberately nothing else. It used to open by telling the\n * agent to identify itself and pass the slug as a flag -- two sentences of\n * instruction to a machine, in the one piece of text a human reads, decides on\n * and pastes. The graph asks for the slug itself now, with `onboard identify`,\n * which is the surface that talks to the agent for the rest of the run\n * (Intelligence OSS-1157).\n *\n * This one stays generic, and so do the docs and Intelligence web-app copies\n * of it (OSS-1150). Those three are entry points for a developer with no\n * CopilotKit app yet, and every `--intent` route requires an existing app: it\n * inspects for one first and reads `feature/stop` when it is missing. The\n * feature buttons on Home are the surface that knows which feature the\n * developer is looking at, so they are the surface that names an intent — see\n * `FEATURE_ONBOARDING_PROMPT_TEMPLATE` below.\n */\nconst RUN_ID_PLACEHOLDER = \"<run-id>\";\n\nexport const ONBOARDING_PROMPT_TEMPLATE =\n  \"Help me get started with CopilotKit. Run this command and follow the \" +\n  \"instructions:\\n\\nnpx --yes copilotkit@latest onboard start --run \" +\n  `${RUN_ID_PLACEHOLDER}`;\n\n/** Length and alphabet are the CLI's, so a run id copied here resolves there. */\nconst RUN_ID_LENGTH = 12;\n\n/**\n * Mint the identifier that joins this copy to the CLI run it starts.\n *\n * The Intelligence app derives it from `crypto.randomUUID()`. The Inspector\n * runs inside whatever page embeds it, so neither `randomUUID` nor a secure\n * context is guaranteed; the two fallbacks keep the id present rather than\n * letting the button fail. Collision risk is irrelevant — this correlates\n * telemetry, it does not authorise anything.\n */\nexport function createOnboardingRunId(): string {\n  const webCrypto = globalThis.crypto;\n\n  if (typeof webCrypto?.randomUUID === \"function\") {\n    return webCrypto.randomUUID().replaceAll(\"-\", \"\").slice(0, RUN_ID_LENGTH);\n  }\n\n  if (typeof webCrypto?.getRandomValues === \"function\") {\n    const bytes = webCrypto.getRandomValues(new Uint8Array(RUN_ID_LENGTH / 2));\n    return Array.from(bytes, (byte) => byte.toString(16).padStart(2, \"0\")).join(\n      \"\",\n    );\n  }\n\n  let id = \"\";\n  while (id.length < RUN_ID_LENGTH) {\n    id += Math.floor(Math.random() * 16).toString(16);\n  }\n  return id.slice(0, RUN_ID_LENGTH);\n}\n\n/** Bind one run id into the prompt text that gets copied. */\nexport function createOnboardingPrompt(runId: string): string {\n  return ONBOARDING_PROMPT_TEMPLATE.replace(RUN_ID_PLACEHOLDER, runId);\n}\n\n/**\n * The closed set of feature outcomes the CLI prompt graph can start at.\n *\n * Kept equal to `ONBOARDING_INTENT_ROOTS` in Intelligence's\n * `apps/cli/onboarding-intents.cjs`, which is the build-time source of truth.\n * The two repositories cannot import each other, so the agreement is held by\n * this list plus the CLI's own `onboarding-intents.spec.ts`. Drift is loud\n * rather than silent: `onboard start` refuses an unknown `--intent` before it\n * persists a run, so a stale slug fails on the first command instead of\n * quietly onboarding the wrong feature.\n */\nexport const ONBOARDING_INTENTS = [\n  \"add-a2ui\",\n  \"add-chat-suggestions\",\n  \"add-learning\",\n  \"add-open-generative-ui\",\n  \"add-realtime-sync\",\n  \"add-rich-threads\",\n  \"add-voice\",\n] as const;\n\nexport type OnboardingIntent = (typeof ONBOARDING_INTENTS)[number];\n\n/**\n * Which feature outcome each Home tile asks the CLI for.\n *\n * The two vocabularies stay separate on purpose. A `HomeServiceId` names a\n * tile and the pane behind it, so `websocket` and `audio` are the right words\n * for it; an intent names the work to be done, so `add-realtime-sync` and\n * `add-voice` are the right words for that. One table maps between them, and\n * `Record<HomeServiceId, OnboardingIntent>` makes a new tile or a renamed\n * slug a type error rather than a missing button.\n *\n * `memory` maps to `add-learning` because the tile is the Learning tile: it is\n * enabled by a *configured Learning container* (see `learningOn` in\n * `index.ts`), which is exactly what `feature/learning` sets up. The tile id\n * and the `memories` menu key are older names for that same pane.\n */\nexport const FEATURE_ONBOARDING_INTENT: Record<\n  HomeServiceId,\n  OnboardingIntent\n> = {\n  threads: \"add-rich-threads\",\n  memory: \"add-learning\",\n  a2ui: \"add-a2ui\",\n  \"open-gen-ui\": \"add-open-generative-ui\",\n  suggestions: \"add-chat-suggestions\",\n  audio: \"add-voice\",\n  websocket: \"add-realtime-sync\",\n};\n\nconst INTENT_PLACEHOLDER = \"<intent>\";\n\n/**\n * The prompt a Home feature button copies.\n *\n * It carries no feature-specific instruction, and it must not gain any. The\n * `--intent` route owns the plan, the guide links, the per-phase check-ins,\n * the refusal when a prerequisite is missing, and the proof step; prose copied\n * here would duplicate all of that and then drift from it the next time the\n * underlying API changes.\n *\n * What is left is the caller's own business: identify yourself, run this\n * command, and the standing permission for the session check that the\n * developer granted by copying the prompt.\n */\nexport const FEATURE_ONBOARDING_PROMPT_TEMPLATE =\n  \"Help me set this up in my CopilotKit app. Run this command and follow the \" +\n  \"instructions:\\n\\nnpx --yes copilotkit@latest onboard start --run \" +\n  `${RUN_ID_PLACEHOLDER} --intent ${INTENT_PLACEHOLDER}` +\n  \"\\n\\nIf it requires a CopilotKit CLI session check, you have permission to \" +\n  \"run it. Never reveal credentials.\";\n\n/** Bind one run id and one tile's feature outcome into the copied prompt. */\nexport function createFeatureOnboardingPrompt(\n  serviceId: HomeServiceId,\n  runId: string,\n): string {\n  return FEATURE_ONBOARDING_PROMPT_TEMPLATE.replace(\n    RUN_ID_PLACEHOLDER,\n    runId,\n  ).replace(INTENT_PLACEHOLDER, FEATURE_ONBOARDING_INTENT[serviceId]);\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA8BA,MAAM,qBAAqB;AAE3B,MAAa,6BACX;;kDAEG;;AAGL,MAAM,gBAAgB;;;;;;;;;;AAWtB,SAAgB,wBAAgC;CAC9C,MAAM,YAAY,WAAW;AAE7B,KAAI,OAAO,WAAW,eAAe,WACnC,QAAO,UAAU,YAAY,CAAC,WAAW,KAAK,GAAG,CAAC,MAAM,GAAG,cAAc;AAG3E,KAAI,OAAO,WAAW,oBAAoB,YAAY;EACpD,MAAM,QAAQ,UAAU,gBAAgB,IAAI,WAAW,gBAAgB,EAAE,CAAC;AAC1E,SAAO,MAAM,KAAK,QAAQ,SAAS,KAAK,SAAS,GAAG,CAAC,SAAS,GAAG,IAAI,CAAC,CAAC,KACrE,GACD;;CAGH,IAAI,KAAK;AACT,QAAO,GAAG,SAAS,cACjB,OAAM,KAAK,MAAM,KAAK,QAAQ,GAAG,GAAG,CAAC,SAAS,GAAG;AAEnD,QAAO,GAAG,MAAM,GAAG,cAAc;;;AAInC,SAAgB,uBAAuB,OAAuB;AAC5D,QAAO,2BAA2B,QAAQ,oBAAoB,MAAM;;;;;;;;;;;;;;;;;AAyCtE,MAAa,4BAGT;CACF,SAAS;CACT,QAAQ;CACR,MAAM;CACN,eAAe;CACf,aAAa;CACb,OAAO;CACP,WAAW;CACZ;AAED,MAAM,qBAAqB;;;;;;;;;;;;;;AAe3B,MAAa,qCACX;;kDAEG,mBAAmB,YAAY;;;;AAKpC,SAAgB,8BACd,WACA,OACQ;AACR,QAAO,mCAAmC,QACxC,oBACA,MACD,CAAC,QAAQ,oBAAoB,0BAA0B,WAAW"}
+{"version":3,"file":"onboarding-prompt.cjs","names":[],"sources":["../../src/lib/onboarding-prompt.ts"],"sourcesContent":["import type { HomeServiceId } from \"./home-briefing.js\";\n\n/**\n * The Intelligence install prompt the Inspector hands to a coding agent.\n *\n * Every other Intelligence call to action in the Inspector opens a page in a\n * new tab, which is where developers drop out: they leave the editor, meet a\n * signup form, and never come back. This prompt lets the install happen where\n * they already are.\n *\n * The wording is kept byte-identical to `INTELLIGENCE_ONBOARDING_PROMPT` in the\n * Intelligence app (`apps/app-frontend/react-shell/src/home/intelligence-home.tsx`).\n * The CLI resolves `onboard start` against a prompt graph, so the two surfaces\n * must not drift — if the CLI's entry point changes, both change together.\n *\n * One sentence, and deliberately nothing else. It used to carry the `npx`\n * command itself, which put a command line and a telemetry id in the one piece\n * of text a human reads, decides on and pastes. The command now lives in the\n * document the URL serves, with the run id already written into it\n * (PE-216/PE-217).\n *\n * This one stays generic, and so do the docs and Intelligence web-app copies\n * of it (OSS-1150). Those three are entry points for a developer with no\n * CopilotKit app yet, and every `--intent` route requires an existing app: it\n * inspects for one first and reads `feature/stop` when it is missing. The\n * feature buttons on Home are the surface that knows which feature the\n * developer is looking at, so they are the surface that names an intent — see\n * `FEATURE_ONBOARDING_PROMPT_TEMPLATE` below.\n */\nconst RUN_ID_PLACEHOLDER = \"<run-id>\";\n\nexport const ONBOARDING_PROMPT_ORIGIN = \"https://copilotkit.ai\";\n\nexport const ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER} and help me get set up.`;\n\n/** Length and alphabet are the CLI's, so a run id copied here resolves there. */\nconst RUN_ID_LENGTH = 12;\n\n/**\n * Mint the identifier that joins this copy to the CLI run it starts.\n *\n * The Intelligence app derives it from `crypto.randomUUID()`. The Inspector\n * runs inside whatever page embeds it, so neither `randomUUID` nor a secure\n * context is guaranteed; the two fallbacks keep the id present rather than\n * letting the button fail. Collision risk is irrelevant — this correlates\n * telemetry, it does not authorise anything.\n */\nexport function createOnboardingRunId(): string {\n  const webCrypto = globalThis.crypto;\n\n  if (typeof webCrypto?.randomUUID === \"function\") {\n    return webCrypto.randomUUID().replaceAll(\"-\", \"\").slice(0, RUN_ID_LENGTH);\n  }\n\n  if (typeof webCrypto?.getRandomValues === \"function\") {\n    const bytes = webCrypto.getRandomValues(new Uint8Array(RUN_ID_LENGTH / 2));\n    return Array.from(bytes, (byte) => byte.toString(16).padStart(2, \"0\")).join(\n      \"\",\n    );\n  }\n\n  let id = \"\";\n  while (id.length < RUN_ID_LENGTH) {\n    id += Math.floor(Math.random() * 16).toString(16);\n  }\n  return id.slice(0, RUN_ID_LENGTH);\n}\n\n/** Bind one run id into the prompt text that gets copied. */\nexport function createOnboardingPrompt(runId: string): string {\n  return ONBOARDING_PROMPT_TEMPLATE.replace(RUN_ID_PLACEHOLDER, runId);\n}\n\n/**\n * The closed set of feature outcomes the CLI prompt graph can start at.\n *\n * Kept equal to `ONBOARDING_INTENT_ROOTS` in Intelligence's\n * `apps/cli/onboarding-intents.cjs`, which is the build-time source of truth.\n * The two repositories cannot import each other, so the agreement is held by\n * this list plus the CLI's own `onboarding-intents.spec.ts`. Drift is loud\n * rather than silent: `onboard start` refuses an unknown `--intent` before it\n * persists a run, so a stale slug fails on the first command instead of\n * quietly onboarding the wrong feature.\n */\nexport const ONBOARDING_INTENTS = [\n  \"add-a2ui\",\n  \"add-chat-suggestions\",\n  \"add-learning\",\n  \"add-open-generative-ui\",\n  \"add-realtime-sync\",\n  \"add-rich-threads\",\n  \"add-voice\",\n] as const;\n\nexport type OnboardingIntent = (typeof ONBOARDING_INTENTS)[number];\n\n/**\n * Which feature outcome each Home tile asks the CLI for.\n *\n * The two vocabularies stay separate on purpose. A `HomeServiceId` names a\n * tile and the pane behind it, so `websocket` and `audio` are the right words\n * for it; an intent names the work to be done, so `add-realtime-sync` and\n * `add-voice` are the right words for that. One table maps between them, and\n * `Record<HomeServiceId, OnboardingIntent>` makes a new tile or a renamed\n * slug a type error rather than a missing button.\n *\n * `memory` maps to `add-learning` because the tile is the Learning tile: it is\n * enabled by a *configured Learning container* (see `learningOn` in\n * `index.ts`), which is exactly what `feature/learning` sets up. The tile id\n * and the `memories` menu key are older names for that same pane.\n */\nexport const FEATURE_ONBOARDING_INTENT: Record<\n  HomeServiceId,\n  OnboardingIntent\n> = {\n  threads: \"add-rich-threads\",\n  memory: \"add-learning\",\n  a2ui: \"add-a2ui\",\n  \"open-gen-ui\": \"add-open-generative-ui\",\n  suggestions: \"add-chat-suggestions\",\n  audio: \"add-voice\",\n  websocket: \"add-realtime-sync\",\n};\n\nconst INTENT_PLACEHOLDER = \"<intent>\";\n\n/**\n * The prompt a Home feature button copies.\n *\n * It carries no feature-specific instruction, and it must not gain any. The\n * `--intent` route owns the plan, the guide links, the per-phase check-ins,\n * the refusal when a prerequisite is missing, and the proof step; prose copied\n * here would duplicate all of that and then drift from it the next time the\n * underlying API changes.\n *\n * The session-check permission the developer granted by copying this, and the\n * credentials warning beside it, moved with the command into the document the\n * URL serves. They are not dropped.\n */\nexport const FEATURE_ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER}?intent=${INTENT_PLACEHOLDER} and help me set this up.`;\n\n/** Bind one run id and one tile's feature outcome into the copied prompt. */\nexport function createFeatureOnboardingPrompt(\n  serviceId: HomeServiceId,\n  runId: string,\n): string {\n  return FEATURE_ONBOARDING_PROMPT_TEMPLATE.replace(\n    RUN_ID_PLACEHOLDER,\n    runId,\n  ).replace(INTENT_PLACEHOLDER, FEATURE_ONBOARDING_INTENT[serviceId]);\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA6BA,MAAM,qBAAqB;AAE3B,MAAa,2BAA2B;AAExC,MAAa,6BAA6B,QAAQ,yBAAyB,sBAAsB,mBAAmB;;AAGpH,MAAM,gBAAgB;;;;;;;;;;AAWtB,SAAgB,wBAAgC;CAC9C,MAAM,YAAY,WAAW;AAE7B,KAAI,OAAO,WAAW,eAAe,WACnC,QAAO,UAAU,YAAY,CAAC,WAAW,KAAK,GAAG,CAAC,MAAM,GAAG,cAAc;AAG3E,KAAI,OAAO,WAAW,oBAAoB,YAAY;EACpD,MAAM,QAAQ,UAAU,gBAAgB,IAAI,WAAW,gBAAgB,EAAE,CAAC;AAC1E,SAAO,MAAM,KAAK,QAAQ,SAAS,KAAK,SAAS,GAAG,CAAC,SAAS,GAAG,IAAI,CAAC,CAAC,KACrE,GACD;;CAGH,IAAI,KAAK;AACT,QAAO,GAAG,SAAS,cACjB,OAAM,KAAK,MAAM,KAAK,QAAQ,GAAG,GAAG,CAAC,SAAS,GAAG;AAEnD,QAAO,GAAG,MAAM,GAAG,cAAc;;;AAInC,SAAgB,uBAAuB,OAAuB;AAC5D,QAAO,2BAA2B,QAAQ,oBAAoB,MAAM;;;;;;;;;;;;;;;;;AAyCtE,MAAa,4BAGT;CACF,SAAS;CACT,QAAQ;CACR,MAAM;CACN,eAAe;CACf,aAAa;CACb,OAAO;CACP,WAAW;CACZ;AAED,MAAM,qBAAqB;;;;;;;;;;;;;;AAe3B,MAAa,qCAAqC,QAAQ,yBAAyB,sBAAsB,mBAAmB,UAAU,mBAAmB;;AAGzJ,SAAgB,8BACd,WACA,OACQ;AACR,QAAO,mCAAmC,QACxC,oBACA,MACD,CAAC,QAAQ,oBAAoB,0BAA0B,WAAW"}

package/dist/lib/onboarding-prompt.mjs

@@ -12,12 +12,11 @@
 * The CLI resolves `onboard start` against a prompt graph, so the two surfaces
 * must not drift — if the CLI's entry point changes, both change together.
 *
-* Two lines, and deliberately nothing else. It used to open by telling the
-* agent to identify itself and pass the slug as a flag -- two sentences of
-* instruction to a machine, in the one piece of text a human reads, decides on
-* and pastes. The graph asks for the slug itself now, with `onboard identify`,
-* which is the surface that talks to the agent for the rest of the run
-* (Intelligence OSS-1157).
+* One sentence, and deliberately nothing else. It used to carry the `npx`
+* command itself, which put a command line and a telemetry id in the one piece
+* of text a human reads, decides on and pastes. The command now lives in the
+* document the URL serves, with the run id already written into it
+* (PE-216/PE-217).
 *
 * This one stays generic, and so do the docs and Intelligence web-app copies
 * of it (OSS-1150). Those three are entry points for a developer with no
@@ -28,9 +27,8 @@
 * `FEATURE_ONBOARDING_PROMPT_TEMPLATE` below.
 */
 const RUN_ID_PLACEHOLDER = "<run-id>";
-const ONBOARDING_PROMPT_TEMPLATE = `Help me get started with CopilotKit. Run this command and follow the instructions:
-
-npx --yes copilotkit@latest onboard start --run ${RUN_ID_PLACEHOLDER}`;
+const ONBOARDING_PROMPT_ORIGIN = "https://copilotkit.ai";
+const ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER} and help me get set up.`;
 /** Length and alphabet are the CLI's, so a run id copied here resolves there. */
 const RUN_ID_LENGTH = 12;
 /**
@@ -91,15 +89,11 @@ const INTENT_PLACEHOLDER = "<intent>";
 * here would duplicate all of that and then drift from it the next time the
 * underlying API changes.
 *
-* What is left is the caller's own business: identify yourself, run this
-* command, and the standing permission for the session check that the
-* developer granted by copying the prompt.
+* The session-check permission the developer granted by copying this, and the
+* credentials warning beside it, moved with the command into the document the
+* URL serves. They are not dropped.
 */
-const FEATURE_ONBOARDING_PROMPT_TEMPLATE = `Help me set this up in my CopilotKit app. Run this command and follow the instructions:
-
-npx --yes copilotkit@latest onboard start --run ${RUN_ID_PLACEHOLDER} --intent ${INTENT_PLACEHOLDER}
-
-If it requires a CopilotKit CLI session check, you have permission to run it. Never reveal credentials.`;
+const FEATURE_ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER}?intent=${INTENT_PLACEHOLDER} and help me set this up.`;
 /** Bind one run id and one tile's feature outcome into the copied prompt. */
 function createFeatureOnboardingPrompt(serviceId, runId) {
 	return FEATURE_ONBOARDING_PROMPT_TEMPLATE.replace(RUN_ID_PLACEHOLDER, runId).replace(INTENT_PLACEHOLDER, FEATURE_ONBOARDING_INTENT[serviceId]);

package/dist/lib/onboarding-prompt.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"onboarding-prompt.mjs","names":[],"sources":["../../src/lib/onboarding-prompt.ts"],"sourcesContent":["import type { HomeServiceId } from \"./home-briefing.js\";\n\n/**\n * The Intelligence install prompt the Inspector hands to a coding agent.\n *\n * Every other Intelligence call to action in the Inspector opens a page in a\n * new tab, which is where developers drop out: they leave the editor, meet a\n * signup form, and never come back. This prompt lets the install happen where\n * they already are.\n *\n * The wording is kept byte-identical to `INTELLIGENCE_ONBOARDING_PROMPT` in the\n * Intelligence app (`apps/app-frontend/react-shell/src/home/intelligence-home.tsx`).\n * The CLI resolves `onboard start` against a prompt graph, so the two surfaces\n * must not drift — if the CLI's entry point changes, both change together.\n *\n * Two lines, and deliberately nothing else. It used to open by telling the\n * agent to identify itself and pass the slug as a flag -- two sentences of\n * instruction to a machine, in the one piece of text a human reads, decides on\n * and pastes. The graph asks for the slug itself now, with `onboard identify`,\n * which is the surface that talks to the agent for the rest of the run\n * (Intelligence OSS-1157).\n *\n * This one stays generic, and so do the docs and Intelligence web-app copies\n * of it (OSS-1150). Those three are entry points for a developer with no\n * CopilotKit app yet, and every `--intent` route requires an existing app: it\n * inspects for one first and reads `feature/stop` when it is missing. The\n * feature buttons on Home are the surface that knows which feature the\n * developer is looking at, so they are the surface that names an intent — see\n * `FEATURE_ONBOARDING_PROMPT_TEMPLATE` below.\n */\nconst RUN_ID_PLACEHOLDER = \"<run-id>\";\n\nexport const ONBOARDING_PROMPT_TEMPLATE =\n  \"Help me get started with CopilotKit. Run this command and follow the \" +\n  \"instructions:\\n\\nnpx --yes copilotkit@latest onboard start --run \" +\n  `${RUN_ID_PLACEHOLDER}`;\n\n/** Length and alphabet are the CLI's, so a run id copied here resolves there. */\nconst RUN_ID_LENGTH = 12;\n\n/**\n * Mint the identifier that joins this copy to the CLI run it starts.\n *\n * The Intelligence app derives it from `crypto.randomUUID()`. The Inspector\n * runs inside whatever page embeds it, so neither `randomUUID` nor a secure\n * context is guaranteed; the two fallbacks keep the id present rather than\n * letting the button fail. Collision risk is irrelevant — this correlates\n * telemetry, it does not authorise anything.\n */\nexport function createOnboardingRunId(): string {\n  const webCrypto = globalThis.crypto;\n\n  if (typeof webCrypto?.randomUUID === \"function\") {\n    return webCrypto.randomUUID().replaceAll(\"-\", \"\").slice(0, RUN_ID_LENGTH);\n  }\n\n  if (typeof webCrypto?.getRandomValues === \"function\") {\n    const bytes = webCrypto.getRandomValues(new Uint8Array(RUN_ID_LENGTH / 2));\n    return Array.from(bytes, (byte) => byte.toString(16).padStart(2, \"0\")).join(\n      \"\",\n    );\n  }\n\n  let id = \"\";\n  while (id.length < RUN_ID_LENGTH) {\n    id += Math.floor(Math.random() * 16).toString(16);\n  }\n  return id.slice(0, RUN_ID_LENGTH);\n}\n\n/** Bind one run id into the prompt text that gets copied. */\nexport function createOnboardingPrompt(runId: string): string {\n  return ONBOARDING_PROMPT_TEMPLATE.replace(RUN_ID_PLACEHOLDER, runId);\n}\n\n/**\n * The closed set of feature outcomes the CLI prompt graph can start at.\n *\n * Kept equal to `ONBOARDING_INTENT_ROOTS` in Intelligence's\n * `apps/cli/onboarding-intents.cjs`, which is the build-time source of truth.\n * The two repositories cannot import each other, so the agreement is held by\n * this list plus the CLI's own `onboarding-intents.spec.ts`. Drift is loud\n * rather than silent: `onboard start` refuses an unknown `--intent` before it\n * persists a run, so a stale slug fails on the first command instead of\n * quietly onboarding the wrong feature.\n */\nexport const ONBOARDING_INTENTS = [\n  \"add-a2ui\",\n  \"add-chat-suggestions\",\n  \"add-learning\",\n  \"add-open-generative-ui\",\n  \"add-realtime-sync\",\n  \"add-rich-threads\",\n  \"add-voice\",\n] as const;\n\nexport type OnboardingIntent = (typeof ONBOARDING_INTENTS)[number];\n\n/**\n * Which feature outcome each Home tile asks the CLI for.\n *\n * The two vocabularies stay separate on purpose. A `HomeServiceId` names a\n * tile and the pane behind it, so `websocket` and `audio` are the right words\n * for it; an intent names the work to be done, so `add-realtime-sync` and\n * `add-voice` are the right words for that. One table maps between them, and\n * `Record<HomeServiceId, OnboardingIntent>` makes a new tile or a renamed\n * slug a type error rather than a missing button.\n *\n * `memory` maps to `add-learning` because the tile is the Learning tile: it is\n * enabled by a *configured Learning container* (see `learningOn` in\n * `index.ts`), which is exactly what `feature/learning` sets up. The tile id\n * and the `memories` menu key are older names for that same pane.\n */\nexport const FEATURE_ONBOARDING_INTENT: Record<\n  HomeServiceId,\n  OnboardingIntent\n> = {\n  threads: \"add-rich-threads\",\n  memory: \"add-learning\",\n  a2ui: \"add-a2ui\",\n  \"open-gen-ui\": \"add-open-generative-ui\",\n  suggestions: \"add-chat-suggestions\",\n  audio: \"add-voice\",\n  websocket: \"add-realtime-sync\",\n};\n\nconst INTENT_PLACEHOLDER = \"<intent>\";\n\n/**\n * The prompt a Home feature button copies.\n *\n * It carries no feature-specific instruction, and it must not gain any. The\n * `--intent` route owns the plan, the guide links, the per-phase check-ins,\n * the refusal when a prerequisite is missing, and the proof step; prose copied\n * here would duplicate all of that and then drift from it the next time the\n * underlying API changes.\n *\n * What is left is the caller's own business: identify yourself, run this\n * command, and the standing permission for the session check that the\n * developer granted by copying the prompt.\n */\nexport const FEATURE_ONBOARDING_PROMPT_TEMPLATE =\n  \"Help me set this up in my CopilotKit app. Run this command and follow the \" +\n  \"instructions:\\n\\nnpx --yes copilotkit@latest onboard start --run \" +\n  `${RUN_ID_PLACEHOLDER} --intent ${INTENT_PLACEHOLDER}` +\n  \"\\n\\nIf it requires a CopilotKit CLI session check, you have permission to \" +\n  \"run it. Never reveal credentials.\";\n\n/** Bind one run id and one tile's feature outcome into the copied prompt. */\nexport function createFeatureOnboardingPrompt(\n  serviceId: HomeServiceId,\n  runId: string,\n): string {\n  return FEATURE_ONBOARDING_PROMPT_TEMPLATE.replace(\n    RUN_ID_PLACEHOLDER,\n    runId,\n  ).replace(INTENT_PLACEHOLDER, FEATURE_ONBOARDING_INTENT[serviceId]);\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA8BA,MAAM,qBAAqB;AAE3B,MAAa,6BACX;;kDAEG;;AAGL,MAAM,gBAAgB;;;;;;;;;;AAWtB,SAAgB,wBAAgC;CAC9C,MAAM,YAAY,WAAW;AAE7B,KAAI,OAAO,WAAW,eAAe,WACnC,QAAO,UAAU,YAAY,CAAC,WAAW,KAAK,GAAG,CAAC,MAAM,GAAG,cAAc;AAG3E,KAAI,OAAO,WAAW,oBAAoB,YAAY;EACpD,MAAM,QAAQ,UAAU,gBAAgB,IAAI,WAAW,gBAAgB,EAAE,CAAC;AAC1E,SAAO,MAAM,KAAK,QAAQ,SAAS,KAAK,SAAS,GAAG,CAAC,SAAS,GAAG,IAAI,CAAC,CAAC,KACrE,GACD;;CAGH,IAAI,KAAK;AACT,QAAO,GAAG,SAAS,cACjB,OAAM,KAAK,MAAM,KAAK,QAAQ,GAAG,GAAG,CAAC,SAAS,GAAG;AAEnD,QAAO,GAAG,MAAM,GAAG,cAAc;;;AAInC,SAAgB,uBAAuB,OAAuB;AAC5D,QAAO,2BAA2B,QAAQ,oBAAoB,MAAM;;;;;;;;;;;;;;;;;AAyCtE,MAAa,4BAGT;CACF,SAAS;CACT,QAAQ;CACR,MAAM;CACN,eAAe;CACf,aAAa;CACb,OAAO;CACP,WAAW;CACZ;AAED,MAAM,qBAAqB;;;;;;;;;;;;;;AAe3B,MAAa,qCACX;;kDAEG,mBAAmB,YAAY;;;;AAKpC,SAAgB,8BACd,WACA,OACQ;AACR,QAAO,mCAAmC,QACxC,oBACA,MACD,CAAC,QAAQ,oBAAoB,0BAA0B,WAAW"}
+{"version":3,"file":"onboarding-prompt.mjs","names":[],"sources":["../../src/lib/onboarding-prompt.ts"],"sourcesContent":["import type { HomeServiceId } from \"./home-briefing.js\";\n\n/**\n * The Intelligence install prompt the Inspector hands to a coding agent.\n *\n * Every other Intelligence call to action in the Inspector opens a page in a\n * new tab, which is where developers drop out: they leave the editor, meet a\n * signup form, and never come back. This prompt lets the install happen where\n * they already are.\n *\n * The wording is kept byte-identical to `INTELLIGENCE_ONBOARDING_PROMPT` in the\n * Intelligence app (`apps/app-frontend/react-shell/src/home/intelligence-home.tsx`).\n * The CLI resolves `onboard start` against a prompt graph, so the two surfaces\n * must not drift — if the CLI's entry point changes, both change together.\n *\n * One sentence, and deliberately nothing else. It used to carry the `npx`\n * command itself, which put a command line and a telemetry id in the one piece\n * of text a human reads, decides on and pastes. The command now lives in the\n * document the URL serves, with the run id already written into it\n * (PE-216/PE-217).\n *\n * This one stays generic, and so do the docs and Intelligence web-app copies\n * of it (OSS-1150). Those three are entry points for a developer with no\n * CopilotKit app yet, and every `--intent` route requires an existing app: it\n * inspects for one first and reads `feature/stop` when it is missing. The\n * feature buttons on Home are the surface that knows which feature the\n * developer is looking at, so they are the surface that names an intent — see\n * `FEATURE_ONBOARDING_PROMPT_TEMPLATE` below.\n */\nconst RUN_ID_PLACEHOLDER = \"<run-id>\";\n\nexport const ONBOARDING_PROMPT_ORIGIN = \"https://copilotkit.ai\";\n\nexport const ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER} and help me get set up.`;\n\n/** Length and alphabet are the CLI's, so a run id copied here resolves there. */\nconst RUN_ID_LENGTH = 12;\n\n/**\n * Mint the identifier that joins this copy to the CLI run it starts.\n *\n * The Intelligence app derives it from `crypto.randomUUID()`. The Inspector\n * runs inside whatever page embeds it, so neither `randomUUID` nor a secure\n * context is guaranteed; the two fallbacks keep the id present rather than\n * letting the button fail. Collision risk is irrelevant — this correlates\n * telemetry, it does not authorise anything.\n */\nexport function createOnboardingRunId(): string {\n  const webCrypto = globalThis.crypto;\n\n  if (typeof webCrypto?.randomUUID === \"function\") {\n    return webCrypto.randomUUID().replaceAll(\"-\", \"\").slice(0, RUN_ID_LENGTH);\n  }\n\n  if (typeof webCrypto?.getRandomValues === \"function\") {\n    const bytes = webCrypto.getRandomValues(new Uint8Array(RUN_ID_LENGTH / 2));\n    return Array.from(bytes, (byte) => byte.toString(16).padStart(2, \"0\")).join(\n      \"\",\n    );\n  }\n\n  let id = \"\";\n  while (id.length < RUN_ID_LENGTH) {\n    id += Math.floor(Math.random() * 16).toString(16);\n  }\n  return id.slice(0, RUN_ID_LENGTH);\n}\n\n/** Bind one run id into the prompt text that gets copied. */\nexport function createOnboardingPrompt(runId: string): string {\n  return ONBOARDING_PROMPT_TEMPLATE.replace(RUN_ID_PLACEHOLDER, runId);\n}\n\n/**\n * The closed set of feature outcomes the CLI prompt graph can start at.\n *\n * Kept equal to `ONBOARDING_INTENT_ROOTS` in Intelligence's\n * `apps/cli/onboarding-intents.cjs`, which is the build-time source of truth.\n * The two repositories cannot import each other, so the agreement is held by\n * this list plus the CLI's own `onboarding-intents.spec.ts`. Drift is loud\n * rather than silent: `onboard start` refuses an unknown `--intent` before it\n * persists a run, so a stale slug fails on the first command instead of\n * quietly onboarding the wrong feature.\n */\nexport const ONBOARDING_INTENTS = [\n  \"add-a2ui\",\n  \"add-chat-suggestions\",\n  \"add-learning\",\n  \"add-open-generative-ui\",\n  \"add-realtime-sync\",\n  \"add-rich-threads\",\n  \"add-voice\",\n] as const;\n\nexport type OnboardingIntent = (typeof ONBOARDING_INTENTS)[number];\n\n/**\n * Which feature outcome each Home tile asks the CLI for.\n *\n * The two vocabularies stay separate on purpose. A `HomeServiceId` names a\n * tile and the pane behind it, so `websocket` and `audio` are the right words\n * for it; an intent names the work to be done, so `add-realtime-sync` and\n * `add-voice` are the right words for that. One table maps between them, and\n * `Record<HomeServiceId, OnboardingIntent>` makes a new tile or a renamed\n * slug a type error rather than a missing button.\n *\n * `memory` maps to `add-learning` because the tile is the Learning tile: it is\n * enabled by a *configured Learning container* (see `learningOn` in\n * `index.ts`), which is exactly what `feature/learning` sets up. The tile id\n * and the `memories` menu key are older names for that same pane.\n */\nexport const FEATURE_ONBOARDING_INTENT: Record<\n  HomeServiceId,\n  OnboardingIntent\n> = {\n  threads: \"add-rich-threads\",\n  memory: \"add-learning\",\n  a2ui: \"add-a2ui\",\n  \"open-gen-ui\": \"add-open-generative-ui\",\n  suggestions: \"add-chat-suggestions\",\n  audio: \"add-voice\",\n  websocket: \"add-realtime-sync\",\n};\n\nconst INTENT_PLACEHOLDER = \"<intent>\";\n\n/**\n * The prompt a Home feature button copies.\n *\n * It carries no feature-specific instruction, and it must not gain any. The\n * `--intent` route owns the plan, the guide links, the per-phase check-ins,\n * the refusal when a prerequisite is missing, and the proof step; prose copied\n * here would duplicate all of that and then drift from it the next time the\n * underlying API changes.\n *\n * The session-check permission the developer granted by copying this, and the\n * credentials warning beside it, moved with the command into the document the\n * URL serves. They are not dropped.\n */\nexport const FEATURE_ONBOARDING_PROMPT_TEMPLATE = `Read ${ONBOARDING_PROMPT_ORIGIN}/onboarding-prompts/${RUN_ID_PLACEHOLDER}?intent=${INTENT_PLACEHOLDER} and help me set this up.`;\n\n/** Bind one run id and one tile's feature outcome into the copied prompt. */\nexport function createFeatureOnboardingPrompt(\n  serviceId: HomeServiceId,\n  runId: string,\n): string {\n  return FEATURE_ONBOARDING_PROMPT_TEMPLATE.replace(\n    RUN_ID_PLACEHOLDER,\n    runId,\n  ).replace(INTENT_PLACEHOLDER, FEATURE_ONBOARDING_INTENT[serviceId]);\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;AA6BA,MAAM,qBAAqB;AAE3B,MAAa,2BAA2B;AAExC,MAAa,6BAA6B,QAAQ,yBAAyB,sBAAsB,mBAAmB;;AAGpH,MAAM,gBAAgB;;;;;;;;;;AAWtB,SAAgB,wBAAgC;CAC9C,MAAM,YAAY,WAAW;AAE7B,KAAI,OAAO,WAAW,eAAe,WACnC,QAAO,UAAU,YAAY,CAAC,WAAW,KAAK,GAAG,CAAC,MAAM,GAAG,cAAc;AAG3E,KAAI,OAAO,WAAW,oBAAoB,YAAY;EACpD,MAAM,QAAQ,UAAU,gBAAgB,IAAI,WAAW,gBAAgB,EAAE,CAAC;AAC1E,SAAO,MAAM,KAAK,QAAQ,SAAS,KAAK,SAAS,GAAG,CAAC,SAAS,GAAG,IAAI,CAAC,CAAC,KACrE,GACD;;CAGH,IAAI,KAAK;AACT,QAAO,GAAG,SAAS,cACjB,OAAM,KAAK,MAAM,KAAK,QAAQ,GAAG,GAAG,CAAC,SAAS,GAAG;AAEnD,QAAO,GAAG,MAAM,GAAG,cAAc;;;AAInC,SAAgB,uBAAuB,OAAuB;AAC5D,QAAO,2BAA2B,QAAQ,oBAAoB,MAAM;;;;;;;;;;;;;;;;;AAyCtE,MAAa,4BAGT;CACF,SAAS;CACT,QAAQ;CACR,MAAM;CACN,eAAe;CACf,aAAa;CACb,OAAO;CACP,WAAW;CACZ;AAED,MAAM,qBAAqB;;;;;;;;;;;;;;AAe3B,MAAa,qCAAqC,QAAQ,yBAAyB,sBAAsB,mBAAmB,UAAU,mBAAmB;;AAGzJ,SAAgB,8BACd,WACA,OACQ;AACR,QAAO,mCAAmC,QACxC,oBACA,MACD,CAAC,QAAQ,oBAAoB,0BAA0B,WAAW"}

package/dist/package.cjs

@@ -1,6 +1,6 @@
 
 //#region package.json
-var version = "1.73.2-canary.1790085728";
+var version = "1.73.3";
 
 //#endregion
 Object.defineProperty(exports, 'version', {

package/dist/package.mjs

@@ -1,5 +1,5 @@
 //#region package.json
-var version = "1.73.2-canary.1790085728";
+var version = "1.73.3";
 
 //#endregion
 export { version };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@copilotkit/web-inspector",
-  "version": "1.73.2-canary.1790085728",
+  "version": "1.73.3",
   "description": "Lit-based web component for the CopilotKit web inspector",
   "license": "MIT",
   "repository": {
@@ -28,11 +28,11 @@
   },
   "dependencies": {
     "@ag-ui/client": "0.0.59",
-    "@copilotkit/core": "1.73.2-canary.1790085728",
-    "@copilotkit/shared": "1.73.2-canary.1790085728",
     "lit": "^3.2.0",
     "lucide": "^0.525.0",
-    "marked": "^12.0.2"
+    "marked": "^12.0.2",
+    "@copilotkit/core": "1.73.3",
+    "@copilotkit/shared": "1.73.3"
   },
   "devDependencies": {
     "@playwright/test": "^1.59.1",