Repomix local config breaks when using `--remote` option

[leovigna]

Description

Bug / Unintuitive DX

Running repomix --remote https://github.com/user/repo.git ignores the local repomix.config.json in my workspace because repomix first clones the remote repo and then searches for the config in the target repo instead of my current working directory.

Specifying a custom config with -c myconfig.json also initially seems to fail as well.

Solution

Technically, you can get the custom config working with an explicity path as opposed to a relative one but this is a bit unintuitive.
repomix --remote https://github.com/user/repo.git -c "$PWD/repomix.config.json"

The challenge is there are 3 potentiall options to pull config from

1. Global config (home directory)
2. Local workspace (local directory)
3. Target repo (remote repo)

Since the purpose of the config file is for the library consumer rather than the library author it would be better if repomix used the local config instead of search the target repo for a config file.

Usage Context

Repomix CLI

Repomix Version

1.11.0

Node.js Version

v22.19.0

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Running against the repomix repository itself fails #899

Related Issues

• Add support for Docker #221
• Impossible to pack a remote with specific paths #433
• Failed to compile template: Invalid string length #739
• Export loadFileConfig so that when repomix is used as a js library the users can choose to load a repomix.config.json #431
• Specifying an absolute file path for a remote repo output in library mode crashes #873
• .gitignore patterns are ignored when using repomix <directory> command #776

🔗 Related PRs

#256 - fix(cli): ignore output path using a relative path to the target [merged]
#885 - fix(cli): Skip file copy when absolute path is specified for remote repository output [merged]

👤 Suggested Assignees

• gaby
• ThomasKientz
• NEGU93
• eastlondoner
• cjol

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[github-actions]

Related Issues

I found some similar issues that might be helpful:

• Targeting remote while specifying nested output location fails #378 - Targeting remote while specifying nested output location fails - This issue describes the same underlying problem where config.cwd contains the temp directory path instead of the actual working directory when using --remote. The behavior affects config file resolution as well as output path handling.

• Feature request: global configuration equivalent of repopack.config.json #51 - Feature request: global configuration equivalent of repopack.config.json - This closed issue discusses global configuration support, which is related to the config hierarchy question you raised (global, local workspace, target repo).

These might provide additional context or solutions.