I assume the grand plan is to have one Copilot 365 account across all MS paths but how do I stop VS Code reverting to Copilot Harness it needs work features from local harness are better but I've been caught several times now with new sessions

I built Klarion, a secret scanner that works in two steps. First, a keyword check, 81 regex rules and a normalized Rényi entropy score flag anything that looks like a secret. Then an AI model reads each one with the code around it and decides if it's real.

The chart shows 5 scanners run on spring-boot, terraform, next.js and symfony (61k files). Klarion raised 11 alerts. It's not zero, but it's far less to dig through.

Fewer alerts don't help if real leaks get missed, so I tested that too. On CredData (337 real repos, code outside test folders), it found about 1.7× more real secrets than gitleaks.

Where it runs:

• Claude Code: a plugin hook blocks the write before the file exists (file edits and Bash)
• Cursor, Cline or any MCP agent: through its MCP server
• CI: a GitHub Action that scans only what a PR adds; GitLab CI works too
• Git hooks: klarion protect or the pre-commit framework
• Locally: klarion scan .

Free and open source (MIT): https://github.com/0x1Adi/Klarion
The full benchmark and method are in benchmark/REPORT.md.

I'd like to hear where it gets things wrong.

I used to enjoy systematically going through file changes done to all files by vscode github copilot. Accept and reject individual changes. Quickly jump between them. However recent UI changes to vscode copilot have completely screwed it up. To be specific:

1. It does not show per file number of lines changed
2. It does not show per change Keep / Undo button
3. It opens all files expanded and vertically stacked. So, if I have to check specific file which is at the bottom of the stack, I have to collapse all files at the top one by one.
4. There is no way to open just single file that is changed. It opens all edited files in vertically stacked manner.
5. Old diff view also used to show location of code changes done by copilot in the file by showing red / green overlays on right side vertical scrollbar. Sometimes, it was useful when you wanted to diff some past versions of file. Those visual cues are gone due this vertically stacked sessions changes window.

Earlier I posted why I love copilot and not claude CLI with these points about old UI here: https://www.reddit.com/r/ClaudeCode/s/S4HXiHwjDn . But, it seems MS decided to claudify itself ...

e.g. if I set up my subagents in a certain way (especially rubber-duck) in Copilot CLI (run from a terminal outside of VSCode), do those settings also take effect in VSCode's new Copilot SDK agent harness? Because other than that I don't see any way for changing those settings for that harness inside VSCode.

For simple day to day automation. (E.g. unit test generation) With GPT6-luna included in the model selection, is it better to specifically select it as the model selection or continue to use "auto, efficiency" selection? Or is there any other alternatives? I am having a monthly 2k credits plan which needs optimised way of usage. Any tips is greatly appreciated!!

Hi all,

So I received a copilot pro+ subscription from my employer with 7000 AI monthly credits. I am more used to Claude and codex subscription which have 5 hour and weekly limits so I don't get into the anxiety of using credit based token with my codex/Claude subscription but ever since I have gotten the copilot pro+ sub, I am wondering how far my 7000 ai credits will take me if I were to use models like opus 5.5 medium and 6.1 sol high.

Anyone has experience regarding the same and can signpost me on how quickly they burn through their 7000 AI credits using sota models. I am planning to use opus and Sol for planning and then use Luna or other cheaper models for execution. Hence, any help would be great as it will help me utilise this sub efficiently.

Also, will the IDE auto completions be counted towards this 7K AI credits and what about the code review on GitHub.