.github/agents/code-munch.agent.md

---
name: code_munch
description: "Minimal agent to invoke the MCP `code_munch` indexer for repository indexing."
model: qwen3.6:35b-a3b (ollama)
---

# Minimal Code Munch Agent

This file contains a minimal usage note for invoking the MCP `code_munch` indexer to create a JSON index of this repository.

## Prerequisite — ensure code_munch is installed and running

- Verify the `jcodemunch-mcp` executable is available and runnable:

```
# Unix / WSL / Git Bash:
command -v jcodemunch-mcp && jcodemunch-mcp --version

# Windows (PowerShell):
Get-Command jcodemunch-mcp

# Simple run test:
jcodemunch-mcp --help
```

- If the executable is missing, install per upstream instructions (example):

```
pip install jcodemunch-mcp
```

- Start the server locally before calling the MCP client, or ensure the MCP host listed in `.continue/mcpServers/code-munch.yaml` can reach it.

- Check the local MCP client config for JSON errors that can prevent startup:

```
# Windows (PowerShell) — validate the MCP client config JSON
python -c "import json,sys;json.load(open(r'C:\Users\CharlesFettinger\AppData\Roaming\Code\User\.mcp.json'));print('OK')"

# Or use a JSON linter/editor to open `C:\Users\CharlesFettinger\AppData\Roaming\Code\User\.mcp.json`
```

If this check raises an exception, fix the JSON (missing commas, trailing commas, or invalid values) before starting the MCP server.

## Usage

Use the `mcp_code_munch_index_folder` tool directly to index a repository. No `mcp call` CLI is required.

```
mcp_code_munch_index_folder(path: "g:\\Projects\\Wrdler")
```

- MCP server configuration: `.continue/mcpServers/code-munch.yaml`.
- Output index fields: `relative_path`, `language`, `size_bytes`, `line_count`, `sha256`, `imports`, `top_level_defs`, `summary`.

## Important Agent Instruction

- Do NOT create a plan that instructs other agents or tools to call the MCP `code_munch` server. When invoking `code_munch`, use the `mcp_code_munch_index_folder` tool directly instead of generating a separate "plan" step or using the `mcp call` CLI. This avoids accidental plan-driven remote executions or duplicated orchestration steps.