replicas-cli 0.2.789 → 0.2.791

package/dist/index.cjs

@@ -22950,7 +22950,6 @@ var sendChatMessageRequestSchema = external_exports.object({
   idempotencyKey: external_exports.string().min(1).max(128).optional(),
   automationId: external_exports.string().optional(),
   environmentId: external_exports.string().min(1).optional(),
-  chatCredentials: external_exports.boolean().optional(),
   senderUserId: external_exports.string().optional(),
   senderEmail: external_exports.string().optional(),
   senderDisplayName: external_exports.string().optional(),
@@ -24163,7 +24162,7 @@ replicas computer record stop
 replicas media upload /tmp/walkthrough.mp4 --name "<Project> walkthrough"
 \`\`\`
 
-Keep the recording short (one to three minutes) and focused on the flow that proves the environment works. \`replicas media upload\` prints a chat embed line and a \`View in Replicas\` link ending in \`?media=<media-id>\`; keep both. The media id goes into the proposal, and the embed line goes into your final message. Follow \`MEDIA.md\` for anything shared outside the dashboard.
+Keep the recording short (one to three minutes) and focused on the flow that proves the environment works. \`replicas media upload\` prints a chat embed line and a \`View in Replicas\` link ending in \`?mode=media&media=<media-id>\`; keep both. The media id goes into the proposal, and the embed line goes into your final message. Follow \`MEDIA.md\` for anything shared outside the dashboard.
 
 Add screenshots of important states (a passing test run, the running app) with \`replicas computer screenshot\` and upload them the same way when they help the user trust the result.
 
@@ -24687,7 +24686,7 @@ For each media file, the CLI prints an embed line and a dashboard link:
 
 1. Images always print \`![filename](<public-url>)\`. This public, stable link works in Replicas chat, GitHub, and anywhere else Markdown images render. No flag is needed.
 2. Video and audio print \`Replicas chat embed: ![filename](<api-url>)\` by default; this authenticated URL renders inline in Replicas chat **only** \u2014 see below. \`--access public\` prints a public embed instead.
-3. \`View in Replicas: <deep-link>\` is a per-file dashboard URL of the form \`https://app.replicas.dev/workspaces/<workspace-id>?media=<media-id>\` that opens directly to that specific file.
+3. \`View in Replicas: <deep-link>\` is a per-file dashboard URL of the form \`https://app.replicas.dev/workspaces/<workspace-id>?mode=media&media=<media-id>\` that opens directly to that specific file.
 
 Match each "View in Replicas" line to the embed line directly above it \u2014 that's the deep link for that file.
 
@@ -24718,7 +24717,7 @@ Permanently delete an upload with \`replicas media delete <media-id>\`. The back
 | \`https://api.replicas.dev/v1/media/<id>\` (inside \`![\u2026](\u2026)\`) | Authenticated API redirect printed for private video, audio, and HTML \u2014 requires the Replicas chat session | **Only** in the Replicas chat reply. Nowhere else. |
 | \`https://replicas.dev/organizations/<organization-id>/media/<media-id>\` | Organization-only page printed by \`--access organization\` | Pull requests and other places where every viewer belongs to the Replicas organization. |
 | \`https://api.replicas.dev/v1/media/public/<id>/<token>\` | Public bearer URL printed for every image, and for video or audio with \`--access public\` | The Replicas chat reply and GitHub embeds. |
-| \`https://app.replicas.dev/workspaces/<workspace-id>?media=<media-id>\` | Authenticated dashboard deep link that opens the media file in the workspace | Everywhere external: Slack, GitHub, GitLab, Linear, PR bodies, comments, emails. |
+| \`https://app.replicas.dev/workspaces/<workspace-id>?mode=media&media=<media-id>\` | Authenticated dashboard deep link that opens the media file in the workspace | Everywhere external: Slack, GitHub, GitLab, Linear, PR bodies, comments, emails. |
 
 ### NEVER link the API redirect URL outside the Replicas chat reply
 
@@ -24737,10 +24736,10 @@ This rule has no exceptions:
 For an organization-only HTML page, use the \`Forge link\` printed by \`--access organization\`. For other authenticated media references, use the dashboard form:
 
 \`\`\`
-https://app.replicas.dev/workspaces/<workspace-id>?media=<media-id>
+https://app.replicas.dev/workspaces/<workspace-id>?mode=media&media=<media-id>
 \`\`\`
 
-The \`media=<media-id>\` query param opens that specific file in the workspace.
+The \`mode=media&media=<media-id>\` query params open that specific file in the workspace.
 
 When you have a specific file in mind, never link the bare workspace URL without the \`media=<id>\` param.
 
@@ -24750,6 +24749,8 @@ Always render as a markdown / mrkdwn hyperlink labeled **View in Replicas** \u20
 
 Include each markdown embed line **verbatim** where you want that file to render inline. The chat substitutes each one with an embedded image, video, or audio player. For HTML, use the printed \`HTML page\` link. Multiple embeds can appear in a single reply.
 
+Never reply with only dashboard links (for example a "Links:" list of \`?mode=media&media=\` URLs) in place of the embeds: a dashboard link renders as plain text, so the user sees nothing inline. This applies even when the task came from Slack, Linear, GitHub, or GitLab; the chat reply still gets the embeds.
+
 After (or alongside) the embeds, include a \`[View in Canvas](<deep-link>)\` hyperlink for each file using the per-file dashboard URL printed by the CLI as **View in Replicas**. Keep that URL unchanged so it opens the specific media item in the workspace's Canvas. External messages still label this dashboard link **View in Replicas**.
 
 ## On external platforms: embed the file AND link the dashboard
@@ -24757,7 +24758,7 @@ After (or alongside) the embeds, include a \`[View in Canvas](<deep-link>)\` hyp
 After \`replicas media upload\` succeeds, external delivery has two required follow-up steps for every file:
 
 1. **Use the destination's inline representation:** upload the raw bytes to Slack, Linear, or GitLab; embed the image's printed public link on GitHub.
-2. **Link the Replicas dashboard deep link** (\`?media=<id>\` form) so the user can jump straight to the file in the workspace.
+2. **Link the Replicas dashboard deep link** (\`?mode=media&media=<id>\` form) so the user can jump straight to the file in the workspace.
 
 A dashboard link alone is not enough. An embed without the dashboard link is not enough. Do both.
 
@@ -24786,7 +24787,7 @@ await replicas.slack.call('files.completeUploadExternal', {
   files: [{ id: reservation.file_id, title: 'Screenshot' }],
   channel_id: 'CHANNEL_ID',
   thread_ts: 'THREAD_TS',
-  initial_comment: '<https://app.replicas.dev/workspaces/<workspace-id>?media=<media-id>|View in Replicas>',
+  initial_comment: '<https://app.replicas.dev/workspaces/<workspace-id>?mode=media&media=<media-id>|View in Replicas>',
 });
 \`\`\`
 
@@ -24809,7 +24810,7 @@ Use \`jq\` to build the JSON bodies \u2014 the GraphQL variables (\`size\`, \`fi
 FILE=/abs/path/to/screenshot.png
 FILENAME=$(basename "$FILE")
 SIZE=$(stat -c%s "$FILE" 2>/dev/null || stat -f%z "$FILE")
-CONTENT_TYPE=image/png
+CONTENT_TYPE=image/png   # the file's real MIME type, e.g. video/mp4 for a recording
 ISSUE_UUID=...           # the Linear issue's UUID
 MEDIA_ID=...             # the media ID printed by \`replicas media upload\`
 
@@ -24846,7 +24847,7 @@ curl -s -X PUT "$UPLOAD_URL" \\
   --data-binary @"$FILE"
 
 # 3. Reference assetUrl inline in the comment body, alongside the dashboard link.
-BODY=$(printf '![screenshot](%s)\\n\\n[View in Replicas](https://app.replicas.dev/workspaces/%s?media=%s)' \\
+BODY=$(printf '![screenshot](%s)\\n\\n[View in Replicas](https://app.replicas.dev/workspaces/%s?mode=media&media=%s)' \\
   "$ASSET_URL" "$REPLICAS_WORKSPACE_ID" "$MEDIA_ID")
 
 jq -n \\
@@ -24858,6 +24859,8 @@ jq -n \\
     }' | linear_graphql
 \`\`\`
 
+For a recording, upload the MP4 with its own MIME type, then upload a poster frame (\`ffmpeg -i /tmp/demo.mp4 -frames:v 1 /tmp/demo-poster.png\`) the same way as \`image/png\` and link it: \`[![Demo recording](<poster-asset-url>)](<recording-asset-url>)\`.
+
 The same flow works for issue bodies (use \`issueCreate\` / \`issueUpdate\` with the same markdown body).
 
 Never paste the \`api.replicas.dev/v1/media/<id>\` URL into a Linear body or comment \u2014 it will render as a broken image to anyone outside your Replicas chat.
@@ -24897,7 +24900,7 @@ Do **not** commit screenshots to the repo, use placeholder URLs, expose the auth
 
 GitLab supports native project Markdown uploads. For a GitLab destination, always upload the media to Replicas first, then POST the same original file to the repository's \`/projects/:id/uploads\` API using the workspace GitLab credential. Insert the returned \`markdown\` value into the merge request body or comment and include the Replicas dashboard link. Image uploads render inline; MP4, MOV, and WebM uploads render as inline video players.
 
-Do not use a Replicas public link for GitLab when the native project upload succeeds; native uploads preserve project access controls.
+Do not use a Replicas public link for GitLab when the native project upload succeeds; native uploads preserve project access controls. \`replicas.gitlab.request\` only sends JSON and cannot POST multipart file bytes, so without another supported upload path use the GitHub flow above instead: the image's printed public embed, and a poster linked to the recording's **View in Replicas** URL.
 
 ## Recording defaults
 
@@ -24945,7 +24948,7 @@ replicas media upload chart-a.svg chart-b.svg --name "Latency chart" --name "Err
 var MEDIA_ABILITY = {
   label: "Media",
   description: "Deliver media to Replicas and destination workflows with inline uploads.",
-  bullet: "- Producing or showing the user any media \u2014 screenshots, screen recordings, generated images or diagrams, audio clips, or HTML recap pages \u2014 including in your Replicas chat reply, PR descriptions/comments, and other external platforms",
+  bullet: "- Producing or showing the user any media \u2014 screenshots, screen recordings, generated images or diagrams, audio clips, or HTML recap pages \u2014 including in your Replicas chat reply, PR descriptions/comments, and other external platforms. Paste the printed `![\u2026](\u2026)` embeds in your chat reply, never only dashboard links, and upload the file itself to Slack, Linear, or GitLab",
   section: SECTION7,
   referenceFile: { name: "MEDIA.md", content: REFERENCE7 }
 };
@@ -27986,7 +27989,7 @@ var headlessAgentRequestSchema = external_exports.object({
 });
 
 // ../shared/src/cli-version.ts
-var CLI_VERSION = "0.2.789";
+var CLI_VERSION = "0.2.791";
 
 // ../shared/src/version.ts
 function compareVersions(v1, v2) {
@@ -32390,6 +32393,7 @@ var MEDIA_ACCESS_VALUES = ["organization", "public"];
 function publicMediaUrl(mediaId, token) {
   return `${MONOLITH_URL}/v1/media/public/${mediaId}/${token}`;
 }
+var MEDIA_DELIVERY_HINT = "Next: paste each ![\u2026](\u2026) or HTML page line above verbatim into your Replicas chat reply so it renders inline; View in Replicas links are secondary and never replace it. Slack, Linear, and GitLab also need a native upload of the file bytes; see the replicas-agent skill's references/MEDIA.md.";
 function formatMediaEmbed(fileName, mediaId, publicUrl) {
   if (publicUrl) return `![${fileName}](${publicUrl})`;
   return `Replicas chat embed: ![${fileName}](${MONOLITH_URL}/v1/media/${mediaId})`;
@@ -32491,6 +32495,7 @@ async function mediaUploadCommand(filePaths, options) {
   );
   const config3 = readAgentConfig();
   const failures = [];
+  let printedEmbed = false;
   for (let i = 0; i < results.length; i++) {
     const result = results[i];
     if (result.status === "fulfilled") {
@@ -32511,8 +32516,10 @@ async function mediaUploadCommand(filePaths, options) {
       }
       if (media.kind === MEDIA_KIND.HTML) {
         console.log(`HTML page: [${fileName}](${MONOLITH_URL}/v1/media/${media.id})`);
+        printedEmbed = true;
       } else if (!shared[i] || publicUrl) {
         console.log(formatMediaEmbed(fileName, media.id, publicUrl));
+        printedEmbed = true;
       }
       if (options.access === "organization" && !shared[i]) {
         console.log(
@@ -32531,6 +32538,10 @@ async function mediaUploadCommand(filePaths, options) {
       failures.push({ filePath: filePaths[i], operation: "upload", error: error51 });
     }
   }
+  if (printedEmbed) {
+    console.log(`
+${MEDIA_DELIVERY_HINT}`);
+  }
   if (failures.length > 0) {
     const detail = failures.map((f) => `${f.filePath} ${f.operation}: ${f.error.message}`).join("; ");
     throw new Error(`${failures.length} media operation(s) failed \u2014 ${detail}`);

package/package.json

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