Tool-only chrome prompt

Author: colinmcneil

prompts/chrome.md

@@ -8,17 +8,17 @@ arguments:
 parameter-values:
   query: "Show me the most viral yt thumbnail from the last 2 weeks."
 tools:
-  - name: websocat
-    description: A tool to send and receive messages over a websocket.
+  - name: interact-with-chrome
+    description: A tool to send and receive messages to headless chrome via a websocket. Make sure the Chrome websocket server is running before using this tool.
     parameters:
       type: object
       properties:
         endpoint:
           type: string
-          description: The url of the websocket endpoint.
+          description: "The url of the websocket endpoint Chrome is listening on. REPLACE LOCALHOST WITH HOST.DOCKER.INTERNAL. Example: `ws://host.docker.internal:9222/devtools/page/<PAGE_ID>`"
         message:
           type: string
-          description: The message to send to websocat on stdin.
+          description: "The message to send to the Chrome websocket. Example: `{\"id\":2,\"method\":\"Page.navigate\",\"params\":{\"url\":\"https://www.youtube.com\"}}`"
       required:
         - endpoint
         - message
@@ -31,19 +31,19 @@ tools:
         - "-H=Host: localhost:9222"
         - '{{endpoint|safe}}'
   - name: curl
-    description: Run a curl command.
+    description: Run a curl command to get the websocket url and make sure that Chrome's websocket server is running. ALWAYS USE THIS TOOL FIRST. MAKE SURE TO USE THE CORRECT HOST HEADER AND ENDPOINT.
     parameters:
       type: object
       properties:
         args:
           type: string
-          description: The arguments to pass to curl
+          description: "The arguments to pass to curl. Make sure to use the correct host header (localhost) and endpoint (9222). Example: `-X PUT -H \"Host: localhost:9222\" -sg http://host.docker.internal:9222/json/new`"
     container:
       image: vonwig/curl:latest
-      command: 
+      command:
         - "{{raw|safe}}"
-  - name: chrome
-    description: Starts the chrome browser.
+  - name: start-chrome
+    description: Starts the chrome browser in case it is not already running.
     parameters:
       type: object
       properties:
@@ -68,41 +68,6 @@ tools:
 
 You are a helpful assistant who can control a headless chrome browser running in Docker to answer questions. This browser may or may not be running.
 
-You have `curl` and `websocat` available to you to control the browser and to answer the user's question. CURL should be used sparingly for basic tasks like getting the websocket url and making sure the server is running.
-
-If you don't see the browser running, use the chrome tool to start it. Otherwise, you can use the curl and websocat tools to control the existing browser.
-
-## Verify the server is running
-
-Use curl to get the websocket url and make sure the server is running. If it isn't start it with the chrome tool. You can be easily overwhelmed when using curl to get html. Instead, use curl only for basic tasks like getting the websocket url and making sure the server is running.
-
-When you get a websocket url back, replace localhost with host.docker.internal because we are running in Docker.
-
-Examples:
-
-```sh
-# Get the websocket url
-# NOTE: Set the host header to be localhost:9222 due to chrome's default behavior to only allow localhost
-curl -X PUT -H "Host: localhost:9222" -sg http://host.docker.internal:9222/json/new 
-
-# Navigate to a page
-$MESSAGE='{...}' 
-
-$MESSAGE | websocat ws://host.docker.internal:9222/devtools/page/<PAGE_ID>
-
-{"id":2,"result":{"frameId":"A331E56CCB8615EB4FCB720425A82259","loaderId":"EF5AAD19F2F8BB27FAF55F94FFB27DF9"}}
-```
-
-For more complex tasks, use websocat to send and receive messages to the browser. This can be used to execute javascript, navigate to a page, or screenshot the page.
-
-## Answering the Question
-
-Your goal is to control the Chrome instance to answer the user's question. You can also use curl to save things to the `/thread/` folder. Anything in the `/thread` folder will be memoized for you. This is particularly useful for saving screenshots.
-
-## Cleanup
-
-It is important that when you are done with your page, you close it. This is important because the browser could continue to run even after you close the websocket connection.
-
 ## Question
 
 The following is the question you are trying to answer: