docs: fixed the config_dir extraction

AIChat-Migration.md

@@ -11,7 +11,7 @@ location of the Coyote configuration directory varies between systems, you can u
 config directory:
 
 ```shell
-coyote --info | grep 'config_dir' | awk '{print $2}'
+dirname $(coyote --info | grep ^config_file | awk '{print $2}')
 ```
 
 Then, you'll need to make the following changes:

Clients.md

@@ -5,7 +5,7 @@ The location of the global Coyote configuration file varies between systems, so
 locate your configuration file:
 
 ```shell
-coyote --info | grep 'config_file' | awk '{print $2}'
+coyote --info | grep '^config_file' | awk '{print $2}'
 ```
 
 ---

Custom-Bash-Tools.md

@@ -277,7 +277,7 @@ We'd first make sure the script is visible in all contexts by ensuring it's in t
 You can find the location of your global `config.yaml` file with the following command:
 
 ```shell
-coyote --info | grep 'config_file' | awk '{print $2}'
+coyote --info | grep '^config_file' | awk '{print $2}'
 ```
 
 Then, we can instruct Coyote to build the script so we can test it out:

Custom-Tools.md

@@ -109,7 +109,7 @@ All tools have access to the following environment variables that provide contex
 | Variable             | Description                                                                                                                                                          |
 |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `LLM_OUTPUT`         | Indicates where the output of the tool should go. <br>In certain situations, this may be set to a temporary file instead of `/dev/stdout`.                           |
-| `LLM_ROOT_DIR`       | The root `config_dir` directory for Coyote <br>(i.e. `dirname $(coyote --info \| grep config_file \| awk '{print $2}')`)                                             |
+| `LLM_ROOT_DIR`       | The root `config_dir` directory for Coyote <br>(i.e. `dirname $(coyote --info \| grep ^config_file \| awk '{print $2}')`)                                            |
 | `LLM_TOOL_NAME`      | The name of the tool being executed                                                                                                                                  |
 | `LLM_TOOL_CACHE_DIR` | A directory specific to the tool for storing cache or temporary files                                                                                                |
 | `LLM_TOOL_RAW_JSON`  | The raw JSON envelope the LLM sent for this tool call, exactly as received. See [Reading values via LLM_TOOL_RAW_JSON](#reading-values-via-llm_tool_raw_json) below. |

Environment-Variables.md

@@ -5,7 +5,7 @@ Coyote also supports defining environment variables via a `.env` file in the Coy
 varies between systems, so you can find the location of your configuration directory using the following command:
 
 ```shell
-coyote --info | grep 'config_dir' | awk '{print $2}'
+dirname $(coyote --info | grep ^config_file | awk '{print $2}')
 ```
 
 ---

Getting-Started.md

@@ -37,7 +37,7 @@ The location of the global Coyote configuration varies between systems, so you c
 `config.yaml` file:
 
 ```shell
-coyote --info | grep 'config_file' | awk '{print $2}'
+coyote --info | grep '^config_file' | awk '{print $2}'
 ```
 
 The configuration file consists of a number of settings. To see a full example configuration file with every setting

Model-Sync.md

@@ -32,7 +32,7 @@ baked-in registry.
 The file lives in your Coyote configuration directory as `models-override.yaml`. To find your config directory:
 
 ```shell
-coyote --info | grep 'config_dir' | awk '{print $2}'
+dirname $(coyote --info | grep ^config_file | awk '{print $2}')
 ```
 
 The full path is therefore `<coyote-config-dir>/models-override.yaml`. If `$COYOTE_CONFIG_DIR` is set, the file is 

REPL-Prompt.md

@@ -10,7 +10,7 @@ The location of the global configuration file differs between systems, so you ca
 global configuration file's location:
 
 ```shell
-coyote --info | grep 'config_file' | awk '{print $2}'
+coyote --info | grep '^config_file' | awk '{print $2}'
 ```
 
 # Syntax

Sessions.md

@@ -104,7 +104,7 @@ Session behavior can be configured from the global Coyote configuration file. Th
 systems so you can use the following command to locate it on your system:
 
 ```shell
-coyote --info | grep 'config_file' | awk '{print $2}'
+coyote --info | grep '^config_file' | awk '{print $2}'
 ```
 
 The following settings are available to customize the default behavior of sessions globally:

Themes.md

@@ -6,7 +6,7 @@ or `light.tmTheme`. The location of the Coyote configuration directory varies be
 following command to locate it on your system:
 
 ```shell
-coyote --info | grep 'config_dir' | awk '{print $2}'
+dirname $(coyote --info | grep ^config_file | awk '{print $2}')
 ```
 
 # Themes

Tools.md

@@ -132,7 +132,7 @@ file. This file is located in the root of the Coyote `config` directory. The loc
 so your config file can be found using the following command:
 
 ```bash
-coyote --info | grep 'config_file' | awk '{print $2}'
+coyote --info | grep '^config_file' | awk '{print $2}'
 ```
 
 Each line in the `visible_tools` array lists a tool.

Vault.md

@@ -219,7 +219,7 @@ Note that all paths are relative to the Coyote configuration directory. The dire
 running
 
 ```shell
-coyote --info | grep config_dir | awk '{print $2}'
+dirname $(coyote --info | grep ^config_file | awk '{print $2}')
 ```
 
 # Environment Variable Secret Injection in Agents