tkmind/tkmind_go
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

docs: clarifies config file locations and purposes (#5210)

Browse Source 
Signed-off-by: Anthony D. Mays <anthony@morganlatimer.com>
This commit is contained in:
Anthony D. Mays
2025-10-29 13:46:01 -07:00
committed by GitHub
parent 5180c4ba54
commit 40f453445f
15 changed files with 33 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/getting-started/installation.md
+3 -2
View File
@@ -376,10 +376,10 @@ You can change your LLM provider and/or model or update your API key at any time
## Shared Configuration Settings
The Goose CLI and Desktop UI share all core configurations, including LLM provider settings, model selection, and extension configurations. When you install or configure extensions in either interface, the settings are stored in a central location at `~/.config/goose/config.yaml`, making them available to both the Desktop application and CLI. This makes it convenient to switch between interfaces while maintaining consistent settings.
The Goose CLI and Desktop UI share all core configurations, including LLM provider settings, model selection, and extension configurations. When you install or configure extensions in either interface, the settings are stored in a central location, making them available to both the Desktop application and CLI. This makes it convenient to switch between interfaces while maintaining consistent settings. For more information, visit the [Config Files][config-files] guide.
:::info
While core configurations are shared between interfaces, extensions have flexibility in how they store authentication credentials. Some extensions may use the shared config file while others implement their own storage methods.
While core configurations are shared between interfaces, extensions have flexibility in how they store authentication credentials. Some extensions may use the shared config files while others implement their own storage methods.
:::
<Tabs groupId="interface">
@@ -404,3 +404,4 @@ You can also configure Extensions to extend Goose's functionality, including add
[providers]: /docs/getting-started/providers
[handling-rate-limits]: /docs/guides/handling-llm-rate-limits-with-goose
[mcp]: https://www.anthropic.com/news/model-context-protocol
[config-files]: /docs/guides/config-files.md
documentation/docs/getting-started/using-extensions.md
+1 -1
View File
@@ -523,7 +523,7 @@ Goose relies on extension properties to determine how to handle an extension. Yo
<TabItem value="cli" label="Config file">
1. Navigate to the Goose [configuration file](/docs/guides/config-file). For example, navigate to `~/.config/goose/config.yaml` on macOS.
1. Navigate to the Goose [configuration file](/docs/guides/config-files). For example, navigate to `~/.config/goose/config.yaml` on macOS.
2. Edit the extension properties as needed and save your changes.
</TabItem>