staklink 0.3.91 → 0.4.0

package/dist/proxy-server.cjs

@@ -61258,7 +61258,7 @@ var SSEManager = class {
 var sseManager = new SSEManager();
 
 // src/proxy/version.ts
-var VERSION = "0.3.91";
+var VERSION = "0.4.0";
 
 // node_modules/uuid/dist/esm/stringify.js
 var byteToHex = [];
@@ -136946,6 +136946,8 @@ var makeRepairPrompt = (podConfigPath, history, initialPrompt) => {
   
 The config files can be read at ${podConfigPath}. You must find out how to edit the pm2.config.js and the docker-compose.yaml in order to get the project to run successfully (there is also a Dockerfile which may also be changed if absolutely needed). Remember that you may need to add or alter env vars in the pm2.config.js file. Focus on the frontend app defined in the pm2 config file, don't worry about other services unless they are needed to run the frontend. For example, if its a next.js app, you can read the package.json to see what SHOULD be in the pm2 "script" command or the special install/build/etc commands. REMEMBER: this is a development environment, so the pm2 script should be something like "npm run dev" or something similar... we want to default to whatever start script is best for development (like whatever has hot-reload etc). If its a simple backend api project, then thats fine to be defined as the "frontend". If there really is no public-facing frontend or api, then the "frontend" pm2 service should just be a dummy server: "npx -y hell0-w0rld". Its important that we have at least SOMETHING running as the "frontend" so we can verify that the pod is running smoothly!
 
+IMPORTANT: You may be in a multi-repo workspace! If so, make sure the "cwd" field for each appin the pm2.config.js specifies different paths to each repo! Like "/workspaces/repo1", "/workspaces/repo2", etc.
+
 This project is currently running a remote code-server instance. Docker is optional, but may be used. The docker-compose file has already been started. You can use the regular docker commands (docker ps, docker logs, etc) to inspect the running containers.
 
 The actual core project code is being run with pm2! You can use pm2 commands to inspect the running processes. However, there is another service running in pm2 also (called staklink-proxy), that is not part of the software project at hand. DO NOT run "pm2 logs" just like that... only read logs of specific processes from the pm2 config file one at a time! Your goal is to get all supporting services and processes running in order to run the main project frontend. (Of course, sometimes its just one simple frontend process without supporting services. It really just depends on the project).

package/dist/staklink-cli.cjs

@@ -10967,13 +10967,18 @@ var glob = Object.assign(glob_, {
 glob.glob = glob;
 
 // src/proxy/version.ts
-var VERSION = "0.3.91";
+var VERSION = "0.4.0";
 
-// src/goose.ts
+// src/deps.ts
 var import_child_process = require("child_process");
 var import_util2 = require("util");
 var execAsync = (0, import_util2.promisify)(import_child_process.exec);
 var GOOSE_VERSION = "1.22.0";
+async function ensureDepsInstalled() {
+  await ensureGooseInstalled();
+  await ensureAgentBrowserInstalled();
+  await ensureAgentBrowserSkillInstalled();
+}
 async function ensureGooseInstalled() {
   try {
     const { stdout } = await execAsync("goose --version");
@@ -11003,6 +11008,52 @@ async function installGoose() {
     console.error("\u26A0\uFE0F Failed to install Goose:", error2);
   }
 }
+async function ensureAgentBrowserInstalled() {
+  try {
+    await execAsync("agent-browser --version");
+    console.log("\u2705 agent-browser is already installed");
+  } catch {
+    console.log("\u{1F4E6} agent-browser not found, installing...");
+    await installAgentBrowser();
+  }
+}
+async function installAgentBrowser() {
+  try {
+    console.log("\u{1F4E6} Installing agent-browser...");
+    await execAsync("npm install -g agent-browser");
+    console.log("\u{1F4E6} Running agent-browser install...");
+    await execAsync("agent-browser install");
+    console.log("\u2705 agent-browser installed successfully");
+  } catch (error2) {
+    console.error("\u26A0\uFE0F Failed to install agent-browser:", error2);
+  }
+}
+var AGENT_BROWSER_SKILL_NAME = "agent-browser";
+var AGENT_BROWSER_SKILL_REPO = "https://github.com/vercel-labs/agent-browser";
+async function ensureAgentBrowserSkillInstalled() {
+  try {
+    const { stdout } = await execAsync("npx skills ls -g");
+    if (stdout.includes(AGENT_BROWSER_SKILL_NAME)) {
+      console.log(`\u2705 Skill "${AGENT_BROWSER_SKILL_NAME}" is already installed`);
+      return;
+    }
+    console.log(`\u{1F4E6} Installing ${AGENT_BROWSER_SKILL_NAME} skill...`);
+    await installAgentBrowserSkill();
+  } catch {
+    console.log(`\u{1F4E6} Installing ${AGENT_BROWSER_SKILL_NAME} skill...`);
+    await installAgentBrowserSkill();
+  }
+}
+async function installAgentBrowserSkill() {
+  try {
+    await execAsync(
+      `npx skills add ${AGENT_BROWSER_SKILL_REPO} --skill ${AGENT_BROWSER_SKILL_NAME} -g -y`
+    );
+    console.log(`\u2705 Skill "${AGENT_BROWSER_SKILL_NAME}" installed successfully`);
+  } catch (error2) {
+    console.error(`\u26A0\uFE0F Failed to install ${AGENT_BROWSER_SKILL_NAME} skill:`, error2);
+  }
+}
 
 // src/cli.ts
 var STAKLINK_PROXY = "staklink-proxy";
@@ -11048,7 +11099,7 @@ program2.command("start").description("Start the staklink proxy server").action(
     const root = await workspaceRoot();
     const proxyServerPath = getProxyPath();
     console.log("Starting staklink proxy server...");
-    await ensureGooseInstalled();
+    await ensureDepsInstalled();
     console.log(`Workspace root: ${root}`);
     console.log(`Proxy server path: ${proxyServerPath}`);
     const runner = new Runner(root, console.log);

package/package.json

@@ -2,7 +2,7 @@
   "name": "staklink",
   "displayName": "staklink",
   "description": "staklink process manager",
-  "version": "0.3.91",
+  "version": "0.4.0",
   "type": "module",
   "publisher": "stakwork",
   "engines": {