staklink 0.3.46 → 0.3.47

package/dist/proxy-server.cjs

@@ -56941,7 +56941,7 @@ var SSEManager = class {
 var sseManager = new SSEManager();
 
 // src/proxy/version.ts
-var VERSION = "0.3.46";
+var VERSION = "0.3.47";
 
 // node_modules/uuid/dist/esm/stringify.js
 var byteToHex = [];
@@ -111183,7 +111183,8 @@ 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.
+var makePrompt = (podConfigPath, history) => {
+  let p = `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). 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).
 
@@ -111202,10 +111203,20 @@ We have SPECIAL env vars for pm2, that tell the code-server system how to automa
 
 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. 
+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. IMPORTANT: the main frontend service should be accessible from outside the pod... so depending on the language/framework being used, you might want to make sure the host is correct (such as adding '--host 0.0.0.0' to the start script of rails for example).
 
 Good luck!
 `;
+  if (history) {
+    p += `
+
+Here is a summary of our previous conversation history:
+${history}
+
+`;
+  }
+  return p;
+};
 var parseXML = (rawResponse) => {
   const files = {};
   const regex = /<([\w.\-]+)>([\s\S]*?)<\/\1>/g;
@@ -113123,8 +113134,16 @@ ${diff.trim()}`);
     createAsyncAgentHandler(
       (req) => {
         const podConfigPath = req.body.podConfigPath || "/workspaces/.pod-config/.user-dockerfile";
+        let history = void 0;
+        if (req.body.history) {
+          if (typeof req.body.history === "string") {
+            history = req.body.history;
+          } else {
+            history = JSON.stringify(req.body.history);
+          }
+        }
         return {
-          prompt: repair_exports.makePrompt(podConfigPath),
+          prompt: repair_exports.makePrompt(podConfigPath, history),
           system: repair_exports.SYSTEM
         };
       },

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.46";
+var VERSION = "0.3.47";
 
 // 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.46",
+  "version": "0.3.47",
   "type": "module",
   "publisher": "stakwork",
   "engines": {