docs: update Discord invite (#10863)

Co-authored-by: Douwe M Osinga <douwe@sidewalklabs.com> Co-authored-by: Jasper Hugo <jasper@jasperhugo.com>
2026-08-01 00:49:19 +02:00
parent 83ee4efcf7
commit 0f32f8d0a9
51 changed files with 58 additions and 58 deletions
@@ -74,7 +74,7 @@ The list of experimental features may change as goose development progresses. So
    <Card 
      title="Discord Community"
      description="Join our community to discuss experimental features, share feedback, and connect with other users."
-      link="https://discord.gg/goose-oss"
+      link="https://discord.gg/n8R5VaWDAn"
    />
  </div>
 </div>
@@ -1571,7 +1571,7 @@ Reasoning output can be useful for understanding how the model arrived at its an

 ---

-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/aaif-goose/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/n8R5VaWDAn) or on the [goose repo](https://github.com/aaif-goose/goose).


 [providers]: /docs/getting-started/providers
@@ -274,7 +274,7 @@ If you encounter issues:

 1. Check the [Cloudflare MCP Server repository](https://github.com/cloudflare/mcp-server-cloudflare) for documentation
 2. Review [Cloudflare API documentation](https://developers.cloudflare.com/api/)
-3. Join our [Discord community](https://discord.gg/goose-oss) for support
+3. Join our [Discord community](https://discord.gg/n8R5VaWDAn) for support
 4. Check [Cloudflare Community](https://community.cloudflare.com/) for platform-specific help

 ## Next Steps
@@ -144,4 +144,4 @@ After completing tutorials, you can:
 ### Need Further Help? 
 If you have questions, run into issues, or just need to brainstorm ideas join the [Discord Community][discord]!

-[discord]: https://discord.gg/goose-oss
+[discord]: https://discord.gg/n8R5VaWDAn
@@ -44,7 +44,7 @@ import styles from '@site/src/components/Card/styles.module.css';
    <Card 
      title="Discord Community"
      description="Join our active Discord server for real-time help, discussions, and community support from goose users and maintainers."
-      link="https://discord.gg/goose-oss"
+      link="https://discord.gg/n8R5VaWDAn"
    />
    <Card 
      title="GitHub Issues"
@@ -7,7 +7,7 @@ description: Comprehensive troubleshooting guide for common goose problems with
 goose, like any system, may run into occasional issues. This guide provides solutions for common problems.

 :::tip Need help with an issue not listed here?
-Our [Discord community](https://discord.gg/goose-oss) is here to help! For the fastest support, consider generating a [diagnostic report](/docs/troubleshooting/diagnostics-and-reporting) - it helps us understand your setup quickly.
+Our [Discord community](https://discord.gg/n8R5VaWDAn) is here to help! For the fastest support, consider generating a [diagnostic report](/docs/troubleshooting/diagnostics-and-reporting) - it helps us understand your setup quickly.
 :::

 ### goose Edits Files
@@ -523,7 +523,7 @@ If you can share a [diagnostic report](/docs/troubleshooting/diagnostics-and-rep

 [handling-rate-limits]: /docs/guides/handling-llm-rate-limits-with-goose
 [installation]: /docs/getting-started/installation
-[discord]: https://discord.gg/goose-oss
+[discord]: https://discord.gg/n8R5VaWDAn
 [goosehints]: /docs/guides/context-engineering/using-goosehints
 [configure-llm-provider]: /docs/getting-started/providers
 [extensions-directory]: /extensions
@@ -323,4 +323,4 @@ Whether you're looking to streamline your CI/CD pipelines, automate server maint
 3. **Test in a safe environment** before deploying to production
 4. **Integrate with your existing workflows** and watch your productivity soar

-Connect with us on our [Discord community](https://discord.gg/goose-oss) to share your headless mode success stories, ask questions, and collaborate with other developers who want to push the boundaries of AI automation.
+Connect with us on our [Discord community](https://discord.gg/n8R5VaWDAn) to share your headless mode success stories, ask questions, and collaborate with other developers who want to push the boundaries of AI automation.
@@ -116,7 +116,7 @@ If you encounter issues:

 1. Check the **[Container Use GitHub repository](https://github.com/dagger/container-use)** for documentation
 2. Verify all prerequisites are installed and working
-3. Join our [Discord community](https://discord.gg/goose-oss) for support
+3. Join our [Discord community](https://discord.gg/n8R5VaWDAn) for support

 ## Next Steps

@@ -451,7 +451,7 @@ The key is treating goose as a planning partner, not just a code generator. Give

 - Try this approach with your own complex setup challenges
 - Experiment with different types of planning prompts
- Share your planning successes with the [goose community](https://discord.gg/goose-oss)
+- Share your planning successes with the [goose community](https://discord.gg/n8R5VaWDAn)
 - Explore how planning integrates with [Subagents](/docs/guides/context-engineering/subagents) for even more sophisticated workflows

 Remember, the goal is to get the right approach, in the right order, with the right safeguards. That's what makes the difference between a quick fix and a robust, maintainable solution.