From f971d0f6f66cb70257add3d7f194d7212bde478d Mon Sep 17 00:00:00 2001 From: Diane Diaz Date: Thu, 14 Aug 2025 13:05:26 -0700 Subject: [PATCH] changes per feedback --- documentation/docs/guides/environment-variables.md | 2 +- documentation/docs/guides/recipes/session-recipes.md | 2 +- documentation/docs/guides/using-goosehints.md | 11 +++++++---- 3 files changed, 9 insertions(+), 6 deletions(-) diff --git a/documentation/docs/guides/environment-variables.md b/documentation/docs/guides/environment-variables.md index 326bc62dc273..dcceb4248f2e 100644 --- a/documentation/docs/guides/environment-variables.md +++ b/documentation/docs/guides/environment-variables.md @@ -133,7 +133,7 @@ export GOOSE_MAX_TURNS=25 export GOOSE_MAX_TURNS=100 # Use multiple context files -export CONTEXT_FILE_NAMES='["CLAUDE.md", ".goosehints", "project_rules.txt"]' +export CONTEXT_FILE_NAMES='["CLAUDE.md", ".goosehints", ".cursorrules", "project_rules.txt"]' # Set the ANSI theme for the session export GOOSE_CLI_THEME=ansi diff --git a/documentation/docs/guides/recipes/session-recipes.md b/documentation/docs/guides/recipes/session-recipes.md index b8ca683fb69a..6324bb28e15a 100644 --- a/documentation/docs/guides/recipes/session-recipes.md +++ b/documentation/docs/guides/recipes/session-recipes.md @@ -339,7 +339,7 @@ You can turn your current Goose session into a reusable recipe that includes the **Basic Usage** - Run once and exit (see [run options](/docs/guides/goose-cli-commands#run-options) and [recipe commands](/docs/guides/goose-cli-commands#recipe) for more): ```sh - # Using recipe file in current directory or GOOSE_RECIPE_PATH directories + # Using recipe file in current directory or `GOOSE_RECIPE_PATH` directories goose run --recipe recipe.yaml # Using full path diff --git a/documentation/docs/guides/using-goosehints.md b/documentation/docs/guides/using-goosehints.md index 6f9ffae82924..2a0ee78f3a43 100644 --- a/documentation/docs/guides/using-goosehints.md +++ b/documentation/docs/guides/using-goosehints.md @@ -37,8 +37,8 @@ Goose supports two types of hint files: You can use both global and local hints at the same time. When both exist, Goose will consider both your global preferences and project-specific requirements. If the instructions in your local hints file conflict with your global preferences, Goose will prioritize the local hints. -:::tip Custom Context File -You can [customize context file names](#custom-context-files) using the `CONTEXT_FILE_NAMES` environment variable. +:::tip Custom Context Files +You can use other agent rule files with Goose by using the [`CONTEXT_FILE_NAMES` environment variable](#custom-context-files). ::: @@ -140,12 +140,15 @@ Here's how it works: ### Configuration -Set the `CONTEXT_FILE_NAMES` environment variable to a JSON array of filenames. If not set, it defaults to `[".goosehints"]`. +Set the `CONTEXT_FILE_NAMES` environment variable to a JSON array of filenames. The default is `[".goosehints"]`. ```bash # Single custom file export CONTEXT_FILE_NAMES='["AGENTS.md"]' -# Multiple files (loaded in order) +# Project toolchain files +export CONTEXT_FILE_NAMES='[".cursorrules", "AGENTS.md"]' + +# Multiple files export CONTEXT_FILE_NAMES='["CLAUDE.md", ".goosehints", "project_rules.txt"]' ```