mirror of
https://github.com/aaif-goose/goose.git
synced 2026-07-03 14:10:03 +02:00
docs: fix links in recipe topics (#6256)
This commit is contained in:
@@ -378,7 +378,7 @@ The `response` field enables recipes to enforce a final structured JSON output.
|
||||
1. **Validate the output**: Validates the output JSON against your JSON schema with basic JSON schema validations
|
||||
2. **Final structured output**: Ensure the final output of the agent is a response matching your JSON structure
|
||||
|
||||
This feature is designed for **non-interactive automation** to ensure consistent, parseable output. Recipes can produce structured output when run from either the goose CLI or goose Desktop. See [use cases and ideas for automation workflows](/docs/guides/recipes/session-recipes#response).
|
||||
This feature is designed for **non-interactive automation** to ensure consistent, parseable output. Recipes can produce structured output when run from either the goose CLI or goose Desktop. See [use cases and ideas for automation workflows](/docs/guides/recipes/session-recipes#structured-output-for-automation).
|
||||
|
||||
#### Response Schema
|
||||
|
||||
|
||||
@@ -91,7 +91,7 @@ When you modify and save a recipe with a new name, a new recipe and new link are
|
||||
:::warning Recipe File Format
|
||||
goose Desktop accepts `.yaml`, `.yml`, and `.json` files, but **the CLI only supports `.yaml` and `.json`**. For full compatibility across both interfaces, avoid `.yml` extensions.
|
||||
|
||||
All recipe formats follow the same [schema structure](/docs/guides/recipes/recipe-reference#recipe-structure).
|
||||
All recipe formats follow the same [schema structure](/docs/guides/recipes/recipe-reference#core-recipe-schema).
|
||||
:::
|
||||
|
||||
</TabItem>
|
||||
|
||||
Reference in New Issue
Block a user