Disable "use_tag" and make "tag" mandatory in MCP commands?

[jiiins]

I'm having a hard time working on multiple lists at the same time (maybe a long feature and a quick bug fix), so I give the instruction to always use the "tag" argument in each MCP command and avoid "use_tag".
It works for a while, but during long sessions sooner or later the tag is omitted and one of the lists gets messed up.
Maybe a simple solution could be to add the config option not to use "use_tag" at all and make "tag" mandatory.

[Crunchyman-ralph]

We can't do that, it would make the tag in state.json obsolete.

Why not instead make a GitHub worktree and work on one list in one branch and another list in the other branch.

Makes your life much easier

[jiiins]

Well, state.json would become superfluous/unused with this approach.

I agree with you on the worktrees, I have to stop being lazy!