diff --git a/documentation/docs/getting-started/installation.md b/documentation/docs/getting-started/installation.md index b084243f00f7..c7bb426991e4 100644 --- a/documentation/docs/getting-started/installation.md +++ b/documentation/docs/getting-started/installation.md @@ -18,7 +18,7 @@ import { PanelLeft } from 'lucide-react'; Choose to install the Desktop and/or CLI version of Goose: - + Install Goose Desktop directly from the browser or with [Homebrew](https://brew.sh/).

Option 1: Install via Download

@@ -48,7 +48,7 @@ import { PanelLeft } from 'lucide-react'; ::: - + Install Goose directly from the browser or with [Homebrew](https://brew.sh/).

Option 1: Install via Download script

@@ -85,7 +85,7 @@ import { PanelLeft } from 'lucide-react'; Choose to install the Desktop and/or CLI version of Goose: - + Install Goose Desktop directly from the browser.

Install via Download

@@ -103,7 +103,7 @@ import { PanelLeft } from 'lucide-react'; ::: - + Run the following command to install the Goose CLI on Linux: ```sh @@ -131,7 +131,7 @@ import { PanelLeft } from 'lucide-react'; Choose to install the Desktop and/or CLI version of Goose: - + Install Goose Desktop directly from the browser.

Install via Download

@@ -146,7 +146,7 @@ import { PanelLeft } from 'lucide-react'; ::: - + 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/) @@ -254,11 +254,11 @@ import { PanelLeft } from 'lucide-react'; 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. - + On the welcome screen, choose how to configure a provider: - + The CLI automatically enters configuration mode where you can choose how to configure a provider: @@ -316,13 +316,13 @@ Goose works with [supported LLM providers][providers] that give Goose the AI int You can change your LLM provider and/or model or update your API key at any time. - + 1. Click the button in the top-left to open the sidebar. 2. Click the `Settings` button on the sidebar. 3. Click the `Models` tab. 4. Choose to update your provider, switch models, or click `Reset Provider and Model` to clear your settings and return to the welcome screen. See details about these [configuration options](/docs/getting-started/providers#configure-provider). - + 1. Run the following command: ```sh goose configure @@ -361,12 +361,12 @@ You can change your LLM provider and/or model or update your API key at any time ## Running Goose - + 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. - + From your terminal, navigate to the directory you'd like to start from and run: ```sh goose session @@ -383,12 +383,12 @@ While core configurations are shared between interfaces, extensions have flexibi ::: - + Navigate to shared configurations through: 1. Click the button in the top-left to open the sidebar. 2. Click the `Settings` button on the sidebar. - + Use the following command to manage shared configurations: ```sh goose configure diff --git a/documentation/docs/getting-started/using-extensions.md b/documentation/docs/getting-started/using-extensions.md index 455abf8e03a7..2e99e6f161fd 100644 --- a/documentation/docs/getting-started/using-extensions.md +++ b/documentation/docs/getting-started/using-extensions.md @@ -33,13 +33,13 @@ Here are the built-in extensions: #### Toggling Built-in Extensions - + 1. Click the button in the top-left to open the sidebar. 2. Click the `Extensions` button on the sidebar. 3. Under `Extensions`, you can toggle the built-in extensions on or off. - + If you know the exact name of the extension you'd like to add, run: @@ -120,7 +120,7 @@ See available servers in the **[MCP Server Directory](https://www.pulsemcp.com/s ::: - + 1. Click the button in the top-left to open the sidebar. 2. Click the `Extensions` button on the sidebar. @@ -138,7 +138,7 @@ See available servers in the **[MCP Server Directory](https://www.pulsemcp.com/s * **Command**: `npx -y @modelcontextprotocol/server-memory` - + 1. Run the following command: @@ -349,14 +349,14 @@ extensions: You can enable or disable installed extensions based on your workflow needs. - + 1. Click the button in the top-left to open the sidebar. 2. Click the `Extensions` button on the sidebar. 2. Use the toggle switch next to each extension to enable or disable it. - + 1. Run the following command to open up Goose's configurations: ```sh goose configure @@ -397,7 +397,7 @@ Any extensions enabled dynamically are only enabled for the current session. To Goose automatically detects when an extension is needed based on your task requirements. Here's an example of how Goose identifies and enables a needed extension during a conversation: - + #### Goose Prompt ```plaintext @@ -424,7 +424,7 @@ Great! Now I can help you query the database... ``` - + #### Goose Prompt ```plaintext @@ -457,7 +457,7 @@ extension_name: postgresql Goose responds to explicit requests for extensions, allowing users to manually enable specific tools they need. Here's an example of how Goose handles a direct request to enable an extension: - + #### Goose Prompt @@ -480,7 +480,7 @@ The PostgreSQL extension is now ready to use. What would you like to do with it? ``` - + #### Goose Prompt @@ -511,7 +511,7 @@ extension_name: postgresql Goose relies on extension properties to determine how to handle an extension. You can edit these properties if you want to change the extension's display settings and behavior, such as the name, timeout, or environment variables. - + 1. Click the button in the top-left to open the sidebar. 2. Click the `Extensions` button on the sidebar. @@ -534,7 +534,7 @@ Goose relies on extension properties to determine how to handle an extension. Yo You can remove installed extensions. - + 1. Click the button in the top-left to open the sidebar. 2. Click the `Extensions` button on the sidebar. diff --git a/documentation/docs/guides/goose-permissions.md b/documentation/docs/guides/goose-permissions.md index b842c26c459a..14c444d9fb9c 100644 --- a/documentation/docs/guides/goose-permissions.md +++ b/documentation/docs/guides/goose-permissions.md @@ -41,7 +41,7 @@ Goose’s permissions determine how much autonomy it has when modifying files, u Here's how to configure: - + You can change modes before or during a session and it will take effect immediately. @@ -58,7 +58,7 @@ Here's how to configure: - + diff --git a/documentation/docs/guides/interactive-chat/mcp-ui.md b/documentation/docs/guides/interactive-chat/mcp-ui.md index 1f7874b4c590..60517823f585 100644 --- a/documentation/docs/guides/interactive-chat/mcp-ui.md +++ b/documentation/docs/guides/interactive-chat/mcp-ui.md @@ -40,7 +40,7 @@ See how interactive responses work in Goose. For this exercise, we'll add an MCP-UI-enabled extension that connects to [MCP-UI Demos](https://mcp-aharvard.netlify.app/) provided by Andrew Harvard. - + - + - + Response Styles customize how tool interactions are displayed in the Goose Desktop chat window. To change this setting: @@ -30,7 +30,7 @@ To change this setting: This setting only affects the default state of tool calls in the conversation. You can always manually expand or collapse any tool call regardless of your chosen style. - + When working with the Goose CLI, you can control the verbosity of tool output. To adjust the tool output, run: diff --git a/documentation/docs/guides/managing-tools/tool-permissions.md b/documentation/docs/guides/managing-tools/tool-permissions.md index 7d33211de22e..f9f7fa527b8f 100644 --- a/documentation/docs/guides/managing-tools/tool-permissions.md +++ b/documentation/docs/guides/managing-tools/tool-permissions.md @@ -41,7 +41,7 @@ Each tool can be set to one of three permission levels: ## Configuring Tool Permissions - + You can configure fine-grained tool permissions for enabled extensions when using `Manual` or `Smart` approval mode. These rules can be accessed from the mode toggle or `Settings` page. @@ -64,7 +64,7 @@ Each tool can be set to one of three permission levels: - + 1. Run the configure command: ```sh diff --git a/documentation/docs/guides/managing-tools/tool-router.md b/documentation/docs/guides/managing-tools/tool-router.md index 6d576f7efd6b..12e737d37edc 100644 --- a/documentation/docs/guides/managing-tools/tool-router.md +++ b/documentation/docs/guides/managing-tools/tool-router.md @@ -58,7 +58,7 @@ When enabled, Goose uses LLM intelligence to analyze your query and select only ## Configuration - + 1. Click the button in the top-left to open the sidebar 2. Click the `Settings` button on the sidebar 3. Click the `Chat` tab @@ -66,7 +66,7 @@ When enabled, Goose uses LLM intelligence to analyze your query and select only - `Disabled` - Use the default tool selection strategy - `Enabled` - Use LLM-based intelligence to select tools - + 1. Run the configuration command: ```sh goose configure diff --git a/documentation/docs/guides/recipes/session-recipes.md b/documentation/docs/guides/recipes/session-recipes.md index 5b829f8d3a76..eb4486bb7a11 100644 --- a/documentation/docs/guides/recipes/session-recipes.md +++ b/documentation/docs/guides/recipes/session-recipes.md @@ -15,7 +15,7 @@ You can turn your current Goose session into a reusable recipe that includes the ## Create Recipe - + Create a recipe from the current session or from a template. @@ -54,7 +54,7 @@ You can turn your current Goose session into a reusable recipe that includes the - + 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 @@ -188,7 +188,7 @@ You can turn your current Goose session into a reusable recipe that includes the ## Edit Recipe - + 1. While in the session that's using the recipe, click the button at the bottom of the app 2. Click `View/Edit Recipe` @@ -205,7 +205,7 @@ You can turn your current Goose session into a reusable recipe that includes the - + Once the recipe file is created, you can open it with your preferred text editor and modify the value of any field. @@ -214,7 +214,7 @@ You can turn your current Goose session into a reusable recipe that includes the ## Use Recipe - + 1. Open the recipe using a direct link or manual URL entry, or from your Recipe library: @@ -256,7 +256,7 @@ You can turn your current Goose session into a reusable recipe that includes the ::: - + Using a recipe with the Goose CLI might involve the following tasks: - [Configuring your recipe location](#configure-recipe-location) @@ -428,10 +428,10 @@ You can turn your current Goose session into a reusable recipe that includes the ## Validate Recipe - + Recipe validation is only available through the CLI. - + Validate your recipe file to ensure it's properly configured. Validation verifies that: - All required fields are present - Parameters are properly formatted @@ -465,7 +465,7 @@ Each recipient gets their own private session when using your shared recipe. No You can share a recipe with Desktop users via a recipe link. - + Copy the deeplink from your Recipe Library to share with others: 1. Click the button in the top-left to open the sidebar 2. Click `Recipes` in the sidebar @@ -473,7 +473,7 @@ You can share a recipe with Desktop users via a recipe link. 4. Under `Deeplink`, click `Copy` - + Generate a deeplink from your recipe file to share with others: ```sh goose recipe deeplink @@ -491,7 +491,7 @@ You can share a recipe with Desktop or CLI users by sending the recipe file dire ## Schedule Recipe - + Automate Goose recipes by running them on a schedule. 1. Click the button in the top-left to open the sidebar @@ -512,7 +512,7 @@ Automate Goose recipes by running them on a schedule. At the bottom of the `Schedule Details` page you can view the list of sessions created by the scheduled recipe and open or restore each session. - + Automate Goose recipes by scheduling them to run with a [cron expression](https://en.wikipedia.org/wiki/Cron#Cron_expression). ```bash diff --git a/documentation/docs/guides/recipes/storing-recipes.md b/documentation/docs/guides/recipes/storing-recipes.md index 08ff346256ea..ebe5271f961d 100644 --- a/documentation/docs/guides/recipes/storing-recipes.md +++ b/documentation/docs/guides/recipes/storing-recipes.md @@ -40,7 +40,7 @@ Before saving recipes, it's important to understand where they can be stored and ## Storing Recipes - + **Save New Recipe:** @@ -60,7 +60,7 @@ When you modify and save a recipe with a new name, a new recipe and new link are ::: - + When you [create a recipe](/docs/guides/recipes/recipe-reference), it gets saved to: @@ -74,7 +74,7 @@ When you modify and save a recipe with a new name, a new recipe and new link are ### Importing Recipes - + Import a recipe using its deeplink or YAML file: **Import via Recipe Link:** @@ -96,7 +96,7 @@ When you modify and save a recipe with a new name, a new recipe and new link are Importing JSON recipe files isn't currently supported. - + Recipe import is only available in Goose Desktop. @@ -104,7 +104,7 @@ When you modify and save a recipe with a new name, a new recipe and new link are ## Finding Your Recipes - + **Access Recipe Library:** 1. Click the button in the top-left to open the sidebar @@ -113,7 +113,7 @@ When you modify and save a recipe with a new name, a new recipe and new link are 4. Each recipe shows its title, description, and whether it's global or local - + To find and configure your saved recipes: @@ -139,7 +139,7 @@ Set up [custom recipe paths](/docs/guides/recipes/session-recipes#configure-reci ## Using Saved Recipes - + 1. Click the button in the top-left to open the sidebar 2. Click `Recipes` @@ -149,7 +149,7 @@ Set up [custom recipe paths](/docs/guides/recipes/session-recipes#configure-reci - Click `Preview` to see the recipe details first, then click **Load Recipe** to run it - + Once you've located your recipe file, [run the recipe](/docs/guides/recipes/session-recipes#run-a-recipe) or [open it in goose desktop](/docs/guides/goose-cli-commands#recipe). diff --git a/documentation/docs/guides/security/prompt-injection-detection.md b/documentation/docs/guides/security/prompt-injection-detection.md index 38a2ca170522..2afe6d91ff64 100644 --- a/documentation/docs/guides/security/prompt-injection-detection.md +++ b/documentation/docs/guides/security/prompt-injection-detection.md @@ -53,7 +53,7 @@ When in doubt, deny. ## Enabling Detection - + 1. Click the button in the top-left to open the sidebar 2. Click `Settings` on the sidebar diff --git a/documentation/docs/guides/sessions/in-session-actions.md b/documentation/docs/guides/sessions/in-session-actions.md index f1c97b14eb3a..0c54f44f6496 100644 --- a/documentation/docs/guides/sessions/in-session-actions.md +++ b/documentation/docs/guides/sessions/in-session-actions.md @@ -22,7 +22,7 @@ This is useful when: - You want to try different approaches to a problem without starting a new session - + 1. Hover over any of your previous messages to reveal the edit button 2. Click the edit button that appears @@ -57,7 +57,7 @@ This is useful when: - **When to Edit vs. Interrupt**: Editing earlier messages when a conversation has gone off track can be more effective than trying to correct course using new messages or [interruptions](#interrupt-task). By editing messages, you rewrite history. With interruptions, you only affect the conversation from the current message onwards. - + Message editing is not available in the Goose CLI. @@ -75,7 +75,7 @@ Goose may perform better when complex tasks are split into subtasks, a technique ::: - + Add a message to the queue: 1. While Goose is processing a response, type your next message 2. Press `Enter` to add it to the queue (or interrupts if using [interruption keywords](#interrupt-task)) @@ -117,7 +117,7 @@ Goose may perform better when complex tasks are split into subtasks, a technique Each task builds on the previous one. - + Message queuing is not available in the Goose CLI. @@ -131,7 +131,7 @@ Interrupt Goose while it's processing a task to take control of the conversation - You want to switch to a completely different task - + There are two ways to interrupt a task: @@ -184,7 +184,7 @@ Interrupt Goose while it's processing a task to take control of the conversation - + 1. Press `Ctrl+C` to interrupt the current task 2. Type your prompt that provides more context or changes direction 3. Press `Enter` @@ -198,7 +198,7 @@ Interrupt Goose while it's processing a task to take control of the conversation Speak to Goose directly instead of typing your prompts. - + To enable voice dictation: 1. Click the button in the top-left to open the sidebar 2. Click `Settings` in the sidebar @@ -222,7 +222,7 @@ Speak to Goose directly instead of typing your prompts. * Recordings are not stored locally after transcription - + Voice dictation is not available in the Goose CLI. @@ -232,7 +232,7 @@ Speak to Goose directly instead of typing your prompts. Provide Goose with context from your codebase, documents, and other files to get more relevant and accurate assistance. - + Share files with Goose in several ways: 1. **Drag and Drop**: Simply drag files from your computer's file explorer/finder and drop them anywhere in the chat window. The file paths will be automatically added to your message. @@ -243,7 +243,7 @@ Provide Goose with context from your codebase, documents, and other files to get 4. **Quick File Search**: Use the [`@` shortcut key](/docs/guides/file-management#quick-file-search-in-goose-desktop) to quickly find and include files - + You can reference files by their paths directly in your messages. Since you're already in a terminal, you can use standard shell commands to help with file paths: ```bash diff --git a/documentation/docs/guides/sessions/session-management.md b/documentation/docs/guides/sessions/session-management.md index d7ae010356ec..021e46c745df 100644 --- a/documentation/docs/guides/sessions/session-management.md +++ b/documentation/docs/guides/sessions/session-management.md @@ -17,7 +17,7 @@ In your first session, Goose prompts you to [set up an LLM (Large Language Model ::: - + When you open Goose, you'll see the session interface ready for use. Just type—[or speak](/docs/guides/sessions/in-session-actions#voice-dictation "Learn how to enable voice dictation")—your questions, requests, or instructions directly into the input field, and Goose will immediately get to work. When you're ready to work on a new task, you can start a new session in the same directory or a different one. This directory is where Goose reads and writes files by default. @@ -59,7 +59,7 @@ In your first session, Goose prompts you to [set up an LLM (Large Language Model | Toggle Sidebar | `Cmd+B` | `Ctrl+B` | - + From your terminal, navigate to the directory from which you'd like to start, and run the [session](/docs/guides/goose-cli-commands#session-options) command: ```sh goose session @@ -74,7 +74,7 @@ In your first session, Goose prompts you to [set up an LLM (Large Language Model ## Name Session - + In the Desktop app, session tiles display auto-generated descriptions based on the context of your initial prompt. You can edit session descriptions after they're created: @@ -94,7 +94,7 @@ In your first session, Goose prompts you to [set up an LLM (Large Language Model ::: - + By default, Goose names your session using the current timestamp in the format `YYYYMMDD_HHMMSS`. If you'd like to provide a specific name, this is where you'd do so. For example to name your session `react-migration`, you would run: ``` @@ -113,10 +113,10 @@ In your first session, Goose prompts you to [set up an LLM (Large Language Model ## Exit Session Note that sessions are automatically saved when you exit. - + To exit a session, simply close the application. - + To exit a session, type `exit`. Alternatively, you exit the session by holding down `Ctrl+C`. Your session will be stored locally in `~/.local/share/goose/sessions`. @@ -128,7 +128,7 @@ Note that sessions are automatically saved when you exit. Search allows you to find specific content within sessions or find specific sessions. - + You can use keyboard shortcuts and search bar buttons to search sessions in Goose Desktop. @@ -183,7 +183,7 @@ Search allows you to find specific content within sessions or find specific sess ::: - + Search functionality is provided by your terminal interface. Use the appropriate shortcut for your environment: @@ -231,7 +231,7 @@ Search allows you to find specific content within sessions or find specific sess ## Resume Session - + 1. Click the button in the top-left to open the sidebar 2. Click `History` in the sidebar 3. Click the session you'd like to resume. Goose provides [search features](#search-sessions) to help you find the session. @@ -244,7 +244,7 @@ Search allows you to find specific content within sessions or find specific sess ::: - + To resume your latest session, you can run the following command: ``` @@ -273,7 +273,7 @@ Search allows you to find specific content within sessions or find specific sess You can resume a CLI session in Desktop. - + All saved sessions are listed in the Desktop app, even CLI sessions. To resume a CLI session within the Desktop: 1. Click the button in the top-left to open the sidebar @@ -284,7 +284,7 @@ You can resume a CLI session in Desktop. - Click `New Window` to open in a new window - + Currently, you cannot resume a Desktop session within the CLI. @@ -292,10 +292,10 @@ You can resume a CLI session in Desktop. ### Resume Project-Based Sessions - + Project-based sessions are only available through the CLI. - + You can use the [`project`](/docs/guides/goose-cli-commands#project) and [`projects`](/docs/guides/goose-cli-commands#projects) commands to start or resume sessions from a project, which is a tracked working directory with session metadata. For a complete guide to using Projects, see [Managing Projects Guide](/docs/guides/managing-projects). @@ -303,7 +303,7 @@ You can resume a CLI session in Desktop. ## Delete Sessions - + You can delete sessions directly from the Desktop app: 1. Click the button in the top-left to open the sidebar @@ -319,7 +319,7 @@ You can resume a CLI session in Desktop. The session will be immediately removed from your session history and the underlying session file will be deleted from your local storage. - + You can remove sessions using CLI commands. For detailed instructions on session removal, see the [CLI Commands documentation](/docs/guides/goose-cli-commands#session-remove-options). @@ -329,10 +329,10 @@ You can resume a CLI session in Desktop. Export sessions to Markdown to share with your team, create documentation, archive conversations, or review them in a readable format. - + Session export is currently only available through the CLI. - + Export sessions using the `export` subcommand: ```bash diff --git a/documentation/docs/guides/sessions/smart-context-management.md b/documentation/docs/guides/sessions/smart-context-management.md index e87f8232e7ad..ff67cf79694d 100644 --- a/documentation/docs/guides/sessions/smart-context-management.md +++ b/documentation/docs/guides/sessions/smart-context-management.md @@ -45,7 +45,7 @@ When you reach the auto-compaction threshold: You can also trigger compaction manually before reaching context or token limits: - + 1. Point to the token usage indicator dot next to the model name at the bottom of the app 2. Click `Compact now` in the context window that appears @@ -57,7 +57,7 @@ You can also trigger compaction manually before reaching context or token limits ::: - + To proactively trigger summarization before reaching context limits, use the `/summarize` command: @@ -86,12 +86,12 @@ When auto-compaction is disabled, or if a conversation still exceeds the context | **Prompt** | Asks user to choose from the above options | Control over each decision in interactive sessions | CLI only | Depends on choice made | - + Goose Desktop exclusively uses summarization by compacting the conversation to manage context, preserving key information while reducing size. - + The CLI supports all context limit strategies: `summarize`, `truncate`, `clear`, and `prompt`. @@ -162,7 +162,7 @@ This feature gives you control over agent autonomy and prevents infinite loops a This setting is stored as the `GOOSE_MAX_TURNS` environment variable in your [config.yaml file](/docs/guides/config-file). You can configure it using the Desktop app or CLI. - + 1. Click the button in the top-left to open the sidebar 2. Click the `Settings` button on the sidebar @@ -170,7 +170,7 @@ This setting is stored as the `GOOSE_MAX_TURNS` environment variable in your [co 4. Scroll to `Conversation Limits` and enter a value for `Max Turns` - + 1. Run the `configuration` command: ```sh @@ -253,7 +253,7 @@ Remember that even simple-seeming tasks often require multiple turns. For exampl After sending your first message, Goose Desktop and Goose CLI display token usage. - + The Desktop displays a colored circle next to the model name at the bottom of the session window. The color provides a visual indicator of your token usage for the session. - **Green**: Normal usage - Plenty of context space available - **Orange**: Warning state - Approaching limit (80% of capacity) @@ -266,7 +266,7 @@ After sending your first message, Goose Desktop and Goose CLI display token usag - A progress bar showing your current token usage - + The CLI displays a context label above each command prompt, showing: - A visual indicator using dots (●○) and colors to represent your token usage: - **Green**: Below 50% usage @@ -311,12 +311,12 @@ Goose resolves context limits with the following precedence (highest to lowest): **Configuration** - + Model context limit overrides are not yet available in the Goose Desktop app. - + Context limit overrides only work as [environment variables](/docs/guides/environment-variables#model-context-limit-overrides), not in the config file. @@ -361,7 +361,7 @@ export GOOSE_PLANNER_CONTEXT_LIMIT=1000000 Display real-time estimated costs of your session. - + To manage live cost tracking: 1. Click the button in the top-left to open the sidebar 2. Click the `Settings` button on the sidebar @@ -374,7 +374,7 @@ Pricing data is regularly fetched from the OpenRouter API and cached locally. Th These costs are estimates only, and not connected to your actual provider bill. The cost shown is an approximation based on token counts and public pricing data. - + Show estimated cost in the Goose CLI by setting the `GOOSE_CLI_SHOW_COST` [environment variable](/docs/guides/environment-variables.md#session-management) or including it in the [configuration file](/docs/guides/config-file.md). ``` diff --git a/documentation/docs/guides/updating-goose.md b/documentation/docs/guides/updating-goose.md index d74479206a2d..466b5a7a6845 100644 --- a/documentation/docs/guides/updating-goose.md +++ b/documentation/docs/guides/updating-goose.md @@ -15,7 +15,7 @@ The Goose CLI and desktop apps are under active and continuous development. To g - + :::info To update Goose to the latest stable version, reinstall using the instructions below ::: @@ -27,7 +27,7 @@ The Goose CLI and desktop apps are under active and continuous development. To g 5. Run the executable file to launch the Goose desktop application. - + You can update Goose by running: ```sh @@ -61,7 +61,7 @@ The Goose CLI and desktop apps are under active and continuous development. To g - + :::info To update Goose to the latest stable version, reinstall using the instructions below ::: @@ -76,7 +76,7 @@ The Goose CLI and desktop apps are under active and continuous development. To g - + You can update Goose by running: ```sh @@ -110,7 +110,7 @@ The Goose CLI and desktop apps are under active and continuous development. To g - + :::info To update Goose to the latest stable version, reinstall using the instructions below ::: @@ -122,7 +122,7 @@ The Goose CLI and desktop apps are under active and continuous development. To g 5. Run the executable file to launch the Goose Desktop application. - + You can update Goose by running: ```sh diff --git a/documentation/docs/guides/using-goosehints.md b/documentation/docs/guides/using-goosehints.md index abb11e224ee8..1ac6381d0144 100644 --- a/documentation/docs/guides/using-goosehints.md +++ b/documentation/docs/guides/using-goosehints.md @@ -43,7 +43,7 @@ You can use other agent rule files with Goose by using the [`CONTEXT_FILE_NAMES` ::: - + #### Global hints file 1. Create a `.goosehints` file in `~/.config/goose`. diff --git a/documentation/docs/mcp/_template_.mdx b/documentation/docs/mcp/_template_.mdx index 343bfe1d74e2..af9e836cbc3d 100644 --- a/documentation/docs/mcp/_template_.mdx +++ b/documentation/docs/mcp/_template_.mdx @@ -18,10 +18,10 @@ This tutorial covers how to add the [{Extension Name} MCP Server](/) as a Goose :::tip TLDR - + [Launch the installer]({goose_url}) - + **Command** ```sh {command} @@ -37,7 +37,7 @@ This tutorial covers how to add the [{Extension Name} MCP Server](/) as a Goose ## Configuration - + - + _exact prompt_ -### Goose Output +### goose Output :::note Desktop {exact output} -::: \ No newline at end of file +::: diff --git a/documentation/docs/mcp/context7-mcp.mdx b/documentation/docs/mcp/context7-mcp.mdx index d2eaf4297cec..a3f87b04dc7b 100644 --- a/documentation/docs/mcp/context7-mcp.mdx +++ b/documentation/docs/mcp/context7-mcp.mdx @@ -17,10 +17,10 @@ This tutorial covers how to add the [Context7 MCP Server](https://github.com/ups :::tip TLDR - + [Launch the installer](goose://extension?cmd=npx&arg=-y&arg=%40upstash%2Fcontext7-mcp&id=context7&name=Context7&description=Context7%20MCP%20server%20for%20up-to-date%20code%20and%20docs) - + **Command** ```sh npx -y @upstash/context7-mcp @@ -47,10 +47,10 @@ This tutorial covers how to add the [Context7 MCP Server](https://github.com/ups In this example, Goose uses Context7 to pull real-time docs, compare tools, and scaffold a modern app using only the latest, official implementation patterns. - - 1. Open a new session in Goose Desktop + + 1. Open a new session in goose Desktop - + 1. Open a terminal and start a new Goose session: @@ -156,4 +156,4 @@ Type safety across the stack Would you like me to explain any part in more detail or help you implement specific features? -::: \ No newline at end of file +::: diff --git a/documentation/docs/tutorials/isolated-development-environments.md b/documentation/docs/tutorials/isolated-development-environments.md index 2a6c0ce082bf..9c88dae5ee9a 100644 --- a/documentation/docs/tutorials/isolated-development-environments.md +++ b/documentation/docs/tutorials/isolated-development-environments.md @@ -41,7 +41,7 @@ Click this link to automatically add the extension to Goose: ### Method 2: Manual Configuration - + 1. Click `...` in the top right corner of the Goose Desktop. 2. Select `Advanced Settings` from the menu. @@ -56,7 +56,7 @@ Click this link to automatically add the extension to Goose: 5. Click `Add` button - + 1. Run the configuration command: ```bash diff --git a/documentation/docs/tutorials/lead-worker.md b/documentation/docs/tutorials/lead-worker.md index 080f2b9dd09e..3f17251d13b1 100644 --- a/documentation/docs/tutorials/lead-worker.md +++ b/documentation/docs/tutorials/lead-worker.md @@ -58,14 +58,14 @@ Ensure you have [added the LLMs to Goose](/docs/getting-started/providers) ::: - + 1. Click the model name at the bottom of the Goose Desktop window 2. Click **Lead/Worker Settings** 3. Check the box to **Enable lead/worker mode** 4. Select your **Lead Model** and **Worker Model** from the dropdown menus 5. (Optional) Change the default number of **initial lead turns**, the **failure threshold** before switching back to the leavd model, or the number of **fallback turns** to use the lead model during fallback - + The only required configuration is setting the `GOOSE_LEAD_MODEL` [environment variable](/docs/guides/environment-variables#leadworker-model-configuration): ```bash