docs: usage data collection (#6822)
This commit is contained in:
@@ -20,6 +20,10 @@ The configuration files allow you to set default behaviors, configure language m
|
||||
- **secrets.yaml** - API keys and secrets (only when keyring is disabled)
|
||||
- **permissions/tool_permissions.json** - Runtime permission decisions (auto-managed)
|
||||
|
||||
In addition to editing configuration files directly, many settings can be managed from goose Desktop and goose CLI:
|
||||
- **goose Desktop**: From the `Settings` page and the bottom toolbar
|
||||
- **goose CLI**: Run the `goose configure` command
|
||||
|
||||
## Global Settings
|
||||
|
||||
The following settings can be configured at the root level of your config.yaml file:
|
||||
@@ -51,6 +55,7 @@ The following settings can be configured at the root level of your config.yaml f
|
||||
| `SECURITY_PROMPT_CLASSIFIER_ENABLED` | Enable ML-based prompt injection detection for advanced threat identification | true/false | false | No |
|
||||
| `SECURITY_PROMPT_CLASSIFIER_ENDPOINT` | Classification endpoint URL for ML-based prompt injection detection | URL (e.g., "https://api.example.com/classify") | None | No |
|
||||
| `SECURITY_PROMPT_CLASSIFIER_TOKEN` | Authentication token for `SECURITY_PROMPT_CLASSIFIER_ENDPOINT` | String | None | No |
|
||||
| `GOOSE_TELEMETRY_ENABLED` | Enable [anonymous usage data](/docs/guides/usage-data) collection | true/false | false | No |
|
||||
|
||||
## Experimental Features
|
||||
|
||||
|
||||
Reference in New Issue
Block a user