docs: sessions reorg and conversation features (#4462)

Co-authored-by: Rizel Scarlett <rizel@squareup.com>
This commit is contained in:
dianed-square
2025-09-01 16:42:43 -07:00
committed by GitHub
parent ce69b396ce
commit e73b6037a2
20 changed files with 368 additions and 97 deletions
@@ -1,6 +1,6 @@
{
"label": "Recipes",
"position": 1,
"position": 2,
"link": {
"type": "doc",
"id": "guides/recipes/index"
@@ -55,7 +55,7 @@ You can turn your current Goose session into a reusable recipe that includes the
</TabItem>
<TabItem value="cli" label="Goose CLI">
Recipe files can be either JSON (.json) or YAML (.yaml) files. While in a [session](/docs/guides/managing-goose-sessions#start-session), run this command to generate a recipe.yaml file in your current directory:
Recipe files can be either JSON (.json) or YAML (.yaml) files. While in a [session](/docs/guides/sessions/session-management#start-session), run this command to generate a recipe.yaml file in your current directory:
```sh
/recipe
@@ -441,7 +441,7 @@ You can turn your current Goose session into a reusable recipe that includes the
```
:::info
If you want to validate a recipe you just created, you need to [exit the session](/docs/guides/managing-goose-sessions#exit-session) before running the [`validate` subcommand](/docs/guides/goose-cli-commands#recipe).
If you want to validate a recipe you just created, you need to [exit the session](/docs/guides/sessions/session-management#exit-session) before running the [`validate` subcommand](/docs/guides/goose-cli-commands#recipe).
:::
Recipe validation can be useful for: