ZetabS

I'm encountering the same issue. This bug is caused by a mismatch between the CLI and MCP server in how the `tag` argument is handled in `addTask()`. In the MCP...

This issue clearly illustrates the risk of using positional parameters across modules that evolve independently—like the CLI and MCP server. The fact that `projectRoot` silently matched the `tag` parameter slot...

@marbens-arch While this relates to #837, that issue is ineffective as a duplicate. Issue #837 explored multiple approaches over 10+ years: **Rejected:** - [Default ignore lists](https://github.com/syncthing/syncthing/issues/837#issue-45624994) ([rejected by maintainer](https://github.com/syncthing/syncthing/issues/837#issuecomment-58870335)) **Discussed...

Sorry if I was aggressive. I don't speak English as my first language. I just wanted to know why you think the issue is duplicate.

To clarify: this proposal is NOT about "adding global ignores by default". > The proposed global ignore file avoids those issues by being opt-in and customizable This is focused on...

> it should be in the config and not in a file ... I think this simplifies things. @calmh I agree storing patterns in the config would be simpler, but...

> if I copied ~/.config/syncthing or wherever the config is stored to another machine I'd be surprised and annoyed if this specific little part of the config didn't carry over....

How about using both prepend and append patterns? **Global ignore:** ```text .DS_Store # prepend #local # separator *.log # append ``` **Local ignore:** ```text !important.log ``` **Evaluated ignore:** ```text .DS_Store...

Thank you for the clarification @jest — I completely agree. I’ve updated the report accordingly.