How do I do this in a convenient way? The standard Go extension is installed. On Jetbrains IDEs it would be something like cmd-space, select import you want from a fuzzy search, and it adds a corresponding import clause at the top of the file and package name/alias at the import site. It's been working like that for 10 years. In vscode, all you get is opt-Enter ("quickfix") and let an agent try to figure it out, which takes ages and will probably not do what you want.

If you generate all the code with Claude Code / Codex or a similar harness, it'll obviously take care of the imports, but sometimes I still write code manually or use some more pedestrian AI autocomplete like Supermaven, as in the above screencap, and it'll not add imports on its own, annoyingly. Anyway, you need some kind of reasonable deterministic fallback.

So what am I missing here?

Is there a debloated fork of VS Code which I can use with Claude Code or Open Code?

Every security scan on my team shows up after the fact. I push, the pipeline runs and an hour later I get a wall of findings on code I have already mentally moved on from. By then fixing it means context switching all the way back into something I was done with.

What I want is IDE security scanning that runs while I am writing, in the editor, before the commit even exists. I have tried a couple of extensions and they were either so noisy I turned them off in a day or so shallow they caught nothing. With an assistant writing half my code now, catching this at the point it is written seems like the only place that scales.

Feels like this should be solved by now and somehow it is not.

Hello! I'm trying to install .NET 8 to use on VSC in order to just do some modding for Vintage Story, which uses .NET 8 for text encoding. Using >.NET Install Tool - Install the .NET SDK System-Wide, this error occurs. What can I do about it? (etc/os-release exists but it does not contain CachyOS)

dskdakCancelled Installation of .NET notAnAcquisitionRequest-global~x64.
We are unable to detect the distro or version of your machine ... does /etc/os-release or /usr/lib/os-release exist?
Cancelled Installation of .NET undefined.
An active-support version of dotnet couldn't be found. Discovered versions: []Cancelled Installation of .NET notAnAcquisitionRequest-global~x64.
We are unable to detect the distro or version of your machine ... does /etc/os-release or /usr/lib/os-release exist?
Cancelled Installation of .NET undefined.
An active-support version of dotnet couldn't be found. Discovered versions: [] 

Looking for devs / likeminded people in the above areas open to meeting up and having a coffee together whilst we get on with our own projects. Just looking for some company really! I mainly use GitHub copilot to do the leg work in VSCode and it would be great to learn more, share prompt ideas etc. thank you

This is my vscodium.nix, correctly imported. Catppuccin normally works for other modules:

{ pkgs, ... }:

{
programs.vscodium = {
enable = true;
profiles.default.extensions = with pkgs.vscode-extensions; [
vscodevim.vim
jnoortheen.nix-ide
];
};

catppuccin.vscodium.profiles.default = {
enable = true;
flavor = "macchiato";
icons = {
enable = true;
flavor = "macchiato";
};
};
}

The extensions are applied correctly.

Every time I create a source file (.cpp or .hpp) the refactor preview opens, how do i disable this? I don't need or want it

Edit: Fixed, it was the cmake extension; set [Cmake > Modify Lists: Add New Source Files] to no

Anyone else seeing this?

I have a repo with multiple Git worktrees. In the Source Control sidebar, VS Code shows all of them, which is expected. I used to be able to right click a worktree and choose Close Repository so I could keep only the current one visible.

Now when I click Close Repository, the Source Control view just refreshes and all the repositories are still there. Nothing actually closes.

Is this a recent bug, or did something change?

version: 1.129.1

Basalt: click any element in your running React Native/Expo app, drag it, change the color, change the text, and it writes straight into your real source file. No separate design tool, no copy-pasting values back into code.

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before testing it!

Would love to get your brutal feedback on it.

Hello, hopefully I am posting this in the correct Reddit group. I am not a programmer, but I have configured vscode to use Qwen 3.5 hosted on a remote computer to help me create code for NIXOS on a git repo on my local computer. Mostly it seems to be working file, I created a .continueignore file that contains the following

# This file sits inside /home/username

# Step 1: Block absolutely everything in the opened workspace

*

