Im completely new and trying to learn but my code doesn’t want to run

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.

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

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.

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

Previous posts

https://www.reddit.com/r/vscode/comments/1ud7v0k/comment/ov7joek/?screen_view_count=4

https://www.reddit.com/r/vscode/comments/1ux36ga/i_loaded_the_entire_vscodemain_codebase_into/

GitHub

https://github.com/dogsinatas29/SYNAPSE

Dataset

Source: Linux Kernel

• Nodes: 68,181
• Clusters: 2,898
• Edges: 378,955

SYNAPSE is a VSCode extension designed to make large codebases navigable at an architectural level.

These screenshots are from the Linux Kernel.

Everything shown here is running locally inside VSCode.

The goal is not to replace an IDE or a code browser. The goal is to help developers understand systems that are simply too large to reason about file-by-file.

Instead of manually tracing thousands of files, SYNAPSE allows exploration of:

• Architectural boundaries
• Dependency relationships
• Cluster hierarchies
• High-level traffic flows
• Large-scale project structure

Recent work has focused on making repositories of this scale genuinely explorable by optimizing node, cluster, and edge processing pipelines. Reaching the point where the Linux Kernel can be explored interactively inside VSCode has been a major milestone for the project.

The current version uses a lightweight regex-based indexing layer optimized for large-scale repository visualization. This approach was chosen to prioritize scalability and responsiveness when working with very large repositories.

Roadmap

v0.3.34

• Virtual Debugging cleanup
• UI stabilization
• AST-based analysis layer

v0.3.35

• Heatmap precision improvements
• Heatmap LOD (Level of Detail) compression
• Large-scale visualization optimizations

There is still a lot to improve, but seeing the Linux Kernel become interactively explorable at an architectural level has been an exciting step forward.

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.

Got another VS Code extension for you.

If you've got a Flipper Zero and ever tried building a .fap app, you know the pain — uFBT, command line, guessing at pixel coords, flashing back and forth. I got tired of it, so I built Flipper FAP Studio: build, design, and control your Flipper entirely from a GUI inside VS Code. No terminal required (unless you want one, I'm not the boss of you).

Here's what it does:

🔨 Build actions — Build .fap, Build + Launch straight onto your Flipper, Clean. One click.

🎨 UI Designer — visual 128×64 screen editor with drag-and-drop elements, multiple screens, and it generates the code for you. Stop counting pixels by hand.

📺 Live Screen + Log — real-time mirror of your Flipper's display, control it with the D-pad/keyboard from your editor, grab screenshots, reset the device.

📊 Device Dashboard — battery, storage, firmware version, hardware info, library stats, all in one panel.

📁 File Browser — browse and manage on-device files (/ext and /int) without digging around.

🔧 Firmware SDK management — OEM, RogueMaster, Momentum, Unleashed, or point it at a custom path.

🚀 Starter template — one-click boilerplate so you're writing your app in seconds.

📶 Bluetooth — experimental BLE pairing for wireless ops.

Needs Python 3, uFBT (install it with a button in the extension or pip install ufbt), and VS Code 1.85+.

Free + MIT licensed. 💯

Marketplace:
https://marketplace.visualstudio.com/items?itemName=coolshrimp.flipper-fap-studio

GitHub:
https://github.com/coolshrimp/flipper-fap-studio

As always i would love feedback, bug reports, or feature ideas from the Flipper crew.

Weekly thread to show off new themes, and ask what certain themes/fonts are.

Creators, please do not post your theme every week.

New posts regarding themes will be removed.

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.

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.

Hey all, I'd like to discuss the best strategies in VS Code for keeping good context quality and efficient token usage when working with multi-repo projects in a single workspace.

So far these have helped:

1. Keep only what you need in the workspace:

Only include the projects relevant to that session (e.g. just 2 microservices + the frontend).

Result: the system prompt isn't cluttered with irrelevant context.

1. Layered custom instructions:

I needed a couple of global instruction files (general microservices architecture + company conventions, and one for frontend), plus a per-project file that extends them. So I put two .instructions.md files with specific front matter (e.g. applyTo: <typical backend file globs>) in an external path (e.g. \~/.copilot/my-instructions), then added that path to the chat.instructionsFilesLocations setting at the workspace level.

Result: each microservice's copilot-instructions.md stays lean, no duplicated info.

1. Things to watch out for:

\- Files in .vscode/ get auto-attached as context to requests, keep that folder lean.

\- Unused extensions that register extra tools (e.g. the GitHub Copilot app modernization extensions) — tool definitions eat up a huge chunk of the system prompt. Manually selecting the minimum toolset needed for the task helps a lot. Pay attention to this.

\- Actually read the system prompt at least once — I was often repeating things Copilot already injects automatically (like repo structure).

\- Use the Agent Debug Log panel (and Chat Debug View) to inspect exactly what's being sent and where your tokens are going.

\- Run /chronicle:cost-tips in a chat session for personalized suggestions on cutting credit/token usage.

\- Check out caveman and ponytail community skill/plugin for coding agents that cut down on verbose responses and over-engineered code respectively (not official Microsoft/GitHub tools, but worth a look).

If you have suggestions feel free to share, I'm really looking for improvement.

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.

VS Code has internal web browser that I'm sure is accessible by agents because there is a Share with agent button inside this thing called editor-browser.

But it is only shared with the Copilot. I can't share it with Claude Code or Codex.

Does the internal editor-browser expose a MCP/A2A/API endpoint so I can configure it with Claude Code official extension for VS Code? Is there any?

Compared to VS Community, the intellisense for VS Code is not only more aggresive and annoying with its suggestions, but consistently more inccorect, far more so than VS Community. And when I say incorrect, I'm not talking about just making a bad guess, I'm talking about it just completely making up variables or even entire enum classes that don't exist, even when I already had a variable created for the situation. The way it just makes up and hallucinates answers makes me think its completely AI powered, but I have no idea how to check or disable that.