replicas-cli 0.2.353 → 0.2.355

package/dist/index.mjs

@@ -7799,19 +7799,18 @@ function classifyCanvasFilename(filename) {
 
 // ../shared/src/pricing.ts
 var INTEGRATION_SOURCES = ["slack", "linear", "github", "gitlab"];
-var SYSTEMIC_SOURCES = ["api", "automation"];
+var AUTOMATED_SOURCES = ["api", "automation"];
 var INTEGRATION_SOURCES_SQL = INTEGRATION_SOURCES.map((s) => `'${s}'`).join(", ");
-var SYSTEMIC_SOURCES_SQL = SYSTEMIC_SOURCES.map((s) => `'${s}'`).join(", ");
+var AUTOMATED_SOURCES_SQL = AUTOMATED_SOURCES.map((s) => `'${s}'`).join(", ");
 var PLANS = {
   hobby: {
     id: "hobby",
     name: "Hobby",
     monthlyPrice: 0,
     seatPriceCents: 0,
-    creditsIncluded: 1200,
     features: [
-      "1,200 minutes of human-initiated workspace usage (one-time)",
-      "1,200 minutes of API + automation usage (one-time)",
+      "2,400 minutes of workspace usage per month",
+      "Use them however you want, manual or automated",
       "Automations (limited to 2)",
       "Warm pools and warm hooks",
       "Up to 3 repositories",
@@ -7823,9 +7822,8 @@ var PLANS = {
     name: "Developer",
     monthlyPrice: 120,
     seatPriceCents: 12e3,
-    creditsIncluded: 0,
     features: [
-      "Unlimited human-initiated workspaces",
+      "Unlimited manual workspaces",
       "5,000 included automation/API minutes per month",
       "Up to 10 repositories",
       "Up to 15 environments",
@@ -7839,9 +7837,8 @@ var PLANS = {
     name: "Team",
     monthlyPrice: 300,
     seatPriceCents: 3e4,
-    creditsIncluded: 0,
     features: [
-      "Unlimited human-initiated workspaces",
+      "Unlimited manual workspaces",
       "15,000 included automation/API minutes per month",
       "Unlimited repositories",
       "Unlimited automations",
@@ -7856,7 +7853,6 @@ var PLANS = {
     name: "Enterprise",
     monthlyPrice: 0,
     seatPriceCents: 0,
-    creditsIncluded: 0,
     features: [
       "Unlimited usage",
       "Unlimited automations",
@@ -9287,6 +9283,7 @@ In agent mode the CLI hides commands that don't make sense for in-workspace agen
 | \`replicas automation ...\` | Manage automations (cron + GitHub/GitLab event triggers) |
 | \`replicas preview ...\` | Register / list preview URLs (covered in \`PREVIEWS.md\`) |
 | \`replicas media ...\` | Upload screenshots, videos, audio (covered in \`MEDIA.md\`) |
+| \`replicas slack thread ...\` | Attach or switch Slack thread routing (covered in \`SLACK.md\`) |
 
 \`replicas <command> --help\` is always the source of truth for flags.
 
@@ -9520,6 +9517,30 @@ curl -s -X POST "https://slack.com/api/chat.postMessage" \\
 
 Omit \`thread_ts\` to post a new message to the channel. Include it to reply in a thread.
 
+#### Attach every new conversation
+
+Whenever you send a Slack message outside the thread that already routes to the current workspace, immediately attach the destination thread so future replies are delivered to this workspace:
+
+\`\`\`bash
+replicas slack thread attach --channel <channel-id> --thread-ts <thread-root-ts>
+\`\`\`
+
+- For a new top-level message or DM, use the \`channel\` and \`ts\` from the successful \`chat.postMessage\` response. That message's \`ts\` is the new thread root.
+- For a reply in another existing thread, use its root \`thread_ts\`, not the reply's \`ts\`.
+- Do not attach the originating thread again when it already routes to the current workspace.
+- Treat sending and attaching as one operation: check that both API calls succeed, and report an attachment failure instead of implying future replies will reach you.
+
+#### Switch a thread to an existing workspace
+
+When the user wants a Slack thread to continue in a particular existing workspace, resolve the target and switch the thread:
+
+\`\`\`bash
+replicas list
+replicas slack thread switch <workspace-id-or-name> --channel <channel-id> --thread-ts <thread-root-ts>
+\`\`\`
+
+The channel and thread flags default to \`SLACK_CHANNEL_ID\` and \`SLACK_THREAD_TS\` for a Slack-triggered workspace. Workspace-authenticated agents may target only their current workspace; switching to a different workspace requires running the command with user authentication outside agent mode. If that restriction applies, give the user the exact command to run rather than claiming the switch succeeded.
+
 ### Searching Messages
 
 \`\`\`bash
@@ -9658,7 +9679,7 @@ var HOOK_EXEC_MAX_BUFFER_BYTES = 10 * 1024 * 1024;
 var REPLICAS_CONFIG_FILENAMES = ["replicas.json", "replicas.yaml", "replicas.yml"];
 
 // ../shared/src/cli-version.ts
-var CLI_VERSION = "0.2.353";
+var CLI_VERSION = "0.2.355";
 
 // ../shared/src/version.ts
 function compareVersions(v1, v2) {

package/package.json

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