vrr/goose
2
0
Fork 0
mirror of https://github.com/block/goose.git synced 2026-04-28 19:49:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 34

Add settings field documentation to recipe guides (#3809)

Browse source
This commit is contained in:
Rizel Scarlett 2025-08-03 00:12:10 -04:00 • committed by GitHub
parent f775cd9a47
commit c850ac20f4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 50 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

13
documentation/docs/tutorials/recipes-tutorial.md
View file

@ -82,11 +82,22 @@ goose run --recipe trip.yaml --params destination=Africa --params duration=14
By default, Goose uses the `temperature` and `model` you've already chosen, which usually works just fine. But sometimes you might want more control. For example, when performing a subjective task like planning a trip, it can help to turn up the `temperature` setting. Think of temperature like a creativity dial - the higher it is, the more varied and unexpected the results. If the first suggestion isn't quite right, the user can just run the recipe again to get a new one.
You can also specify which AI provider and model to use for a specific recipe:
```yaml
settings:
temperature: 0.8
goose_provider: "anthropic"
goose_model: "claude-3-5-sonnet-latest"
temperature: 0.8
```
The available settings are:
- `goose_provider`: The AI provider (e.g., "anthropic", "openai")
- `goose_model`: The specific model name
- `temperature`: Controls creativity/randomness (0.0-1.0, higher = more creative)
These settings will override your default Goose configuration when this recipe runs.
## External Files
Sometimes, you'll want to give the agent access to extra information without cramming all that data into the prompt. Instead of pasting everything in, you can keep the data in a separate file and point the recipe to it.