mirror of
https://github.com/aljazceru/goose.git
synced 2025-12-17 22:24:21 +01:00
docs: remove repeated paragraph (#2328)
This commit is contained in:
@@ -240,19 +240,13 @@ Goose works with a set of [supported LLM providers][providers], and you’ll nee
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
|
||||
## Goose Configuration Sharing
|
||||
|
||||
Goose Desktop and CLI applications 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.
|
||||
|
||||
You can manage these shared configurations through the Desktop settings or by using the CLI command `goose configure`, which allows you to add, remove, or toggle extensions and modify other core settings.
|
||||
|
||||
## Shared Configuration Settings
|
||||
## 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.
|
||||
|
||||
:::note
|
||||
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.
|
||||
:::
|
||||
:::
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="cli" label="Goose CLI" default>
|
||||
|
||||
Reference in New Issue
Block a user