ok

coder · bpmct · Apr 18, 2025 · Apr 7, 2025 · Apr 7, 2025 · Apr 7, 2025
commit bf41bb26e0487309d92edcc07d472ad182da4c41
diff --git a/goose/main.tf b/goose/main.tf
@@ -90,6 +90,32 @@ variable "experiment_post_install_script" {
   default     = null
 }
 
+variable "GOOSE_SYSTEM_PROMPT" {
+  type        = string
+  description = "The system prompt to use for Goose."
+  default     = <<-EOT
+Hey, you are a fast programming architect! The user will provide you with a prompt of something to create. Come up with a plan then create it the best you can. 
+
+Report every tiny task to Coder and be sure to be explicit about the status and whether you need
 input or not.
+
+If you are making a web app:
+  - ALWAYS listen on port 3000 so the user has a consistent preview to see their work
+    - If the dev server is already running, kill the dev server to run on port 3000.
+    - Avoid building the project for production. Just use dev servers (in a new \`screen\` as mentioned below)
+  - When you think you have finished, you should use Playwright to review the HTML to ensure it is working as expected.
+    - Feel free to fix anything bad you see.
+  - When reporting URLs to Coder, do not use localhost. Instead, run \`env | grep CODER\` and use a URL like https://nicky-pike.demo.coder.com/@USERNAME/WORKSPACE_NAME.main/apps/preview/ but with it replaced with the proper env vars. That proxies port 3000. If using Vite (or similar), be sure to allow that URL as a host as well.
+
+  Keep in mind that the proxied URL above is on a PATH. So if you are using a web framework (I prefer static HTML),
+  be sure to configure that web framework to run on the proper path as per the URL above. 
+
+  Always run long-running commands and servers (e.g. \`pnpm dev\`, \`npm run dev\`, \`python3 -m http.server\`) in a new \`screen\` so it runs it in the background and users can prompt you. Other short-lived commands (build, test, cd, write, read, view, etc) can run normally. For previewing, always use the dev server for fast feedback loops.
+
+  Your task at hand:
+EOT
+}
+
 # Install and Initialize Goose
 resource "coder_script" "goose" {
   agent_id     = var.agent_id
@@ -158,6 +184,10 @@ extensions:
 EOL
     fi
 
+    # Write system prompt to config
+    mkdir -p "$HOME/.config/goose"
+    echo "$GOOSE_SYSTEM_PROMPT" > "$HOME/.config/goose/.goosehints"
+
     # Run with screen if enabled
     if [ "${var.experiment_use_screen}" = "true" ]; then
       echo "Running Goose in the background..."
@@ -200,8 +230,7 @@ EOL
 
       screen -U -dmS goose bash -c "
         cd ${var.folder}
-        export GOOSE_SYSTEM_PROMPT=\"$GOOSE_SYSTEM_PROMPT\"
-        \"$GOOSE_CMD\" run --text \"\$GOOSE_SYSTEM_PROMPT\" --interactive | tee -a \"$HOME/.goose.log\"
+        \"$GOOSE_CMD\" run --text \"\${GOOSE_TASK_PROMPT}\" --interactive | tee -a \"$HOME/.goose.log\"
       "
     else
       # Check if goose is installed before running
@@ -248,7 +277,7 @@ resource "coder_app" "goose" {
       cd ${var.folder}
       export LANG=en_US.UTF-8
       export LC_ALL=en_US.UTF-8
-      "$GOOSE_CMD" run --text "Always report status and instructions to Coder, before and after your steps" --interactive
+      "$GOOSE_CMD" run --text "$GOOSE_TASK_PROMPT" --interactive
     fi
     EOT
   icon         = var.icon