diff --git a/AIChat-Migration.md b/AIChat-Migration.md index 868b67e..7cda673 100644 --- a/AIChat-Migration.md +++ b/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: diff --git a/Clients.md b/Clients.md index 79421ce..b162951 100644 --- a/Clients.md +++ b/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}' ``` --- diff --git a/Custom-Bash-Tools.md b/Custom-Bash-Tools.md index 24bf16b..654ebb8 100644 --- a/Custom-Bash-Tools.md +++ b/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: diff --git a/Custom-Tools.md b/Custom-Tools.md index 5086a17..8e81a27 100644 --- a/Custom-Tools.md +++ b/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.
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
(i.e. `dirname $(coyote --info \| grep config_file \| awk '{print $2}')`) | +| `LLM_ROOT_DIR` | The root `config_dir` directory for Coyote
(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. | diff --git a/Environment-Variables.md b/Environment-Variables.md index 142c658..81822af 100644 --- a/Environment-Variables.md +++ b/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}') ``` --- diff --git a/Getting-Started.md b/Getting-Started.md index 6d3967b..efc4845 100644 --- a/Getting-Started.md +++ b/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 diff --git a/Model-Sync.md b/Model-Sync.md index 8e9efb5..d138f96 100644 --- a/Model-Sync.md +++ b/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 `/models-override.yaml`. If `$COYOTE_CONFIG_DIR` is set, the file is diff --git a/REPL-Prompt.md b/REPL-Prompt.md index a3726cb..6c72fc9 100644 --- a/REPL-Prompt.md +++ b/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 diff --git a/Sessions.md b/Sessions.md index 42a5a9a..50431fe 100644 --- a/Sessions.md +++ b/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: diff --git a/Themes.md b/Themes.md index 891ec69..8a39f66 100644 --- a/Themes.md +++ b/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 diff --git a/Tools.md b/Tools.md index 70d15b9..4a9ab25 100644 --- a/Tools.md +++ b/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. diff --git a/Vault.md b/Vault.md index 1e958ad..6e3bedf 100644 --- a/Vault.md +++ b/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