replicas-cli 0.2.190 → 0.2.191

package/dist/index.mjs

@@ -8494,8 +8494,8 @@ gh pr review 123 --request-changes --body "Changes needed"
 GitHub does NOT have a public API for uploading images to PRs/issues. When you need to include images:
 - Do NOT use placeholder image URLs
 - Do NOT commit screenshots as files to the repository
-- Upload images to Imgur (or another external host) and use the returned URLs in your PR markdown
-- If you were triggered from Slack, also upload the images to the Slack thread so the user can see them directly
+- Use the \`replicas-agent\` skill to share the image
+- If you were triggered from Slack, also upload the image to the Slack thread so the user can see it directly
 `;
 var GITHUB_ABILITY = {
   label: "GitHub",
@@ -8943,10 +8943,9 @@ After (or alongside) the embeds, include a \`[View in Replicas](<deep-link>)\` h
 
 ### On external platforms (Slack, Linear, GitHub, etc.)
 
-Do **both** of these \u2014 neither alone is sufficient:
+Always include a \`[View in Replicas](<deep-link>)\` hyperlink \u2014 use the per-file deep link the CLI printed for that file (\`...?mode=media&media=<media-id>\`), so the recipient lands directly on that specific item.
 
-1. Upload the raw bytes via that platform's own upload API (Slack \`files.upload\`, Linear attachments, Imgur for GitHub PR/issue images, etc.) so the recipient actually sees the media.
-2. Include a \`[View in Replicas](<deep-link>)\` hyperlink \u2014 use the per-file deep link the CLI printed for that file (\`...?mode=media&media=<media-id>\`), so the recipient lands directly on that specific item.
+For platforms that support native uploads (Slack \`files.upload\`, Linear attachments, etc.), upload the raw bytes there too so the recipient sees the media inline in addition to the Replicas link. GitHub PRs/issues do not have a public upload API, so the \`View in Replicas\` link is the canonical way to share media there \u2014 do not commit screenshots to the repo and do not use placeholder URLs.
 
 Do **not** include the \`![filename](https://api.tryreplicas.com/...)\` markdown embed in external messages. It will render as a broken image / 401 for the recipient.
 
@@ -8992,7 +8991,7 @@ replicas media upload chart-a.svg chart-b.svg --kind image
 var MEDIA_ABILITY = {
   label: "Media",
   description: "Share screenshots, recordings, generated images, and audio clips.",
-  bullet: "- Sharing media (screenshots, screen recordings, generated diagrams, audio clips) \u2014 including in your Replicas chat reply and to external platforms",
+  bullet: "- Producing or showing the user any media \u2014 screenshots, screen recordings, generated images or diagrams, audio clips \u2014 including in your Replicas chat reply, PR descriptions/comments, and other external platforms",
   section: SECTION6,
   referenceFile: { name: "MEDIA.md", content: REFERENCE6 }
 };
@@ -16602,7 +16601,7 @@ Deleted file ${pathOrId}.
 }
 
 // src/index.ts
-var CLI_VERSION = "0.2.190";
+var CLI_VERSION = "0.2.191";
 function parseBooleanOption(value) {
   if (value === "true") return true;
   if (value === "false") return false;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replicas-cli",
-  "version": "0.2.190",
+  "version": "0.2.191",
   "description": "CLI for managing Replicas workspaces - SSH into cloud dev environments with automatic port forwarding",
   "main": "dist/index.mjs",
   "bin": {