Is ‎.claude/iloom-swarm-mcp-config-path commited supposed to be commited?

[NoahCardoza]

I'm not sure if this is a question, bug or both. I used the epic swarm feature and it committed .claude/iloom-swarm-mcp-config-path. That seems a little strange, is this supposed to happen?

helixclaw/2keychains@39089ae

[acreeger]

No! It should get ignored because iloom adds it to ~/.config/git/ignore - can you look at the file and see what's in there?

[NoahCardoza]

After some digging, it's become apparent that the culprit is my custom global core.excludesFile setting.

The ~/.config/git/ignore the file was correctly initialized by iloom (a couple hours before I opened this ticket/discussion).

➜  ls -al ~/.config/git/ignore
-rw-r--r--@ 1 prometheus  staff  254 Feb 23 21:39 /Users/prometheus/.config/git/ignore
➜  cat ~/.config/git/ignore   

# Added by iloom CLI
**/.iloom/settings.local.json

**/.claude/settings.local.json

# Added by iloom CLI
**/.iloom/package.iloom.local.json

# Added by iloom CLI
**/.claude/agents/iloom-*
**/.claude/skills/iloom-*
**/.claude/iloom-swarm-mcp-config-path

However, my core.excludesFile setting points to a custom location. When I unset this, then the settings in ~/.config/git/ignore were picked up.

➜  git config --global --get core.excludesFile
~/.gitignore_global

---

Honestly, I configured this custom location because I didn't know that there was a default global location. I should probably change it, there isn't a good reason to be different here... However, we could handle this by checking the core.excludesFile config value and write there if it's set.

[acreeger]

This is fixed! v0.10.3 will handle this properly.