Then again, I see that the top buzz in the industry is about Claws and letting LLMs run loose with only a handshake agreement to be safe, and I already know the answer.
I actually wrote about this recently after poking around a popular extension that Antigravity users were installing. It's wild what people are doing with your credentials, and you'd have no idea! https://opista.com/posts/blind-trust-in-vs-code-extensions
We’re cooked.
(One of the only good things about GH is, that if you block some account, it will tell you if that account contributed to some repo at the top. Makes it very easy to filter out slopcode.)
This is why allot run dev containers but agreed this really should be top priority but instead is probably in the "maybe if we have a major security incident" bucket of concerns as these things often are
One option is to vet a version yourself and disable auto-update, but that's not really feasible to spend time on for most people.
that said, I'm not sure i plan on using it long term - as someone else pointed out, the lack of extension sandboxing does make me feel a bit uncomfortable for extensions like this that aren't backed by large entities.
Nova has a git sidebar which does some of the same thing, but I do think there's something more that is useful to yours. Yours is definitely better because of the heatmap colouring, sadly I can't do that in Nova.
Beyond the core concept, there's also
- A heatmap that colors files based on recency
- Deleted files appear in the tree where they used to be
- A pinned section for files that are not recent but handy
- File history, diff search (pickaxe) and git log -L line/function history available from editor context menu
- File grouping based on the moon phase during the most recent commit (good luck finding alternative software for this)
- a button to toggle view as list / as tree
- a better search file feature
- some deleted files are shown while they where only on feature branches and never on the main branch
- looking for an setting to hide some file types (binary for example)
Nice work !
- The search inside the tree is ass, it's what vscode provides for tree controls and I can't really change it aside from reimplementing a tree from scratch. But do try the quick pick (ctrl+q, f) which is like ctrl+p for fresh files only
- i don't really see how they'd show up, because i don't examine files outside the branch you are in. possibly something doesn't get cleaned up when switching branches. i'll look into it but if you have a way to reproduce, an issue would help here
- file type filters would be easy to add
PS: unfortunately does not work on latest cursor (2.5.20). Can you please check?
You'll need to wait for 1.1.2 to show up in the marketplace, it usually takes a few minutes to update. I'm going to sleep now and I'll check on it tomorrow.