replicas-cli 0.2.251 → 0.2.253

package/dist/index.mjs

@@ -8056,8 +8056,66 @@ var GITHUB_ABILITY = {
   referenceFile: { name: "GITHUB.md", content: REFERENCE3 }
 };
 
+// ../shared/src/default-skills/replicas-agent/abilities/gitlab.ts
+var SECTION4 = `### GitLab
+Workspace repos hosted on GitLab use pre-configured git credentials \u2014 push, pull, and open merge requests with plain \`git\`.
+
+**Reference:** \`references/GITLAB.md\`
+
+Use this when:
+- A repo's remote is on gitlab.com or a self-managed GitLab instance
+- You need to open or update a merge request`;
+var REFERENCE4 = `# GitLab Integration
+
+This guide covers how to work with GitLab-hosted repositories from within your Replicas workspace.
+
+## Prerequisites
+
+Git credentials for the workspace's GitLab hosts are pre-configured in \`~/.git-credentials\` and refreshed automatically. Plain \`git fetch\` / \`git pull\` / \`git push\` over HTTPS work with no additional setup.
+
+- Never ask the user for a GitLab token or PAT \u2014 credentials are already wired. If a push fails with an authentication error, report it to the user instead of working around it.
+- There is no \`glab\` CLI in the workspace, and \`gh\` only works for GitHub remotes. Check a repo's host with \`git remote get-url origin\` before choosing the GitHub or GitLab workflow.
+
+## Merge Requests
+
+Create a merge request directly from a push using push options:
+
+\`\`\`bash
+git push -o merge_request.create -o merge_request.target=<default-branch> origin HEAD
+\`\`\`
+
+Useful options:
+
+\`\`\`bash
+-o merge_request.title="Title"
+-o merge_request.description="Description"
+-o merge_request.draft                  # open as draft
+-o merge_request.remove_source_branch   # delete branch on merge
+\`\`\`
+
+GitLab prints the MR URL in the push output \u2014 include it in your reply to the user.
+
+## GitLab API (advanced)
+
+For operations with no git equivalent (commenting on MRs, reading pipelines), call the REST API with the workspace credential:
+
+\`\`\`bash
+TOKEN=$(grep -m1 '://oauth2:' ~/.git-credentials | sed -E 's#https://oauth2:([^@]+)@.*#\\1#')
+curl -s -H "Authorization: Bearer $TOKEN" "https://gitlab.com/api/v4/projects/<url-encoded-path>/merge_requests"
+\`\`\`
+
+Use the repo's own host in the API base URL for self-managed instances.
+`;
+var GITLAB_ABILITY = {
+  label: "GitLab",
+  description: "Pre-configured git credentials for GitLab repos; merge requests via push options.",
+  bullet: "- Interacting with GitLab (pushing to GitLab repos, opening merge requests)",
+  section: SECTION4,
+  referenceFile: { name: "GITLAB.md", content: REFERENCE4 }
+};
+
 // ../shared/src/default-skills/replicas-agent/abilities/google.ts
-var SECTION4 = `### Google Workspace (Docs, Sheets, Forms, Drive)
+var SECTION5 = `### Google Workspace (Docs, Sheets, Forms, Drive)
 Create and edit Google Docs, Sheets, and Forms via the Replicas gateway. Files are owned by Replicas \u2014 the integration cannot access pre-existing Google content created outside of it.
 
 **Reference:** \`references/GOOGLE.md\`
@@ -8066,7 +8124,7 @@ Use this when:
 - You need to create or edit a Google Doc, Sheet, or Form
 - You need to share, rename, move, or delete a Replicas-created Google file
 - You need to read responses from a Replicas-created Google Form`;
-var REFERENCE4 = `# Google Workspace (Docs, Sheets, Forms, Drive)
+var REFERENCE5 = `# Google Workspace (Docs, Sheets, Forms, Drive)
 
 This guide covers how to create and edit Google Docs, Sheets, and Forms \u2014 plus do basic Drive file operations \u2014 from inside a Replicas workspace, using the monolith as a gateway to Google's APIs.
 
@@ -8327,12 +8385,12 @@ var GOOGLE_ABILITY = {
   label: "Google Workspace",
   description: "Create / edit Docs, Sheets, Forms, and Drive files via the Replicas gateway.",
   bullet: "- Interacting with Google Workspace (creating and editing Docs, Sheets, and Forms, sharing files, reading form responses, etc.)",
-  section: SECTION4,
-  referenceFile: { name: "GOOGLE.md", content: REFERENCE4 }
+  section: SECTION5,
+  referenceFile: { name: "GOOGLE.md", content: REFERENCE5 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/linear.ts
-var SECTION5 = `### Linear
+var SECTION6 = `### Linear
 Fetch issues, update state, add comments, and search via the Linear GraphQL API.
 
 **Reference:** \`references/LINEAR.md\`
@@ -8341,7 +8399,7 @@ Use this when:
 - You encounter a Linear issue link and need to understand the task
 - You need to update an issue's state (e.g. mark as done)
 - You need to comment on or search for Linear issues`;
-var REFERENCE5 = `# Linear Integration
+var REFERENCE6 = `# Linear Integration
 
 This guide covers how to interact with Linear from within your Replicas workspace.
 
@@ -8416,12 +8474,12 @@ var LINEAR_ABILITY = {
   label: "Linear",
   description: "Fetch issues, post comments, update states via the Linear GraphQL API.",
   bullet: "- Interacting with Linear (fetching issues, updating state, commenting, etc.)",
-  section: SECTION5,
-  referenceFile: { name: "LINEAR.md", content: REFERENCE5 }
+  section: SECTION6,
+  referenceFile: { name: "LINEAR.md", content: REFERENCE6 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/media.ts
-var SECTION6 = `### Media
+var SECTION7 = `### Media
 Share screenshots, screen recordings, generated diagrams, and audio clips inline in the Replicas chat and natively embedded in external messages.
 
 **Reference:** \`references/MEDIA.md\`
@@ -8430,7 +8488,7 @@ Use this when:
 - You produce a screenshot, recording, generated image, or audio clip the user should see
 - You record video output (browser automation, screen capture) \u2014 including the recommended aspect ratio and FPS
 - You need to embed media in a Slack/Linear/GitHub message AND keep a referenceable copy in the Replicas dashboard`;
-var REFERENCE6 = `# Media (Screenshots, Recordings, Audio)
+var REFERENCE7 = `# Media (Screenshots, Recordings, Audio)
 
 This guide covers how to share screenshots, screen recordings, generated diagrams, and audio clips \u2014 both inline in the Replicas chat and natively embedded in external surfaces (Slack, Linear, GitHub).
 
@@ -8681,12 +8739,12 @@ var MEDIA_ABILITY = {
   label: "Media",
   description: "Share screenshots, recordings, generated images, and audio clips.",
   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 }
+  section: SECTION7,
+  referenceFile: { name: "MEDIA.md", content: REFERENCE7 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/previews.ts
-var SECTION7 = `### Previews
+var SECTION8 = `### Previews
 Expose locally running services (web apps, APIs, databases) as public preview URLs so humans can interact with them directly.
 
 **Reference:** \`references/PREVIEWS.md\`
@@ -8695,7 +8753,7 @@ Use this when:
 - You need to start a service that a human should view or interact with
 - The task involves UI work that benefits from human review
 - You are verifying frontend/backend integrations visually`;
-var REFERENCE7 = `# Preview URLs
+var REFERENCE8 = `# Preview URLs
 
 When you run services on ports \u2014 such as a web app, API server, or database \u2014 humans may want to interact with them directly. You can expose your locally running services as public preview URLs.
 
@@ -8777,12 +8835,12 @@ var PREVIEWS_ABILITY = {
   label: "Previews",
   description: "Expose locally running services on public preview URLs for humans.",
   bullet: "- Creating preview URLs for locally running services",
-  section: SECTION7,
-  referenceFile: { name: "PREVIEWS.md", content: REFERENCE7 }
+  section: SECTION8,
+  referenceFile: { name: "PREVIEWS.md", content: REFERENCE8 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/replicas.ts
-var SECTION8 = `### Replicas (in-workspace CLI)
+var SECTION9 = `### Replicas (in-workspace CLI)
 Take action *with* Replicas itself \u2014 manage automations, environments (variables, files), repos, and \`replicas.json\` config \u2014 using the pre-installed, pre-authenticated \`replicas\` CLI.
 
 **Reference:** \`references/REPLICAS.md\`
@@ -8792,7 +8850,7 @@ Use this when:
 - The user asks you to manage environments, environment variables, or environment files
 - The user asks "what envs / repos / automations do I have?"
 - The user asks you to scaffold a \`replicas.json\` / \`replicas.yaml\` in a repo`;
-var REFERENCE8 = `# Replicas (in-workspace CLI)
+var REFERENCE9 = `# Replicas (in-workspace CLI)
 
 This guide covers how to take action *with* Replicas itself from inside a Replicas workspace \u2014 managing automations, environments (and their variables/files), repos, previews, and the user's \`replicas.json\` config \u2014 using the pre-installed \`replicas\` CLI.
 
@@ -8986,13 +9044,13 @@ var REPLICAS_ABILITY = {
   description: "Teach the agent about Replicas itself \u2014 automations, environments, the in-workspace CLI.",
   // No bullet — help_instructions covers the `replicas` CLI surface in detail.
   bullet: "",
-  section: SECTION8,
-  referenceFile: { name: "REPLICAS.md", content: REFERENCE8 },
+  section: SECTION9,
+  referenceFile: { name: "REPLICAS.md", content: REFERENCE9 },
   locked: true
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/slack.ts
-var SECTION9 = `### Slack
+var SECTION10 = `### Slack
 Send messages, read threads, search conversations, and upload files via the Slack Web API.
 
 **Reference:** \`references/SLACK.md\`
@@ -9002,7 +9060,7 @@ Use this when:
 - You need to read or fetch a Slack conversation
 - You encounter a Slack message link and need to retrieve its content
 - The task asks you to notify, update, or communicate via Slack`;
-var REFERENCE9 = `# Slack Integration
+var REFERENCE10 = `# Slack Integration
 
 This guide covers how to interact with Slack from within your Replicas workspace.
 
@@ -9103,8 +9161,8 @@ var SLACK_ABILITY = {
   label: "Slack",
   description: "Send messages, read threads, search conversations, upload files.",
   bullet: "- Interacting with Slack (sending messages, reading threads, etc.)",
-  section: SECTION9,
-  referenceFile: { name: "SLACK.md", content: REFERENCE9 }
+  section: SECTION10,
+  referenceFile: { name: "SLACK.md", content: REFERENCE10 }
 };
 
 // ../shared/src/default-skills/replicas-agent/registry.ts
@@ -9113,6 +9171,7 @@ var REPLICAS_AGENT_ABILITY_REGISTRY = {
   computer: COMPUTER_ABILITY,
   docker: DOCKER_ABILITY,
   github: GITHUB_ABILITY,
+  gitlab: GITLAB_ABILITY,
   google: GOOGLE_ABILITY,
   linear: LINEAR_ABILITY,
   media: MEDIA_ABILITY,
@@ -9157,7 +9216,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.251";
+var CLI_VERSION = "0.2.253";
 
 // ../shared/src/engine/environment.ts
 var DESKTOP_NOVNC_PORT = 6080;
@@ -11349,7 +11408,7 @@ Found ${response.workspaces.length} workspaces matching "${workspaceName}":`));
   console.log(chalk4.gray(`  Status: ${selectedWorkspace.status || "unknown"}`));
   if (selectedWorkspace.status === "sleeping") {
     throw new Error(
-      "Workspace is currently sleeping. Wake it using `replicas app` (press w on a sleeping workspace) or visit https://tryreplicas.com"
+      "Workspace is currently sleeping. Wake it using `replicas interact` (press w on a sleeping workspace) or visit https://tryreplicas.com"
     );
   }
   console.log(chalk4.blue("\nRequesting SSH access token..."));

package/package.json

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