staklink 0.4.9 → 0.4.10

package/dist/proxy-server.cjs

@@ -60814,7 +60814,7 @@ var SSEManager = class {
 var sseManager = new SSEManager();
 
 // src/proxy/version.ts
-var VERSION = "0.4.9";
+var VERSION = "0.4.10";
 
 // node_modules/uuid/dist/esm/stringify.js
 var byteToHex = [];
@@ -137544,7 +137544,9 @@ async function runAgent({
   createGooseConfig(searchApiKey);
   const env2 = goose_env(apiKey, model);
   console.log("RUN goose with env", env2);
-  const cleanPrompt = sanitizeShellArg(prompt);
+  const safePrompt = prompt.startsWith("-") ? `
+${prompt}` : prompt;
+  const cleanPrompt = sanitizeShellArg(safePrompt);
   let system = SYSTEM_CORE;
   system += system_prompt ? sanitizeShellArg(system_prompt) + "\n\n" : "";
   system += SYSTEM_SUFFIX;
@@ -139220,7 +139222,17 @@ 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 STILL INCLUDE A pm2 service called "frontend", which can just be this 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.
+If this is an Android project, prefer Android conventions:
+- The frontend pm2 service can use a placeholder script (for example, "echo android-frontend") and do real setup via env commands.
+- Set PORT to "8000" (screen stream port).
+- Use PRE_START_COMMAND to ensure adb is ready (for example, "adb wait-for-device").
+- Use INSTALL_COMMAND/BUILD_COMMAND for dependency fetch + APK build (for example, "./gradlew dependencies" and "./gradlew assembleDebug").
+- Use POST_START_COMMAND to install/launch the app when needed.
+- Set REBUILD_COMMAND to APK build command and RESTART to "true" so code updates trigger rebuild/reinstall flow.
+- Derive package/activity from AndroidManifest or Gradle config when launching with adb shell am start.
+- Use ghcr.io/stakwork/staklink-android:latest as the base image in Dockerfile.
+
+IMPORTANT: You may be in a multi-repo workspace! If so, make sure the "cwd" field for each app in 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.
 

package/dist/staklink-cli.cjs

@@ -10987,7 +10987,7 @@ var glob = Object.assign(glob_, {
 glob.glob = glob;
 
 // src/proxy/version.ts
-var VERSION = "0.4.9";
+var VERSION = "0.4.10";
 
 // src/deps.ts
 var import_child_process = require("child_process");

package/package.json

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