diff --git a/documentation/docs/getting-started/_category_.json b/documentation/docs/getting-started/_category_.json index 9c9d23a8ac04..26625e0cd67f 100644 --- a/documentation/docs/getting-started/_category_.json +++ b/documentation/docs/getting-started/_category_.json @@ -3,6 +3,6 @@ "position": 2, "link": { "type": "generated-index", - "description": "Get up to speed quickly with Goose" + "description": "Get up to speed quickly with goose" } } diff --git a/documentation/docs/getting-started/installation.md b/documentation/docs/getting-started/installation.md index 0b521acacff5..4e0b2ce49539 100644 --- a/documentation/docs/getting-started/installation.md +++ b/documentation/docs/getting-started/installation.md @@ -11,25 +11,25 @@ import WindowsDesktopInstallButtons from '@site/src/components/WindowsDesktopIns import LinuxDesktopInstallButtons from '@site/src/components/LinuxDesktopInstallButtons'; import { PanelLeft } from 'lucide-react'; -# Install Goose +# Install goose - Choose to install the Desktop and/or CLI version of Goose: + Choose to install the Desktop and/or CLI version of goose: - Install Goose Desktop directly from the browser or with [Homebrew](https://brew.sh/). + Install goose Desktop directly from the browser or with [Homebrew](https://brew.sh/).

Option 1: Install via Download

1. Unzip the downloaded zip file. - 2. Run the executable file to launch the Goose Desktop application. + 2. Run the executable file to launch the goose Desktop application. - :::tip Updating Goose - It's best to keep Goose updated by periodically running the installation steps again. + :::tip Updating goose + It's best to keep goose updated by periodically running the installation steps again. :::

Option 2: Install via Homebrew