**/*

# Step 2: Un-ignore just the specific folder (relative to home)

!nixos/

!nixos/**

to stop vscode from reading and writing outside the git repo. The issues is whenever I ask it to create a README file it is constantly creating a home profile within the git hub repo, instead of creating the README file at the root of the repo. Does anyone know why this would be happing, and how to stop it, thank you.

Takes around 7-10 minutes and its kinda annoying, it does it for other apps but for some reason vscode takes 15x the time other apps take

Hello,

i would love to know how people around here are able to debug, code that are writing in python using vscode, I am looking for a similar behavior to matlab (where i learned to program).

what i mean by similar behavior, be able to run the complete code, and keep the variables defined in memory, have a terminal where one can interact with the variables defined, print them, modify them etc. be able also to check definitions of function of imported libraries such as numpy.

the only way i found to do this in vscode, is with jupiter extension, but i find it finiky, and wanted to know if there were other alternatives.

Video: https://youtu.be/wErgEe9Pgqo
Source: https://github.com/Automations-Project/VSCode-Perplexity-MCP
VSCode: marketplace.visualstudio.com/items?itemName=Nskha.perplexity-vscode

Quick Start:
- Install the VSCode extension from the links below
- log in with your account
- click auto configure all IDEs (Auto Install MCP and settings)
- chat with your A.I and ask it to use it (4 modes: ask, search, research, compute)

Support the project by giving it a star on GitHub, that’s all💛.

I'm new to VS Code and I would like to understand why I sometimes get this error. I tried by adding every single folder I have the python files in to one workspace, but it still doesn't work. I get the error when I run python3 file.py on the terminal. Why does this happen and how could I fix it?

Hi everyone! 👋

I've been working on a VS Code extension called DebugChronicle, and I'd love to get some feedback from fellow developers.

One thing that always frustrated me while debugging was this question:

So I built an extension that automatically records your development session and helps trace an error back to the code changes that most likely introduced it.

Features

• 📜 Automatic timeline of file changes
• 🐞 Runtime exception capture from the VS Code debugger
• 💻 Terminal error & diagnostic tracking
• 🧠 Deterministic root-cause analysis (no AI required)
• 🌐 Dependency graph showing relationships between edits and errors
• ⏪ Session replay
• 📄 Export reports in Markdown or Word
• 🔒 Completely offline — no cloud, telemetry, or accounts

Everything is stored locally inside the workspace, so it works without sending any code anywhere.

Here's a preview of the UI 👇

(Attach the image.)

I'd really appreciate any feedback:

• What features would make this genuinely useful?
• Is there anything in the UI that could be improved?
• Would this fit into your debugging workflow?

Thanks! I'd love to hear your thoughts.

I run coding agents in the terminal, but I wanted their history to be as easy to navigate as the rest of my work in VS Code. Long terminal sessions are fine while they are running and much less pleasant when I need to find one response, inspect a failed tool call, or understand the process a week later.

So I made Coding Agent Trajectory Visualizer, a free extension that keeps session review inside VS Code.

From the Activity Bar, it provides:

- Session organization by date, project, path, and title, plus cross-session search, a clickable calendar, and copyable resume arguments.

- A readable Timeline that puts prompts and final responses first, adds full-screen readers for long text, supports multi-day navigation, and refreshes live sessions while preserving the active tab, scroll position, and expanded turns.

- Expandable agent process details: intermediate messages, thinking when saved, tool calls, formatted and raw inputs, tool results, errors, and linked API calls.

- Interactive Views for context growth, prompt workload, compaction summaries, tool-use history, recurring tool sequences, failures, and task phases. The Overview window can be played or resized, and selected visual blocks can jump directly to the relevant Timeline step.

- Session Replay and Compare, including provider, model, effort, and project indicators for keeping important variables visible.

- Session and workspace setup readers for memory, CLAUDE.md or AGENTS.md, skills, hooks, MCPs, subagents, and other harness files.

- A personal dashboard with calendar history, total agent runtime and rank, achievements, model and effort usage, response speed, TTFT where available, prompt habits, hourly activity, streaks, and frequent-word views.

- Unified JSON export and readable Markdown transcripts.

It supports both Claude Code and Codex local sessions, along with light and dark VS Code themes. Claude Code also has optional API Capture, off by default, for inspecting request parameters, system prompt versions, API messages, tool schemas, caching, HTTP details, TTFT, latency, and response events.

VS Code Marketplace:

https://marketplace.visualstudio.com/items?itemName=yiyang-wu.trajectory-visualizer

Interactive demo:

https://wuwendyy.github.io/coding-agent-trajectory-visualizer/

I am the developer and would especially appreciate feedback on the VS Code interaction and information density.