PR feedback

Signed-off-by: Grant Linville <[email protected]>

Author: g-linville

docs/docs/03-tools/08-workspace.md

@@ -10,6 +10,7 @@ gptscript --workspace . my-script.gpt
 ```
 
 In the above example, the user’s current directory (denoted by `.`) will be set as the workspace.
+The workspace directory is no longer temporary if it is explicitly set, and everything in it will persist after the script has finished running.
 Both absolute and relative paths are supported.
 
 Regardless of whether it is set implicitly or explicitly, the workspace is then made available to the script execution as the `GPTSCRIPT_WORKSPACE_DIR` environment variable.
@@ -21,7 +22,7 @@ The tools must decide to make use of the workspace environment variable.
 
 ## The Workspace Context Tool
 
-To make prompt-based tools aware of the workspace, you can reference the workspace context tool:
+To make a non-code tool that uses the LLM aware of the workspace, you can reference the workspace context tool:
 
 ```
 Context: github.com/gptscript-ai/context/workspace

docs/docs/03-tools/09-code-tool-guidelines.md

@@ -10,6 +10,7 @@ This guide provides guidelines for setting up GitHub repos for proper tool distr
 ### `tool.gpt` or `agent.gpt` file
 
 Every repo should have a `tool.gpt` or `agent.gpt` file. This is the main logic of the tool.
+If both files exist, GPTScript will use the `agent.gpt` file and ignore the `tool.gpt` file.
 Your repo can have other `.gpt` files that are referenced by the main file, but there must be a `tool.gpt` or `agent.gpt` file present.
 
 Under most circumstances, this file should live in the root of the repo.
@@ -116,6 +117,10 @@ Name: my-go-tool
 #!${GPTSCRIPT_TOOL_DIR}/bin/gptscript-go-tool
 ```
 
+:::important
+Unlike the Python and Node cases above where you can name the file you are going to run anything you want, Go tools must be `#!${GPTSCRIPT_TOOL_DIR}/bin/gptscript-go-tool`.
+:::
+
 GPTScript will build the Go program located at `./main.go` to a file called `./bin/gptscript-go-tool` before running the tool.
 All of your dependencies need to be properly specified in a `go.mod` file.
 

docs/docs/03-tools/10-daemon.md

@@ -58,8 +58,17 @@ Let's talk about the daemon tool, called `my-daemon`, first.
 The body of this tool begins with `#!sys.daemon`. This tells GPTScript to take the rest of the body as a command to be
 run in the background that will listen for HTTP requests. GPTScript will run this command (in this case, a Node script).
 GPTScript will assign a port number for the server and set the `PORT` environment variable to that number, so the
-server needs to check that variable and listen on the proper port. The server is required to respond to a GET request at
-`/` with 200 OK, so that GPTScript can make sure it is running properly before continuing execution.
+server needs to check that variable and listen on the proper port.
+
+After GPTScript runs the daemon, it will send it an HTTP GET request to make sure that it is running properly.
+The daemon needs to respond with a 200 OK to this request.
+By default, the request goes to `/`, but this can be configured with the following syntax:
+
+```
+#!sys.daemon (path=/api/ready) node
+
+// (node script here)
+```
 
 ### The Entrypoint Tool