Guides

📄️ Managing Projects

Goose Projects automatically track your working directories and associated sessions, making it easy to resume work across multiple codebases with full context preservation.

📄️ Updating Goose

The Goose CLI and desktop apps are under active and continuous development. To get the newest features and fixes, you should periodically update your Goose client using the following instructions.

Goose’s permissions determine how much autonomy it has when modifying files, using extensions, and performing automated actions. By selecting a permission mode, you have full control over how Goose interacts with your development environment.

📄️ Quick Tips

Best practices for working with Goose

📄️ CLI Commands

Goose provides a command-line interface (CLI) with several commands for managing sessions, configurations and extensions. This guide covers all available CLI commands and interactive session features.

📄️ Using Goosehints

.goosehints is a text file used to provide additional context about your project and improve the communication with Goose. The use of goosehints ensures that Goose understands your requirements better and can execute tasks more effectively.

📄️ CLI Providers

Use Claude Code, Cursor Agent, or Gemini CLI subscriptions in Goose

📄️ Subagents

Subagents are independent instances that execute tasks while keeping your main conversation clean and focused. They bring process isolation and context preservation by offloading work to separate instances. Think of them as temporary assistants that handle specific jobs without cluttering your chat with tool execution details.

🗃️ Rich Interactive Chat

1 item

📄️ LLM Rate Limits

Rate limiting is the process of restricting the number of requests a user or application can send to an LLM API within a specific timeframe. LLM providers enforce this with the purpose of managing resources and preventing abuse.

📄️ Logging System

Goose uses a unified storage system for conversations and interactions. All conversations and interactions (both CLI and Desktop) are stored locally in the following locations:

📄️ File Management

Efficiently find and reference files in Goose Desktop and follow best practices for safe file operations

📄️ Run Tasks

When working with the Goose CLI, you can pass files and instructions to the goose run command to execute tasks and workflows. This could be a simple one-liner command or a complex set of instructions stored in a file.

📄️ Using Gooseignore

.gooseignore is a text file that defines patterns for files and directories that Goose will not access. This means Goose cannot read, modify, delete, or run shell commands on these files when using the Developer extension's tools.

📄️ Configuration File

Goose uses a YAML configuration file to manage settings and extensions. This file is located at:

📄️ 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).

📄️ Environment Variables

Goose supports various environment variables that allow you to customize its behavior. This guide provides a comprehensive list of available environment variables grouped by their functionality.

🗃️ Multi-Model Config

Configure multiple models and providers for model-switching strategies.

📄️ Goose in ACP Clients

Client applications that support the Agent Client Protocol (ACP) can connect natively to Goose. This integration allows you to seamlessly interact with Goose directly from the client.

📄️ Enhanced Code Editing

Use AI models to intelligently apply code changes

🗃️ Managing Sessions

🗃️ Recipes