> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ticket-rs.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Goose

> Set up tk with Goose for AI-powered issue tracking

Use tk with [Goose](https://block.github.io/goose/) to manage issues from Block's open-source AI coding agent.

***

## What is Goose?

[Goose](https://block.github.io/goose/) is a free, open-source AI coding agent built by Block (formerly Square). It features an MCP-native architecture — every extension is an MCP server — making it one of the most natural integration points for tk. Goose runs as a desktop app or CLI and connects to 3,000+ MCP servers.

***

## MCP Integration

### Quick Setup (CLI)

Run the interactive configuration:

```bash theme={null}
goose configure
```

Select **Add custom extension** > **Command-line Extension**, then enter:

* **Name:** `ticket-mcp`
* **Command:** `uvx ticket-mcp`

### Manual Configuration

Edit `~/.config/goose/config.yaml`:

```yaml theme={null}
extensions:
  ticket-mcp:
    name: ticket-mcp
    cmd: uvx
    args: [ticket-mcp]
    enabled: true
    type: stdio
    timeout: 300
```

<Accordion title="Requirements">
  **uv** installed via: `curl -LsSf https://astral.sh/uv/install.sh | sh`

  **Python** version 3.10 or higher (installed automatically by uv)

  **Goose** installed from [block.github.io/goose](https://block.github.io/goose/)
</Accordion>

### Verify Installation

Run `goose info -v` to confirm ticket-mcp appears in the extensions list, then start a session:

```bash theme={null}
goose session
```

Ask: *"What tk tools are available?"* — Goose should list all ticket-mcp tools.

***

## Workflow Tips

### Starting a Session

Ask Goose: *"Run tk triage and show me what I should work on today"*

Goose will execute `tk triage` and present AI-powered recommendations.

### Creating Issues

Ask Goose: *"Create a high-priority bug for the database connection leak"*

Goose will run:

```bash theme={null}
tk create "Fix database connection leak" -t bug -p 1
```

### Closing Work

Ask Goose: *"Resolve tk-abc123, the fix is deployed"*

Goose will run `tk resolve tk-abc123` and report newly unblocked issues.

### Dependency Management

Ask Goose: *"Show the dependency tree for tk-xyz789 and explain what's blocking it"*

### Project Health

Ask Goose: *"Run tk insights and tell me about the project's bottlenecks"*

***

## Goose-Specific Features

<AccordionGroup>
  <Accordion title="MCP-Native Architecture">
    Goose treats every extension as an MCP server. This means ticket-mcp is a first-class citizen — not an adapter or wrapper, but a native integration that Goose can reason about and compose with other MCP tools.
  </Accordion>

  <Accordion title="Desktop App">
    Goose's desktop app provides a visual interface for managing extensions. You can enable/disable ticket-mcp, view tool invocations, and manage sessions through a GUI.
  </Accordion>

  <Accordion title="Extension Composition">
    Goose can compose multiple MCP servers in a single session. Combine ticket-mcp with GitHub, database, or cloud extensions for end-to-end workflows like "create an issue, fix it, push to GitHub, and resolve."
  </Accordion>
</AccordionGroup>

<Info>
  Goose recommends limiting active extensions to 5 or fewer with 50 or fewer total tools for optimal performance. ticket-mcp is lightweight and fits well within these limits.
</Info>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Extension not loading">
    Run `goose info -v` to check extension status. Ensure `uvx` is in your PATH. Try increasing the `timeout` value in config.yaml if the server is slow to start on first run (it needs to download dependencies).
  </Accordion>

  <Accordion title="YAML syntax errors">
    Goose uses YAML (not JSON) for configuration. Verify indentation is correct — YAML is whitespace-sensitive. Use `goose configure` for the interactive setup to avoid syntax issues.
  </Accordion>

  <Accordion title="Tools not available in session">
    Ensure `enabled: true` in your config.yaml. Start a new session with `goose session` after changing configuration.
  </Accordion>

  <Accordion title="Slow tk commands">
    Enable caching with `tk cache info` to verify the analytics cache is working. Cached responses return in under 10ms.
  </Accordion>
</AccordionGroup>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="CLI Reference" icon="terminal" href="/cli-reference/commands">
    Complete tk command documentation
  </Card>

  <Card title="MCP Server" icon="plug" href="/integrations/mcp">
    Deep dive into MCP server capabilities
  </Card>

  <Card title="Graph Analytics" icon="chart-network" href="/concepts/graph-analytics">
    Learn about PageRank and dependency analysis
  </Card>

  <Card title="Goose Docs" icon="book" href="https://block.github.io/goose/">
    Official Goose documentation
  </Card>
</CardGroup>

***

## Sources

* [Goose Documentation](https://block.github.io/goose/)
* [Goose Configuration Files](https://block.github.io/goose/docs/guides/config-files/)
* [Goose Extension Manager](https://block.github.io/goose/docs/mcp/extension-manager-mcp/)
* [Goose GitHub Repository](https://github.com/block/goose)
* [MCP Documentation](https://modelcontextprotocol.io)