@@ -40,24 +40,24 @@ import { PanelLeft } from 'lucide-react'; ---
:::info Permissions - If you're on an Apple Mac M3 and the Goose Desktop app shows no window on launch, check and update the following: + If you're on an Apple Mac M3 and the goose Desktop app shows no window on launch, check and update the following: Ensure the `~/.config` directory has read and write access. - Goose needs this access to create the log directory and file. Once permissions are granted, the app should load correctly. For steps on how to do this, refer to the [Known Issues Guide](/docs/troubleshooting/known-issues#macos-permission-issues) + goose needs this access to create the log directory and file. Once permissions are granted, the app should load correctly. For steps on how to do this, refer to the [Known Issues Guide](/docs/troubleshooting/known-issues#macos-permission-issues) :::
- Install Goose directly from the browser or with [Homebrew](https://brew.sh/). + Install goose directly from the browser or with [Homebrew](https://brew.sh/).

Option 1: Install via Download script

- Run the following command to install the latest version of Goose on macOS: + Run the following command to install the latest version of goose on macOS: ```sh curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bash ``` - This script will fetch the latest version of Goose and set it up on your system. + This script will fetch the latest version of goose and set it up on your system. If you'd like to install without interactive configuration, disable `CONFIGURE`: @@ -65,8 +65,8 @@ import { PanelLeft } from 'lucide-react'; curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash ``` - :::tip Updating Goose - It's best to keep Goose updated. To update Goose, run: + :::tip Updating goose + It's best to keep goose updated. To update goose, run: ```sh goose update ``` @@ -82,11 +82,11 @@ import { PanelLeft } from 'lucide-react'; - Choose to install the Desktop and/or CLI version of Goose: + Choose to install the Desktop and/or CLI version of goose: - Install Goose Desktop directly from the browser. + Install goose Desktop directly from the browser.

Install via Download

@@ -96,20 +96,20 @@ import { PanelLeft } from 'lucide-react'; 1. Download the DEB file 2. Navigate to the directory where it is saved in a terminal 3. Run `sudo dpkg -i (filename).deb` - 4. Launch Goose from the app menu + 4. Launch goose from the app menu - :::tip Updating Goose - It's best to keep Goose updated by periodically running the installation steps again. + :::tip Updating goose + It's best to keep goose updated by periodically running the installation steps again. ::: - Run the following command to install the Goose CLI on Linux: + Run the following command to install the goose CLI on Linux: ```sh curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bash ``` - This script will fetch the latest version of Goose and set it up on your system. + This script will fetch the latest version of goose and set it up on your system. If you'd like to install without interactive configuration, disable `CONFIGURE`: @@ -117,8 +117,8 @@ import { PanelLeft } from 'lucide-react'; curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash ``` - :::tip Updating Goose - It's best to keep Goose updated. To update Goose, run: + :::tip Updating goose + It's best to keep goose updated. To update goose, run: ```sh goose update ``` @@ -128,26 +128,26 @@ import { PanelLeft } from 'lucide-react'; - Choose to install the Desktop and/or CLI version of Goose: + Choose to install the Desktop and/or CLI version of goose: - Install Goose Desktop directly from the browser. + Install goose Desktop directly from the browser.

Install via Download

1. Unzip the downloaded zip file. - 2. Run the executable file to launch the Goose Desktop application. + 2. Run the executable file to launch the goose Desktop application. - :::tip Updating Goose - It's best to keep Goose updated by periodically running the installation steps again. + :::tip Updating goose + It's best to keep goose updated by periodically running the installation steps again. :::
- To install Goose natively on Windows, you need one of the following environments: + To install goose natively on Windows, you need one of the following environments: - **Git Bash** (recommended): Comes with [Git for Windows](https://git-scm.com/download/win) - **MSYS2**: Available from [msys2.org](https://www.msys2.org/) - **PowerShell**: Available on Windows 10/11 by default @@ -170,13 +170,13 @@ import { PanelLeft } from 'lucide-react'; ```powershell Invoke-WebRequest -Uri "https://raw.githubusercontent.com/block/goose/main/download_cli.ps1" -OutFile "download_cli.ps1"; ``` - Then run the script to install Goose: + Then run the script to install goose: ```powershell .\download_cli.ps1 ``` :::info Windows PATH Setup - If you see a warning that Goose is not in your PATH, you need to add Goose to your PATH: + If you see a warning that goose is not in your PATH, you need to add goose to your PATH:
For Git Bash/MSYS2 @@ -204,7 +204,7 @@ import { PanelLeft } from 'lucide-react';
Install via Windows Subsystem for Linux (WSL) - We recommend running the Goose CLI natively on Windows, but you can use WSL if you prefer a Linux-like environment. + We recommend running the goose CLI natively on Windows, but you can use WSL if you prefer a Linux-like environment. 1. Open [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows) as Administrator and install WSL and the default Ubuntu distribution: @@ -218,7 +218,7 @@ import { PanelLeft } from 'lucide-react'; wsl -d Ubuntu ``` - 3. Run the Goose installation script: + 3. Run the goose installation script: ```bash curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bash ``` @@ -236,7 +236,7 @@ import { PanelLeft } from 'lucide-react'; curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash ``` - If needed, add Goose to your path: + If needed, add goose to your path: ``` echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc @@ -251,7 +251,7 @@ import { PanelLeft } from 'lucide-react'; ## Set LLM Provider -Goose works with [supported LLM providers][providers] that give Goose the AI intelligence it needs to understand your requests. On first use, you'll be prompted to configure your preferred provider. +goose works with [supported LLM providers][providers] that give goose the AI intelligence it needs to understand your requests. On first use, you'll be prompted to configure your preferred provider. @@ -272,7 +272,7 @@ Goose works with [supported LLM providers][providers] that give Goose the AI int │ Tetrate Agent Router Service Login │ Opening browser for Tetrate Agent Router Service authentication... - [Goose opens the browser and prints details] + [goose opens the browser and prints details] Authentication complete! @@ -283,7 +283,7 @@ Goose works with [supported LLM providers][providers] that give Goose the AI int Testing configuration... ✓ Configuration test passed! ✓ Developer extension enabled! - └ Tetrate Agent Router Service setup complete! You can now use Goose. + └ Tetrate Agent Router Service setup complete! You can now use goose. ``` :::info Windows Users @@ -293,7 +293,7 @@ Goose works with [supported LLM providers][providers] that give Goose the AI int export OPENAI_API_KEY={your_api_key} ``` - Then run `goose configure` again. Goose will detect the environment variable and display: + Then run `goose configure` again. goose will detect the environment variable and display: ``` ● OPENAI_API_KEY is set via environment variable @@ -358,13 +358,13 @@ You can change your LLM provider and/or model or update your API key at any time -## Running Goose +## Running goose - Starting a session in the Goose Desktop is straightforward. After choosing your provider, you'll see the session interface ready for use. + Starting a session in the goose Desktop is straightforward. After choosing your provider, you'll see the session interface ready for use. - Type your questions, tasks, or instructions directly into the input field, and Goose will get to work immediately. + Type your questions, tasks, or instructions directly into the input field, and goose will get to work immediately. From your terminal, navigate to the directory you'd like to start from and run: @@ -376,7 +376,7 @@ You can change your LLM provider and/or model or update your API key at any time ## Shared Configuration Settings -The Goose CLI and Desktop UI share all core configurations, including LLM provider settings, model selection, and extension configurations. When you install or configure extensions in either interface, the settings are stored in a central location, making them available to both the Desktop application and CLI. This makes it convenient to switch between interfaces while maintaining consistent settings. For more information, visit the [Config Files][config-files] guide. +The goose CLI and Desktop UI share all core configurations, including LLM provider settings, model selection, and extension configurations. When you install or configure extensions in either interface, the settings are stored in a central location, making them available to both the Desktop application and CLI. This makes it convenient to switch between interfaces while maintaining consistent settings. For more information, visit the [Config Files][config-files] guide. :::info While core configurations are shared between interfaces, extensions have flexibility in how they store authentication credentials. Some extensions may use the shared config files while others implement their own storage methods. @@ -398,7 +398,7 @@ While core configurations are shared between interfaces, extensions have flexibi ## Additional Resources -You can also configure Extensions to extend Goose's functionality, including adding new ones or toggling them on and off. For detailed instructions, visit the [Using Extensions Guide][using-extensions]. +You can also configure Extensions to extend goose's functionality, including adding new ones or toggling them on and off. For detailed instructions, visit the [Using Extensions Guide][using-extensions]. [using-extensions]: /docs/getting-started/using-extensions [providers]: /docs/getting-started/providers diff --git a/documentation/docs/getting-started/providers.md b/documentation/docs/getting-started/providers.md index e17b5579e4d0..4e09519bae96 100644 --- a/documentation/docs/getting-started/providers.md +++ b/documentation/docs/getting-started/providers.md @@ -792,7 +792,7 @@ Beyond single-model setups, goose supports [multi-model configurations](/docs/gu --- -If you have any questions or need help with a specific provider, feel free to reach out to us on [Discord](https://discord.gg/goose-oss) or on the [Goose repo](https://github.com/block/goose). +If you have any questions or need help with a specific provider, feel free to reach out to us on [Discord](https://discord.gg/goose-oss) or on the [goose repo](https://github.com/block/goose). [providers]: /docs/getting-started/providers diff --git a/documentation/docs/guides/allowlist.md b/documentation/docs/guides/allowlist.md index d61540880a67..01d60a7736b2 100644 --- a/documentation/docs/guides/allowlist.md +++ b/documentation/docs/guides/allowlist.md @@ -1,19 +1,19 @@ --- sidebar_position: 90 -title: Goose Extension Allowlist +title: goose Extension Allowlist sidebar_label: Extension Allowlist --- -Goose is an extensible framework that, by default, allows you to install any MCP server. However, you may want stricter controls on which MCP servers can be installed as extensions (e.g. in a corporate setting). +goose is an extensible framework that, by default, allows you to install any MCP server. However, you may want stricter controls on which MCP servers can be installed as extensions (e.g. in a corporate setting). -This guide explains how you can create an **allowlist** of safe extensions that work with Goose Desktop and CLI. An allowlist lets administrators control which MCP servers can be installed as Goose extensions. When enabled, Goose will only install extensions that are on the list, and will block installation of any others. +This guide explains how you can create an **allowlist** of safe extensions that work with goose Desktop and CLI. An allowlist lets administrators control which MCP servers can be installed as goose extensions. When enabled, goose will only install extensions that are on the list, and will block installation of any others. ## How It Works 1. The allowlist is a YAML file that contains a list of allowed extension commands. -2. Goose fetches the allowlist from a URL specified by the `GOOSE_ALLOWLIST` environment variable. -3. The allowlist is fetched when first needed and is cached. It is refetched on every restart of Goose. -4. When a user attempts to install an extension, Goose checks the MCP server's installation command against the allowlist. +2. goose fetches the allowlist from a URL specified by the `GOOSE_ALLOWLIST` environment variable. +3. The allowlist is fetched when first needed and is cached. It is refetched on every restart of goose. +4. When a user attempts to install an extension, goose checks the MCP server's installation command against the allowlist. 5. If the command is not in the allowlist, the extension installation is rejected. ## Configuration diff --git a/documentation/docs/guides/cli-providers.md b/documentation/docs/guides/cli-providers.md index 5d99d41e3548..b4e35cd12689 100644 --- a/documentation/docs/guides/cli-providers.md +++ b/documentation/docs/guides/cli-providers.md @@ -2,24 +2,24 @@ sidebar_position: 45 title: CLI Providers sidebar_label: CLI Providers -description: Use Claude Code, Cursor Agent, or Gemini CLI subscriptions in Goose +description: Use Claude Code, Cursor Agent, or Gemini CLI subscriptions in goose --- # CLI Providers -Goose can make use of pass-through providers that integrate with existing CLI tools from Anthropic, Cursor, and Google. These providers allow you to use your existing Claude Code, Cursor Agent, and Google Gemini CLI subscriptions through Goose's interface, adding session management, persistence, and workflow integration capabilities to these tools. +goose can make use of pass-through providers that integrate with existing CLI tools from Anthropic, Cursor, and Google. These providers allow you to use your existing Claude Code, Cursor Agent, and Google Gemini CLI subscriptions through goose's interface, adding session management, persistence, and workflow integration capabilities to these tools. :::warning Limitations -These providers don’t fully support all Goose features, may have platform or capability limitations, and can sometimes require advanced debugging if issues arise. They’re included here purely as a convenience. +These providers don’t fully support all goose features, may have platform or capability limitations, and can sometimes require advanced debugging if issues arise. They’re included here purely as a convenience. ::: ## Why Use CLI Providers? CLI providers are useful if you: -- already have a Claude Code, Cursor, or Google Gemini CLI subscription and want to use it through Goose instead of paying per token +- already have a Claude Code, Cursor, or Google Gemini CLI subscription and want to use it through goose instead of paying per token - need session persistence to save, resume, and export conversation history -- want to use Goose recipes and scheduled tasks to create repeatable workflows +- want to use goose recipes and scheduled tasks to create repeatable workflows - prefer unified commands across different AI providers - want to [use multiple models together](#combining-with-other-models) in your tasks @@ -31,16 +31,16 @@ CLI providers are useful if you: - **Session organization**: Manage multiple conversation threads #### Workflow Integration -- **Recipe compatibility**: Use CLI providers in automated Goose recipes +- **Recipe compatibility**: Use CLI providers in automated goose recipes - **Scheduling support**: Include in scheduled tasks and workflows - **Hybrid configurations**: Combine with LLM providers using lead/worker patterns #### Interface Consistency - **Unified commands**: Use the same `goose session` interface across all providers -- **Consistent configuration**: Manage all providers through Goose's configuration system +- **Consistent configuration**: Manage all providers through goose's configuration system :::warning Extensions -CLI providers do **not** give you access to Goose's extension ecosystem (MCP servers, third-party integrations, etc.). They use their own built-in tools to prevent conflicts. If you need Goose's extensions, use standard [API providers](/docs/getting-started/providers#available-providers) instead. +CLI providers do **not** give you access to goose's extension ecosystem (MCP servers, third-party integrations, etc.). They use their own built-in tools to prevent conflicts. If you need goose's extensions, use standard [API providers](/docs/getting-started/providers#available-providers) instead. ::: @@ -53,7 +53,7 @@ The Claude Code provider integrates with Anthropic's [Claude CLI tool](https://c **Features:** - Uses Claude's latest models - 200,000 token context limit -- Automatic filtering of Goose extensions from system prompts (since Claude Code has its own tool ecosystem) +- Automatic filtering of goose extensions from system prompts (since Claude Code has its own tool ecosystem) - JSON output parsing for structured responses **Requirements:** @@ -98,14 +98,14 @@ The Gemini CLI provider integrates with Google's [Gemini CLI tool](https://ai.go Ensure your Claude CLI is authenticated and working -3. **Configure Goose** +3. **Configure goose** Set the provider environment variable: ```bash export GOOSE_PROVIDER=claude-code ``` - Or configure through the Goose CLI using `goose configure`: + Or configure through the goose CLI using `goose configure`: ```bash ┌ goose-configure @@ -139,7 +139,7 @@ The Gemini CLI provider integrates with Google's [Gemini CLI tool](https://ai.go export goose_provider=cursor-agent ``` - Or configure through the Goose CLI using `goose configure`: + Or configure through the goose CLI using `goose configure`: ```bash ┌ goose-configure @@ -166,14 +166,14 @@ The Gemini CLI provider integrates with Google's [Gemini CLI tool](https://ai.go Ensure your Gemini CLI is authenticated and working. -3. **Configure Goose** +3. **Configure goose** Set the provider environment variable: ```bash export GOOSE_PROVIDER=gemini-cli ``` - Or configure through the Goose CLI using `goose configure`: + Or configure through the goose CLI using `goose configure`: ```bash ┌ goose-configure @@ -194,7 +194,7 @@ The Gemini CLI provider integrates with Google's [Gemini CLI tool](https://ai.go ### Basic Usage -Once configured, you can start a Goose session using these providers just like any others: +Once configured, you can start a goose session using these providers just like any others: ```bash goose session @@ -202,7 +202,7 @@ goose session ### Combining with Other Models -CLI providers work well in combination with other models using Goose's [lead/worker pattern](/docs/tutorials/lead-worker): +CLI providers work well in combination with other models using goose's [lead/worker pattern](/docs/tutorials/lead-worker): ```bash # Use Claude Code as lead model, GPT-4o as worker @@ -242,12 +242,12 @@ goose session ### System Prompt Filtering -The CLI providers automatically filter out Goose's extension information from system prompts since these CLI tools have their own tool ecosystems. This prevents conflicts and ensures clean interaction with the underlying CLI tools. +The CLI providers automatically filter out goose's extension information from system prompts since these CLI tools have their own tool ecosystems. This prevents conflicts and ensures clean interaction with the underlying CLI tools. ### Message Translation -- **Claude Code**: Converts Goose messages to Claude's JSON message format, handling tool calls and responses appropriately -- **Cursor Agent**: Converts Goose messages to Cursor's JSON message format, handling tool calls and responses appropriately +- **Claude Code**: Converts goose messages to Claude's JSON message format, handling tool calls and responses appropriately +- **Cursor Agent**: Converts goose messages to Cursor's JSON message format, handling tool calls and responses appropriately - **Gemini CLI**: Converts messages to simple text prompts with role prefixes (Human:/Assistant:) ### Response Processing @@ -267,4 +267,4 @@ CLI providers depend on external tools, so ensure: --- -CLI providers offer a way to use existing AI tool subscriptions through Goose's interface, adding session management and workflow integration capabilities. They're particularly valuable for users with existing CLI subscriptions who want unified session management and recipe integration. +CLI providers offer a way to use existing AI tool subscriptions through goose's interface, adding session management and workflow integration capabilities. They're particularly valuable for users with existing CLI subscriptions who want unified session management and recipe integration. diff --git a/documentation/docs/guides/enhanced-code-editing.md b/documentation/docs/guides/enhanced-code-editing.md index 593459760b84..ee27909c6446 100644 --- a/documentation/docs/guides/enhanced-code-editing.md +++ b/documentation/docs/guides/enhanced-code-editing.md @@ -72,9 +72,9 @@ export GOOSE_EDITOR_MODEL="your-model" When the `str_replace` tool is used to edit code: -1. **Configuration Check**: Goose checks if all three environment variables are properly set and non-empty. +1. **Configuration Check**: goose checks if all three environment variables are properly set and non-empty. -2. **With AI Enabled**: If configured, Goose sends the original code and your requested change to the configured AI model for processing. +2. **With AI Enabled**: If configured, goose sends the original code and your requested change to the configured AI model for processing. 3. **Fallback**: If the AI API is not configured or the API call fails, it falls back to simple string replacement. diff --git a/documentation/docs/guides/environment-variables.md b/documentation/docs/guides/environment-variables.md index 69489174dd51..96af6932d915 100644 --- a/documentation/docs/guides/environment-variables.md +++ b/documentation/docs/guides/environment-variables.md @@ -302,7 +302,7 @@ When the keyring is disabled, secrets are stored here: ## Observability -Beyond Goose's built-in [logging system](/docs/guides/logs), you can export telemetry to external observability platforms for advanced monitoring, performance analysis, and production insights. +Beyond goose's built-in [logging system](/docs/guides/logs), you can export telemetry to external observability platforms for advanced monitoring, performance analysis, and production insights. ### OpenTelemetry Protocol (OTLP) diff --git a/documentation/docs/guides/file-management.md b/documentation/docs/guides/file-management.md index 391a11df7c43..c05e44f69dbc 100644 --- a/documentation/docs/guides/file-management.md +++ b/documentation/docs/guides/file-management.md @@ -2,18 +2,18 @@ title: File Access and Management sidebar_position: 70 sidebar_label: File Management -description: Efficiently find and reference files in Goose Desktop and follow best practices for safe file operations +description: Efficiently find and reference files in goose Desktop and follow best practices for safe file operations --- -As an autonomous agent, Goose is designed to carry out tasks following specified instructions. This often involves working with local files - both finding the right files to work with and modifying them safely. +As an autonomous agent, goose is designed to carry out tasks following specified instructions. This often involves working with local files - both finding the right files to work with and modifying them safely. -This guide covers how to efficiently access and reference files in Goose. It also includes essential best practices for safe file operations, such as monitoring changes and reverting them when necessary, to maintain the integrity of your codebase. +This guide covers how to efficiently access and reference files in goose. It also includes essential best practices for safe file operations, such as monitoring changes and reverting them when necessary, to maintain the integrity of your codebase. ## File Access -### Quick File Search in Goose Desktop +### Quick File Search in goose Desktop -Goose Desktop includes a fuzzy file search feature that makes it easy to reference files from within the chat interface without manually navigating through file system dialogs. This feature helps you quickly find and include files in your messages to Goose. +goose Desktop includes a fuzzy file search feature that makes it easy to reference files from within the chat interface without manually navigating through file system dialogs. This feature helps you quickly find and include files in your messages to goose. 1. Type `@` in the chat input to open the file search box 2. Continue typing to filter files using case-insensitive, fuzzy matching (e.g., `@readme`, `@config.js`, `@src/main`) @@ -22,7 +22,7 @@ Goose Desktop includes a fuzzy file search feature that makes it easy to referen - Use arrow keys (↑/↓) to move through the search results - Click or press `Enter` to insert the selected file path into your message -3. That's it! When you're ready, send your message to Goose +3. That's it! When you're ready, send your message to goose :::info To close the search box without selecting a file, press `Esc` or click in the chat input. @@ -40,16 +40,16 @@ To close the search box without selecting a file, press `Esc` or click in the ch ### Version Control -Always use a version control system like Git to track changes to your codebase. This prevents accidental overwriting and allows you to revert back to previous states easily. Ensure you commit changes before running Goose on your codebase. Use branches to separate experimental changes from the main codebase. +Always use a version control system like Git to track changes to your codebase. This prevents accidental overwriting and allows you to revert back to previous states easily. Ensure you commit changes before running goose on your codebase. Use branches to separate experimental changes from the main codebase. ### Validation and Testing -Implement validation and testing steps before and after Goose modifies any files. Run your unit tests to verify changes made by Goose. Use a staging environment to ensure changes integrate well with the entire system. +Implement validation and testing steps before and after goose modifies any files. Run your unit tests to verify changes made by goose. Use a staging environment to ensure changes integrate well with the entire system. ### Change Review -Manually review or use automated code reviews to ensure the quality of generated code or changes. Integrate tools such as diff tools to visualize changes made by Goose. Implement a review process with team members or CI/CD pipelines. +Manually review or use automated code reviews to ensure the quality of generated code or changes. Integrate tools such as diff tools to visualize changes made by goose. Implement a review process with team members or CI/CD pipelines. ### Codebase Organization -Structure your codebase into well-defined modules or subdirectories to manage them efficiently. Use a modular approach to isolate parts of the code Goose needs to access. You can also provide specific directories or file paths you want Goose to work on. +Structure your codebase into well-defined modules or subdirectories to manage them efficiently. Use a modular approach to isolate parts of the code goose needs to access. You can also provide specific directories or file paths you want goose to work on. diff --git a/documentation/docs/guides/goose-permissions.md b/documentation/docs/guides/goose-permissions.md index 8ec4ce08474a..d15952491b7b 100644 --- a/documentation/docs/guides/goose-permissions.md +++ b/documentation/docs/guides/goose-permissions.md @@ -15,7 +15,7 @@ goose’s permissions determine how much autonomy it has when modifying files, u