# Reported issues for Repomix

Pod holds 8 of 8 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to [Repomix](/mcp/repomix).

## Most discussed

### MCP Feature Request: generate output in project directory

I've somehow managed to chain different repomix mcp tools together, but anytime i try to access it, i get this Cursor error: `Content type "resource" not supported`

would be awesome if pack_codebase could have a `local` parameter so it woud generate the repomix output in the project directory

@yamadashy wdyt?

[Read the thread](https://github.com/yamadashy/repomix/issues/472) · 2025-04-07 · open · external user · 6 comments

### Pack Codebase response resource item doesn't include content

When using the `pack_codebase` tool, the server returns items of the format:

```
{
  type: "resource",
  resource: {
    uri: "file:///tmp/repomix/mcp-outputs/pqmRzP/repomix-output.xml",
    mimeType: "application/xml",
    text: "Repomix output file",
  },
}
```

According to the [MCP docs](https://modelcontextprotocol.io/docs/concepts/resources) if I'm understanding correctly, this call should include the actual contents of the file and the URI would be for future reference or for…

[Read the thread](https://github.com/yamadashy/repomix/issues/426) · 2025-03-17 · closed · external user · 6 comments

### 🔴  Bug: MCP read_repomix_output always take the entire xml file

### Description

Hello !

I'm using the MCP server inside Cursor AI to pack and read my repo, in order to create at the end a complete solution for other developers to have access instantly to key information of our Design System.

⚠️  It's a blocking issue since we can't use properly the MCP server with Repomix ⚠️ 

The packing and the search work fine, however, when it comes to use the `read_repomix_output`, it breaks my `context used`.

After some deep dive, here are my observations:

##…

[Read the thread](https://github.com/yamadashy/repomix/issues/849) · 2025-09-18 · closed · external user · 4 comments

### Bug: McpError: MCP error -32602: Structured content does not match the tool's output schema: data should NOT have additional properties

### Description

Hi @yamadashy,

It's been a while since my last contribution to Repomix. It's great to see how far you guys have come!

I think I found a bug with the MCP server: McpError: MCP error -32602: Structured content does not match the tool's output schema: data should NOT have additional properties

This happens because the tool's output schema only specifies the schema for a successful result, not for an error result. You can see the validation handling here:…

[Read the thread](https://github.com/yamadashy/repomix/issues/833) · 2025-09-12 · closed · outside contributor · 4 comments

### pack_remote_repository hangs indefinitely on inaccessible repos

### Description

When using `pack_remote_repository` (MCP) or `--remote` (CLI) with an inaccessible repository (non-existent, private, or requiring auth), repomix hangs indefinitely.

### Root Cause

`execLsRemote` in `src/core/git/gitCommand.ts` has no timeout and doesn't set `GIT_TERMINAL_PROMPT=0`. Git waits for credential input that never comes in non-interactive contexts.

### Reproduce

```bash
npx repomix --remote https://github.com/user/nonexistent-repo
```

### Expected

Fail with…

[Read the thread](https://github.com/yamadashy/repomix/issues/1077) · 2026-01-06 · closed · outside contributor · 2 comments

### grep_repomix_output: -- separators inside contiguous context blocks, matches printed with the context prefix, and RangeError on large outputs

## Description

`grep_repomix_output` returns a `formattedOutput` array that is documented as "Formatted grep-style output with context lines", but the `--` separator and the `:`/`-` line prefixes are not derived the way `grep -C` derives them. On a large enough output the same code path stops producing output at all and the tool fails with `SEARCH_ERROR`.

Three separate symptoms, all from `formatSearchResults` in `src/mcp/tools/grepRepomixOutputTool.ts`:

1. `--` is inserted between context…

[Read the thread](https://github.com/yamadashy/repomix/issues/1868) · 2026-09-20 · open · external user · 0 comments

### MCP: `--mcp --verbose` writes logger output to stdout, corrupting the JSON-RPC channel

## What happens

`repomix --mcp --verbose` puts the logger's normal output **on stdout** — the same file descriptor
the MCP stdio transport uses for JSON-RPC. Measured on `main` @ `9f01703a` / Node v24.18.0 / Windows
11, driving the real server:

```
$ node probe.mjs .
stdout lines: 2  non-JSON-RPC: 0

$ node probe.mjs . --verbose
stdout lines: 19  non-JSON-RPC: 17
```

Those 17 lines are the logger, e.g.:

```
directories: [ '.' ]
cwd: D:\Desktop\pr\rpx
options: {
  enableFileProcessors: true,…

[Read the thread](https://github.com/yamadashy/repomix/issues/1866) · 2026-09-20 · open · external user · 0 comments

### MCP: operator stderr logging is permanently silenced after the first generate_skill / pack_remote_repository call

## What happens

Once an agent calls the `generate_skill` (or `pack_remote_repository`) MCP tool **once**, the
repomix MCP server stops emitting any operator diagnostic on stderr for the rest of the
session — including `logger.error()` output from completely unrelated tools. The tools keep
working and keep returning correct results, so nothing looks broken to the agent; only the
human sitting on the server side loses visibility, permanently for that session.

## Mechanism

- `runCli()` drives…

[Read the thread](https://github.com/yamadashy/repomix/issues/1864) · 2026-09-20 · open · external user · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/yamadashy/repomix/issues).