wtt-connect 0.2.34 → 0.2.35

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wtt-connect",
-  "version": "0.2.34",
+  "version": "0.2.35",
   "private": false,
   "description": "WTT-native connector daemon for Codex, Claude Code, Cursor, Gemini, ACP, and other coding agent surfaces.",
   "type": "module",

package/src/runner.js

@@ -937,7 +937,8 @@ function renderCloudSandboxStorageInstruction(config, topicId = '') {
     '- Do not install large dependencies, clone large repositories, download datasets, or write bulky generated files into the workspace unless the user explicitly asks for local temporary storage.',
     '- Keep only source edits, small manifests, notes, and temporary scratch files in the workspace.',
     '- If a generated user-facing file is stored in R2/persistent output storage and should appear in WTT chat, still publish it with `wtt-connect upload-file` or a WTT artifact marker.',
-    `- If you start a web server in the sandbox and the user should preview it, expose that port with: wtt-connect preview-port --port <port>${topicId ? ` --topic-id ${topicId}` : ' --topic-id <topic_id>'}. This calls the Cloudflare Sandbox outbound Worker directly to create a preview URL and does not use WTT backend preview or legacy artifact/media preview flows.`,
+    `- If you start a web server in the sandbox and the user should preview it, expose that port with: wtt-preview-port <port>. This command calls the Cloudflare Sandbox outbound Worker directly and prints a public preview URL; include that URL in your reply.`,
+    `- Only if you need WTT to publish the preview card automatically, use: wtt-connect preview-port --port <port>${topicId ? ` --topic-id ${topicId}` : ' --topic-id <topic_id>'}. This is a convenience wrapper around the same sandbox outbound Worker, not a backend preview API.`,
   );
   return lines.join('\n');
 }