more lowercasing of TabItem labels (#5307)
This commit is contained in:
@@ -41,7 +41,7 @@ Goose’s permissions determine how much autonomy it has when modifying files, u
|
||||
Here's how to configure:
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
You can change modes before or during a session and it will take effect immediately.
|
||||
|
||||
@@ -58,7 +58,7 @@ Here's how to configure:
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
<Tabs groupId="method">
|
||||
<TabItem value="session" label="In Session" default>
|
||||
|
||||
@@ -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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
<GooseDesktopInstaller
|
||||
extensionId="richdemo"
|
||||
extensionName="Rich Demo"
|
||||
@@ -49,7 +49,7 @@ For this exercise, we'll add an MCP-UI-enabled extension that connects to [MCP-U
|
||||
url="https://mcp-aharvard.netlify.app/mcp"
|
||||
/>
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
<CLIExtensionInstructions
|
||||
name="rich_demo"
|
||||
type="http"
|
||||
|
||||
@@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem';
|
||||
import { PanelLeft } from 'lucide-react';
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
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.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
When working with the Goose CLI, you can control the verbosity of tool output.
|
||||
|
||||
To adjust the tool output, run:
|
||||
|
||||
@@ -41,7 +41,7 @@ Each tool can be set to one of three permission levels:
|
||||
## Configuring Tool Permissions
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
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.
|
||||
|
||||
<Tabs>
|
||||
@@ -64,7 +64,7 @@ Each tool can be set to one of three permission levels:
|
||||
</Tabs>
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
1. Run the configure command:
|
||||
```sh
|
||||
|
||||
@@ -58,7 +58,7 @@ When enabled, Goose uses LLM intelligence to analyze your query and select only
|
||||
## Configuration
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
1. Run the configuration command:
|
||||
```sh
|
||||
goose configure
|
||||
|
||||
@@ -15,7 +15,7 @@ You can turn your current Goose session into a reusable recipe that includes the
|
||||
## Create Recipe
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
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
|
||||
|
||||
</TabItem>
|
||||
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
1. While in the session that's using the recipe, click the <Bot className="inline" size={16} /> 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
|
||||
|
||||
</TabItem>
|
||||
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Once the recipe file is created, you can open it with your preferred text editor and modify the value of any field.
|
||||
|
||||
</TabItem>
|
||||
@@ -214,7 +214,7 @@ You can turn your current Goose session into a reusable recipe that includes the
|
||||
## Use Recipe
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
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
|
||||
:::
|
||||
</TabItem>
|
||||
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
Recipe validation is only available through the CLI.
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose 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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
Copy the deeplink from your Recipe Library to share with others:
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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`
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Generate a deeplink from your recipe file to share with others:
|
||||
```sh
|
||||
goose recipe deeplink <FILE>
|
||||
@@ -491,7 +491,7 @@ You can share a recipe with Desktop or CLI users by sending the recipe file dire
|
||||
|
||||
## Schedule Recipe
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
Automate Goose recipes by running them on a schedule.
|
||||
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Automate Goose recipes by scheduling them to run with a [cron expression](https://en.wikipedia.org/wiki/Cron#Cron_expression).
|
||||
|
||||
```bash
|
||||
|
||||
@@ -40,7 +40,7 @@ Before saving recipes, it's important to understand where they can be stored and
|
||||
## Storing Recipes
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="desktop" label="Goose Desktop" default>
|
||||
<TabItem value="desktop" label="goose Desktop" default>
|
||||
|
||||
**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
|
||||
:::
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="desktop" label="Goose Desktop" default>
|
||||
<TabItem value="desktop" label="goose Desktop" default>
|
||||
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.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Recipe import is only available in Goose Desktop.
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
@@ -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
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="desktop" label="Goose Desktop" default>
|
||||
<TabItem value="desktop" label="goose Desktop" default>
|
||||
|
||||
**Access Recipe Library:**
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="desktop" label="Goose Desktop" default>
|
||||
<TabItem value="desktop" label="goose Desktop" default>
|
||||
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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).
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ When in doubt, deny.
|
||||
## Enabling Detection
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="goose desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
1. Click the <PanelLeft className="inline" size={16} /> button in the top-left to open the sidebar
|
||||
2. Click `Settings` on the sidebar
|
||||
|
||||
@@ -22,7 +22,7 @@ This is useful when:
|
||||
- You want to try different approaches to a problem without starting a new session
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
1. Hover over any of your previous messages to reveal the edit button
|
||||
2. Click the <Edit2 className="inline" size={16} /> 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.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Message editing is not available in the Goose CLI.
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
@@ -75,7 +75,7 @@ Goose may perform better when complex tasks are split into subtasks, a technique
|
||||
:::
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
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.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Message queuing is not available in the Goose CLI.
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
@@ -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
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
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
|
||||
</details>
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
To enable voice dictation:
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Voice dictation is not available in the Goose CLI.
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
@@ -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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
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
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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
|
||||
|
||||
@@ -17,7 +17,7 @@ In your first session, Goose prompts you to [set up an LLM (Large Language Model
|
||||
:::
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
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` |
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
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
|
||||
:::
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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.
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
To exit a session, simply close the application.
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
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
|
||||
:::
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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
|
||||
:::
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
All saved sessions are listed in the Desktop app, even CLI sessions. To resume a CLI session within the Desktop:
|
||||
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Currently, you cannot resume a Desktop session within the CLI.
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
@@ -292,10 +292,10 @@ You can resume a CLI session in Desktop.
|
||||
### Resume Project-Based Sessions
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
Project-based sessions are only available through the CLI.
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose 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).
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
@@ -303,7 +303,7 @@ You can resume a CLI session in Desktop.
|
||||
## Delete Sessions
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
You can delete sessions directly from the Desktop app:
|
||||
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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.
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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).
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
@@ -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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
Session export is currently only available through the CLI.
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
Export sessions using the `export` subcommand:
|
||||
|
||||
```bash
|
||||
|
||||
@@ -45,7 +45,7 @@ When you reach the auto-compaction threshold:
|
||||
You can also trigger compaction manually before reaching context or token limits:
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
1. Point to the token usage indicator dot next to the model name at the bottom of the app
|
||||
2. Click <ScrollText className="inline" size={16} /> `Compact now` in the context window that appears
|
||||
@@ -57,7 +57,7 @@ You can also trigger compaction manually before reaching context or token limits
|
||||
:::
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI" default>
|
||||
<TabItem value="cli" label="goose CLI" default>
|
||||
|
||||
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 |
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
Goose Desktop exclusively uses summarization by compacting the conversation to manage context, preserving key information while reducing size.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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`
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
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
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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**
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
Model context limit overrides are not yet available in the Goose Desktop app.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
|
||||
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.
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
To manage live cost tracking:
|
||||
1. Click the <PanelLeft className="inline" size={16} /> 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.
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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).
|
||||
|
||||
```
|
||||
|
||||
@@ -15,7 +15,7 @@ The Goose CLI and desktop apps are under active and continuous development. To g
|
||||
<Tabs>
|
||||
<TabItem value="mac" label="macOS" default>
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
:::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.
|
||||
</div>
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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
|
||||
|
||||
<TabItem value="linux" label="Linux">
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
:::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
|
||||
|
||||
</div>
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
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
|
||||
|
||||
<TabItem value="windows" label="Windows">
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
:::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.
|
||||
</div>
|
||||
</TabItem>
|
||||
<TabItem value="cli" label="Goose CLI">
|
||||
<TabItem value="cli" label="goose CLI">
|
||||
You can update Goose by running:
|
||||
|
||||
```sh
|
||||
|
||||
@@ -43,7 +43,7 @@ You can use other agent rule files with Goose by using the [`CONTEXT_FILE_NAMES`
|
||||
:::
|
||||
|
||||
<Tabs groupId="interface">
|
||||
<TabItem value="ui" label="Goose Desktop" default>
|
||||
<TabItem value="ui" label="goose Desktop" default>
|
||||
|
||||
#### Global hints file
|
||||
1. Create a `.goosehints` file in `~/.config/goose`.
|
||||
|
||||
Reference in New Issue
Block a user