tkmind/tkmind_go
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

Spelling (#7137)

Browse Source 
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
Josh Soref
2026-02-11 09:35:24 -05:00
committed by GitHub
parent 544bc1bc4f
commit f636a97faa
81 changed files with 109 additions and 110 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/tutorials/custom-extensions.md
+3 -3
View File
@@ -14,7 +14,7 @@ goose allows you to extend its functionality by creating your own custom extensi
In this guide, we build an MCP server using the [Python SDK for MCP][mcp-python]. We’ll demonstrate how to create an MCP server that reads Wikipedia articles and converts them to Markdown, integrate it as an extension in goose. You can follow a similar process to develop your own custom extensions for goose.
You can check out other example servers in the [MCP servers repository][mcp-servers]. MCP SDKs are also available for other common languages, such as [Typescript][mcp-typescript] and [Kotlin][mcp-kotlin].
You can check out other example servers in the [MCP servers repository][mcp-servers]. MCP SDKs are also available for other common languages, such as [TypeScript][mcp-typescript] and [Kotlin][mcp-kotlin].
:::info
goose supports Tools, Resources, and Prompts from the [Model Context Protocol](https://modelcontextprotocol.io/). See [`mcp_client.rs`](https://github.com/block/goose/blob/main/crates/goose/src/agents/mcp_client.rs) for the supported protocol version and client capabilities.
@@ -211,7 +211,7 @@ Verify that your MCP server is running in the MCP Inspector (a browser-based dev
MCP Inspector requires Node.js and npm installed on your computer.
:::
1. Setup the project environment:
1. Set up the project environment:
```bash
uv sync
@@ -240,7 +240,7 @@ MCP Inspector requires Node.js and npm installed on your computer.
</TabItem>
<TabItem value="cli" label="In the CLI">
1. Setup the project environment:
1. Set up the project environment:
```bash
uv sync
documentation/docs/tutorials/langfuse.md
+1 -1
View File
@@ -13,7 +13,7 @@ This tutorial covers how to integrate goose with Langfuse to monitor your goose
## Set up Langfuse
Sign up for Langfuse Cloud [here](https://cloud.langfuse.com) or self-host Langfuse [Docker Compose](https://langfuse.com/self-hosting/local) to get your Langfuse API keys.
[Sign up for Langfuse Cloud](https://cloud.langfuse.com) or self-host Langfuse [Docker Compose](https://langfuse.com/self-hosting/local) to get your Langfuse API keys.
## Configure goose to Connect to Langfuse
documentation/docs/tutorials/lead-worker.md
+1 -1
View File
@@ -59,7 +59,7 @@ Ensure you have [added the LLMs to goose](/docs/getting-started/providers)
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
5. (Optional) Change the default number of **initial lead turns**, the **failure threshold** before switching back to the lead model, or the number of **fallback turns** to use the lead model during fallback
</TabItem>
<TabItem value="cli" label="goose CLI">
The only required configuration is setting the `GOOSE_LEAD_MODEL` [environment variable](/docs/guides/environment-variables#leadworker-model-configuration):