Skip to content

chore: rename .claude/settings copy.json to avoid VSCode Copilot parsing errors#1615

Open
marioja wants to merge 1 commit intoruvnet:mainfrom
marioja:avoid-github-copilot-using-it
Open

chore: rename .claude/settings copy.json to avoid VSCode Copilot parsing errors#1615
marioja wants to merge 1 commit intoruvnet:mainfrom
marioja:avoid-github-copilot-using-it

Conversation

@marioja
Copy link
Copy Markdown

@marioja marioja commented Apr 16, 2026

Summary

Renames .claude/settings copy.json.claude/settings.json.copy so that VSCode's GitHub Copilot chat does not attempt to parse it as an active settings file.

Why

When Copilot chat is active in VSCode alongside a file named settings copy.json, Copilot treats it as a Claude Code settings file and tries to execute the hooks it defines. This fails on Windows PowerShell with:

The token '||' is not a valid statement separator in this version.

The error fires on SessionStart, UserPromptSubmit, and Stop hooks.

Renaming the file to settings.json.copy (extension .copy, not .json) keeps it as a backup reference while preventing Copilot from trying to load it.

Changes

  • .claude/settings copy.json.claude/settings.json.copy (file rename only, no content changes)

Test plan

  • Rename applied, file content unchanged
  • Verify Copilot chat no longer errors on session hooks in VSCode on Windows

Feel free to close this PR and do the rename yourself if you prefer — it's a one-line change.

🤖 Generated with claude-flow

… by MS github copilot chat. This would run a number of hooks that may cause other problems. You can find out because it will generate this error in session start, user prompt submit and stop hooks:

The token '||' is not a valid statement separator in this version.

If it was not for these error I would have never realized this.
@xkonjin
Copy link
Copy Markdown

xkonjin commented Apr 16, 2026

Nit: renaming settings copy.json to settings.json.copy is fine for consistency, but consider whether this file should be in version control at all. If it is a backup/artifact from local editing, it may be cleaner to .gitignore it instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants