# How to Get Support for Goose: Diagnostics, Discord, and GitHub Issues > Get expert Goose support by generating diagnostics and sharing on Discord or GitHub. Resolve issues quickly and effectively with our community and developers. - Repository: [goose/goose](https://github.com/aaif-goose/goose) - Tags: getting-started - Published: 2026-04-07 --- **To get support for Goose, use the built-in `diagnostics` command to generate a ZIP bundle of your system details, then share it via the Discord server for real-time help or open a GitHub Issue for persistent bug tracking.** Goose is an open-source AI agent framework developed by aaif-goose. When you encounter issues or need assistance, the project provides structured support channels that leverage automated diagnostic collection and an active community ecosystem. ## Generate a Diagnostics Bundle The fastest way to prepare a support request is using the **built-in diagnostics command**. This CLI feature captures your system information, session logs, and configuration files into a single ZIP archive that maintainers can analyze. The diagnostic flow is implemented in [`crates/goose/src/session/diagnostics.rs`](https://github.com/aaif-goose/goose/blob/main/crates/goose/src/session/diagnostics.rs) and exposed through the CLI interface in [`crates/goose-cli/src/commands/session.rs`](https://github.com/aaif-goose/goose/blob/main/crates/goose-cli/src/commands/session.rs). If you are running the server, the OpenAPI endpoint at `/diagnostics/{session_id}` is defined in [`crates/goose-server/src/routes/status.rs`](https://github.com/aaif-goose/goose/blob/main/crates/goose-server/src/routes/status.rs). Run the following to create a diagnostics package: ```bash # Generate a diagnostics bundle for a specific session goose diagnostics my-session-id # Specify a custom output path goose diagnostics my-session-id --output ./my-diagnostics.zip ``` Attach this ZIP file to your GitHub issue or upload it when asking for help on Discord. ## Join the Community Discord Server For **real-time support** and quick questions, the Goose Discord server is the primary channel. The repository's [`README.md`](https://github.com/aaif-goose/goose/blob/main/README.md) prominently displays a Discord badge, and the troubleshooting documentation consistently references Discord as the fastest way to get help. According to the [`documentation/docs/troubleshooting/known-issues.md`](https://github.com/aaif-goose/goose/blob/main/documentation/docs/troubleshooting/known-issues.md) file, the community actively monitors Discord for diagnostic reports and configuration questions. ## File Issues on GitHub For **persistent, searchable issue tracking**, open a new issue in the aaif-goose/goose repository. The [`CONTRIBUTING.md`](https://github.com/aaif-goose/goose/blob/main/CONTRIBUTING.md) file explicitly encourages users to file issues for bugs or feature requests after gathering diagnostics. When filing an issue, include: - A clear title describing the problem - Steps to reproduce - The diagnostics ZIP generated from your session ## Consult the Troubleshooting Documentation The project maintains dedicated troubleshooting guides that explain how to generate diagnostics and where to share them. The [`documentation/docs/troubleshooting/diagnostics-and-reporting.md`](https://github.com/aaif-goose/goose/blob/main/documentation/docs/troubleshooting/diagnostics-and-reporting.md) page provides step-by-step instructions for the support workflow. For common problems, check [`documentation/docs/troubleshooting/known-issues.md`](https://github.com/aaif-goose/goose/blob/main/documentation/docs/troubleshooting/known-issues.md) before opening a new support request. ## Summary - **Run `goose diagnostics `** to collect system data, logs, and configuration into a ZIP file. - **Share the bundle on Discord** for immediate feedback from the community and maintainers. - **Open GitHub Issues** for bugs or feature requests that require long-term tracking. - **Reference the troubleshooting docs** for step-by-step guidance on the support process. ## Frequently Asked Questions ### How do I generate a diagnostics bundle in Goose? Use the CLI command `goose diagnostics ` which is implemented in [`crates/goose-cli/src/commands/session.rs`](https://github.com/aaif-goose/goose/blob/main/crates/goose-cli/src/commands/session.rs). This creates a ZIP archive containing system information and session logs that you can attach to support requests. ### Where should I post my Goose diagnostics file? Post the diagnostics ZIP to either the Discord server for quick troubleshooting or attach it to a new GitHub Issue for persistent tracking. The Discord link is available in the [`README.md`](https://github.com/aaif-goose/goose/blob/main/README.md) badge, while issues should follow the guidelines in [`CONTRIBUTING.md`](https://github.com/aaif-goose/goose/blob/main/CONTRIBUTING.md). ### Does Goose have a Discord server for support? Yes. The Discord server is the primary real-time support channel, referenced throughout the documentation including the root [`README.md`](https://github.com/aaif-goose/goose/blob/main/README.md) and the troubleshooting guides. It is the recommended venue for questions that do not require formal issue tracking. ### What information is included in a Goose diagnostics ZIP? The diagnostics bundle includes system information, session logs, and configuration files collected by the logic in [`crates/goose/src/session/diagnostics.rs`](https://github.com/aaif-goose/goose/blob/main/crates/goose/src/session/diagnostics.rs). This provides maintainers with the context needed to reproduce and diagnose your issue.