replicas-cli 0.2.672 → 0.2.674

package/dist/index.cjs

@@ -22818,12 +22818,20 @@ function coerceAuthFallbackPayload(payload) {
 
 // ../shared/src/engine/v1.ts
 var CHAT_STREAM_RESYNC_EVENT_TYPE = "chat.stream.resync";
+var CHAT_STREAM_READY_EVENT_TYPE = "chat.stream.ready";
+var chatEventSubscriptionsSchema = external_exports.object({
+  chats: external_exports.array(external_exports.object({
+    workspaceId: external_exports.string().uuid(),
+    chatId: external_exports.string().min(1).max(256),
+    after: external_exports.string().regex(/^\d+-\d+$/)
+  })).min(1).max(256)
+});
 function isChatStreamEvent(value) {
   return isRecord(value) && typeof value.id === "string" && typeof value.ts === "string" && typeof value.type === "string" && value.type.startsWith("chat.") && isRecord(value.payload);
 }
 var ENGINE_CHAT_EVENTS_PUSH_MAX_EVENTS = 500;
 var chatScopedEngineEventSchema = external_exports.custom(
-  (value) => isChatStreamEvent(value) && value.type !== CHAT_STREAM_RESYNC_EVENT_TYPE
+  (value) => isChatStreamEvent(value) && value.type !== CHAT_STREAM_RESYNC_EVENT_TYPE && value.type !== CHAT_STREAM_READY_EVENT_TYPE
 );
 var engineChatEventsPushRequestSchema = external_exports.object({
   epoch: external_exports.string().min(1).max(64),
@@ -23576,7 +23584,7 @@ gh pr review 123 --request-changes --body "Changes needed"
 
 ## Media in GitHub workflows
 
-Media delivery is owned by \`references/MEDIA.md\`. Read its GitHub section before adding screenshots, recordings, diagrams, or HTML reports to a pull request, issue, review comment, or commit; it covers the Replicas upload, GitHub's inline fallback, and the required **View in Replicas** link.
+Media delivery is owned by \`references/MEDIA.md\`. Read its GitHub section before adding screenshots, recordings, diagrams, or HTML reports to a pull request, issue, review comment, or commit; it covers public Forge embeds for images and recording previews, organization-only HTML links, and the required **View in Replicas** link.
 `;
 var GITHUB_ABILITY = {
   label: "GitHub",
@@ -23779,7 +23787,7 @@ Upload to Replicas in these cases \u2014 and **only** these cases:
 
 1. **Media you produce.** Any screenshot, screen recording, generated diagram, audio clip, or HTML page you create that the user might want to see. Upload before doing anything else with the file (analyzing, deleting, sending elsewhere). This applies even when you're also sending the file to Slack, Linear, GitHub, or GitLab.
 2. **Files the user explicitly asks you to upload.** If the user sends or points at a file (image, video, audio, HTML) and asks you to upload it, run \`replicas media upload\`. Otherwise leave it alone \u2014 files in the workspace the user did not ask about should not be auto-uploaded as media.
-3. **Anything you plan to share externally (Slack, Linear, GitHub, GitLab, etc.).** Upload to Replicas *in addition to* the platform's destination upload. Never as a replacement.
+3. **Anything you plan to share externally (Slack, Linear, GitHub, GitLab, etc.).** Upload to Replicas first, then follow the destination's delivery path below.
 
 If none of these apply, don't upload.
 
@@ -23789,9 +23797,9 @@ If none of these apply, don't upload.
 
 1. First, run \`replicas media upload\` with the original file. Do not begin any destination upload until the command succeeds. This creates the canonical dashboard copy and prints a chat embed plus a per-file dashboard link. With public access, the printed Forge embed is the chat embed and is also safe to use on GitHub.
 2. Include the printed embed line in the Replicas chat reply, followed by the matching **View in Replicas** link. HTML uses its printed page link instead of an image embed.
-3. Identify every destination in the task and attempt to upload the same original bytes there. Use the destination's inline representation from the table below; do not replace the file with a Replicas link.
+3. Identify every destination in the task and use its inline representation from the table below. Slack, Linear, and GitLab require an upload of the same original bytes; GitHub uses the public Forge embed.
 4. Put the **View in Replicas** dashboard link next to the destination embed as a secondary link.
-5. Check each destination response. If a native upload is unavailable or fails, say so explicitly and keep the dashboard link; never claim that a link is an inline upload.
+5. Check each destination response. If its upload or Forge share fails, say so explicitly and keep the dashboard link; never claim that a dashboard link is an inline embed.
 
 | Destination | Required file delivery | Inline result |
 |---|---|---|
@@ -23799,9 +23807,9 @@ If none of these apply, don't upload.
 | Slack | \`files.getUploadURLExternal\` \u2192 raw-byte POST \u2192 \`files.completeUploadExternal\` | Uploaded file in the channel or thread |
 | Linear | \`fileUpload\` mutation \u2192 presigned upload \u2192 issue/comment mutation | Returned \`assetUrl\` in Markdown |
 | GitLab | Project \`/uploads\` endpoint with the original bytes | Returned GitLab Markdown |
-| GitHub | \`gh\` v2.99.0+ \`--attach\` for images and videos; use a Replicas public forge share as the fallback | Native GitHub attachment URL, or a Forge embed fallback |
+| GitHub | Replicas public Forge share for an image or recording poster | Printed Forge embed, linked to the recording when needed |
 
-The dashboard link is the subtitle and jump-back path. It is never a substitute for the destination upload.
+The dashboard link is the subtitle and jump-back path. It is never a substitute for the destination embed.
 
 ## Uploading to Replicas
 
@@ -23830,7 +23838,7 @@ Names are normalized to hyphen-case (spaces become hyphens, e.g. \`Login page\`
 For each media file, the CLI prints an embed line and a dashboard link:
 
 1. Default and organization access print \`Replicas chat embed: ![filename](<api-url>)\`; this authenticated URL renders inline in Replicas chat **only** \u2014 see below.
-2. Public access (\`--access public\` or \`--share\`) prints \`![filename](<public-url>)\` as the Forge embed instead. This is the public, stable bearer URL for GitHub fallback embeds when native \`--attach\` is unavailable and sharing is authorized.
+2. Public access (\`--access public\` or \`--share\`) prints \`![filename](<public-url>)\` as the Forge embed instead. This is the public, stable bearer URL to paste into GitHub when sharing is authorized.
 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.
 
 Match each "View in Replicas" line to the embed line directly above it \u2014 that's the deep link for that file.
@@ -23859,7 +23867,7 @@ replicas media upload screenshot.png --name "Login page" --access public
 |---|---|---|
 | \`https://api.replicas.dev/v1/media/<id>\` (inside \`![\u2026](\u2026)\`) | Authenticated API redirect to a presigned blob \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>\` | Opt-in public bearer URL printed by \`--access public\` or \`--share\` | The Replicas chat reply and GitHub fallback embeds, for image, video, or audio media. |
+| \`https://api.replicas.dev/v1/media/public/<id>/<token>\` | Opt-in public bearer URL printed by \`--access public\` or \`--share\` | The Replicas chat reply and GitHub embeds, for image, video, or audio media. |
 | \`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. |
 
 ### NEVER link the API redirect URL outside the Replicas chat reply
@@ -23898,12 +23906,12 @@ After (or alongside) the embeds, include a \`[View in Replicas](<deep-link>)\` h
 
 After \`replicas media upload\` succeeds, external delivery has two required follow-up steps for every file:
 
-1. **Upload the raw bytes through that platform's supported inline path** so the recipient sees the media embedded in the message itself.
+1. **Use the destination's inline representation:** upload the raw bytes to Slack, Linear, or GitLab; embed a public Forge share on GitHub.
 2. **Link the Replicas dashboard deep link** (\`?media=<id>\` form) so the user can jump straight to the file in the workspace.
 
-A link alone is not enough. An upload without the dashboard link is not enough. Do both.
+A dashboard link alone is not enough. An embed without the dashboard link is not enough. Do both.
 
-Slack, Linear, and GitLab receive the original bytes through their native upload APIs. GitHub image and video attachments use \`gh --attach\` when the installed CLI and host support it; use an explicit Replicas public share only as the fallback.
+Slack, Linear, and GitLab receive the original bytes through their native upload APIs. GitHub uses a Replicas public Forge share for screenshots and recording previews.
 
 ### Slack \u2014 embed natively via the 3-step external file upload flow
 
@@ -24004,44 +24012,28 @@ The same flow works for issue bodies (use \`issueCreate\` / \`issueUpdate\` with
 
 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.
 
-### GitHub: native image and video attachments
-
-GitHub CLI v2.99.0+ supports a repeatable \`--attach\` flag on \`gh pr create\`, \`gh pr edit\`, and \`gh pr comment\` for GitHub.com and GitHub Enterprise Cloud. It uploads local images and videos to GitHub and writes the resulting attachment URL into the PR body or comment; it requires push access to the repository. GitHub Enterprise Server and unsupported media kinds are not covered by this path. See [GitHub's attachment guide](https://docs.github.com/en/github-cli/github-cli/attaching-files-with-github-cli).
+### GitHub: inline images and recording previews via Forge
 
-Check \`gh --version\` before choosing the delivery path. On a supported host with v2.99.0 or later:
+Replicas authenticates GitHub with GitHub App tokens, which native GitHub CLI attachment uploads do not support. Do not use \`gh --attach\` for media. Use a public Forge share for images in PR descriptions, issues, and comments.
 
-1. Run \`replicas media upload\` with the original file first, without \`--share\`. Keep the matching **View in Replicas** dashboard link for the PR.
-2. Put each local file path in the Markdown body where the attachment should appear, and place its dashboard link next to it.
-3. Pass the same original path once with \`--attach\`. GitHub CLI rewrites a matching local reference in place, preserving its alt text; an unreferenced attachment is appended to the body.
+Create a public share only for a public repository or after explicit consent to publish media from a private repository. If sharing is not authorized, keep the media private and include its **View in Replicas** link, explaining that inline GitHub images require a public share.
 
-\`\`\`markdown
-Before the change:
-
-![Before state](/tmp/before.png)
-[View in Replicas](https://app.replicas.dev/workspaces/<workspace-id>?media=<before-media-id>)
-\`\`\`
+1. Upload the image with public access. This creates both the Replicas dashboard copy and the Forge share:
 
 \`\`\`bash
-gh pr create \\
-  --title "Describe the change" \\
-  --body-file /tmp/pr-body.md \\
-  --attach /tmp/before.png
-
-gh pr edit 456 --body-file /tmp/pr-body.md --attach /tmp/after.png
-gh pr comment 456 --body-file /tmp/comment.md --attach /tmp/result.mp4
+replicas media upload /tmp/screenshot.png --name "PR screenshot" --access public
 \`\`\`
 
-Repeat \`--attach\` for multiple files, up to 50 per command. For an appended image, add alt text after the path with \`#\`, for example \`--attach './error.png#Error state'\`. To render a video as a player, its local Markdown reference must be the only content in its paragraph. Do not paste a Replicas authenticated API URL into the body, and do not emulate GitHub's undocumented browser upload endpoint.
-
-### GitHub attachment fallback
-
-If \`--attach\` is unavailable, the target is GitHub Enterprise Server, the file is not an image or video, or the native upload fails, keep the Replicas dashboard link and report the limitation. For an inline screenshot or video poster, create a Replicas public forge share only for a public repository or after explicit consent to publish media from a private repository, then use the printed \`Forge embed\` Markdown:
+2. Copy the printed \`![filename](<public-url>)\` Forge embed into the body file, followed by the matching **View in Replicas** link. Use the printed public URL verbatim; never use a local file path, the authenticated API URL, or an expiring storage URL.
+3. Create or update the PR using the body file:
 
 \`\`\`bash
-replicas media upload /tmp/screenshot.png --name "PR screenshot" --share
+gh pr create --title "Describe the change" --body-file /tmp/pr-body.md
+gh pr edit 456 --body-file /tmp/pr-body.md
+gh pr comment 456 --body-file /tmp/comment.md
 \`\`\`
 
-For a fallback recording preview, upload the MP4 normally, generate a poster with \`ffmpeg -i /tmp/demo.mp4 -frames:v 1 /tmp/demo-poster.png\`, share the poster, and link its embed to the recording's **View in Replicas** URL:
+GitHub does not reliably render external videos as inline players. For a recording preview, upload the MP4 normally, generate a poster with \`ffmpeg -i /tmp/demo.mp4 -frames:v 1 /tmp/demo-poster.png\`, upload the poster with \`--access public\`, and link its Forge embed to the recording's **View in Replicas** URL:
 
 \`\`\`markdown
 [![Demo recording](<public-poster-url>)](<recording-dashboard-url>)
@@ -27288,7 +27280,7 @@ var headlessFilesystemAgentResultSchema = external_exports.object({
 });
 
 // ../shared/src/cli-version.ts
-var CLI_VERSION = "0.2.672";
+var CLI_VERSION = "0.2.674";
 
 // ../shared/src/version.ts
 function compareVersions(v1, v2) {
@@ -27919,18 +27911,22 @@ async function readSseStream(body, onEvent, shouldContinue = () => true) {
   const reader = body.getReader();
   const decoder2 = new TextDecoder();
   let buffer = "";
-  while (shouldContinue()) {
-    const { done, value } = await reader.read();
-    if (done) break;
-    buffer += decoder2.decode(value, { stream: true });
-    const chunks = buffer.split("\n\n");
-    buffer = chunks.pop() ?? "";
-    for (const chunk of chunks) {
-      if (!shouldContinue()) break;
-      const parsed = parseSseChunk(chunk);
-      if (!parsed) continue;
-      await onEvent(parsed.event, parsed.id);
-    }
+  try {
+    while (shouldContinue()) {
+      const { done, value } = await reader.read();
+      if (done) break;
+      buffer += decoder2.decode(value, { stream: true });
+      const chunks = buffer.split("\n\n");
+      buffer = chunks.pop() ?? "";
+      for (const chunk of chunks) {
+        if (!shouldContinue()) break;
+        const parsed = parseSseChunk(chunk);
+        if (!parsed) continue;
+        await onEvent(parsed.event, parsed.id);
+      }
+    }
+  } finally {
+    await reader.cancel().catch(() => void 0);
   }
 }
 

package/package.json

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