staklink 0.3.44 → 0.3.46

package/dist/proxy-server.cjs

@@ -56941,7 +56941,7 @@ var SSEManager = class {
 var sseManager = new SSEManager();
 
 // src/proxy/version.ts
-var VERSION = "0.3.44";
+var VERSION = "0.3.46";
 
 // node_modules/uuid/dist/esm/stringify.js
 var byteToHex = [];
@@ -111159,11 +111159,12 @@ __export(repair_exports, {
   makePrompt: () => makePrompt,
   parseXML: () => parseXML
 });
-var SYSTEM = `You are a software systems expert. Your job is to help set up the development environment for a software project. Fix the user's pm2 config and/or docker-compose files, and use the pm2 and docker cli to get the project running. YOUR GOAL IS TO THE GET THE frontend APP IN THE PM2 CONFIG FILE TO RUN CORRECTLY! Other apps and docker containers are only supporting services.
+var SYSTEM = `You are a software systems expert. Your job is to help set up the development environment for a software project. Fix the user's pm2 config and/or docker-compose files, and use the pm2 and docker cli to get the project running. YOUR GOAL IS TO THE GET THE frontend APP IN THE PM2 CONFIG FILE TO RUN CORRECTLY! Other apps and docker containers are only supporting services. You can restart the pm2 environment with "npx -y staklink reload" after making changes to the pm2 config or docker-compose files.
 
 When you have gotten the frontend running, or gotten as far as you can, respond to the user by saying either "<status>COMPLETE</status>" or "<status>FAILED</status>". If COMPLETE, then tell the user the fixed config files (put the exact raw content of the files in the XML tags, no extra text like triple backticks or language label). FOR YOUR FINAL TEXT RESPONSE, USE THE THE FOLLOWING XML FORMAT:
 
 <status>COMPLETE</status>
+<summary>Short summary of what you did here.</summary>
 <pm2.config.js>
 module.exports = {
   apps: [ ... ]
@@ -111177,11 +111178,14 @@ services:
 <Dockerfile>
 FROM ghcr.io/stakwork/staklink-js:latest
 </Dockerfile>
+<.env>
+NEW_ENV_VAR=some_value
+</.env>
 
 IMPORTANT: YOU DO NOT NEED TO INCLUDE FILES THAT DID NOT CHANGE. Only include files that you modified.`;
 var makePrompt = (podConfigPath) => `Please inspect the current running environment, and try to fix it. The user tried to load the frontend on the defined PORT, but something went wrong.
 
-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). 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).
+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). Also you may need to return required environment variables in a .env 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).
 
 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.
 
@@ -111196,7 +111200,9 @@ We have SPECIAL env vars for pm2, that tell the code-server system how to automa
 - TEST_COMMAND: Command to run tests (e.g. npm test)
 - E2E_TEST_COMMAND: Command to run end-to-end tests (e.g. npx playwright test)
 
-When you have made a file change and want to restart the whole pm2 environment, do so like this: \`npx -y staklink reload\`. That will start the pm2 apps, then re-run all the install, build, pre-start commands if they are defined. None of these commands are required though, only the "script" is required (to start the frontend).
+None of these commands are required though, only the "script" is required (to start the frontend).
+
+When you have made a file change and want to restart the whole pm2 environment, do so like this: \`npx -y staklink reload\`. That will start the pm2 apps, then re-run all the install, build, pre-start commands if they are defined. 
 
 Good luck!
 `;
@@ -113125,34 +113131,6 @@ ${diff.trim()}`);
       (result) => repair_exports.parseXML(result)
     )
   );
-  app.post("/repair", async (req, res) => {
-    const request_id = startReq();
-    try {
-      const { repoName, prompt, apiKey, agent_name, session, system } = req.body;
-      const workspaceRoot2 = await workspaceRoot();
-      let repoPath = workspaceRoot2;
-      if (repoName) {
-        const candidate = import_path2.default.join(workspaceRoot2, repoName);
-        try {
-          const stat4 = await import_promises2.default.stat(candidate);
-          if (stat4.isDirectory()) {
-            repoPath = candidate;
-          }
-        } catch {
-        }
-      }
-      const agentFn = chooseAgent(agent_name || "goose");
-      agentFn(prompt, apiKey, repoPath, session, system).then((result) => {
-        finishReq(request_id, { success: true, result });
-      }).catch((error85) => {
-        failReq(request_id, error85);
-      });
-      res.json({ request_id, status: "pending" });
-    } catch (e) {
-      console.error("Error running claude scripts:", e);
-      fail(res, e);
-    }
-  });
   app.post(
     "/goose_web",
     async (req, res) => {

package/dist/staklink-cli.cjs

@@ -10948,7 +10948,7 @@ var glob = Object.assign(glob_, {
 glob.glob = glob;
 
 // src/proxy/version.ts
-var VERSION = "0.3.44";
+var VERSION = "0.3.46";
 
 // src/cli.ts
 var STAKLINK_PROXY = "staklink-proxy";

package/package.json

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