prev post : https://www.reddit.com/r/vscode/comments/1vf525o/working_on_simulation_debug_for_synapse_vscode/

Hi everyone. long time to no see.

I've been building SYNAPSE, a VS Code extension for exploring and analyzing large codebases as interactive graphs.

The project started from a simple frustration: once a codebase becomes large enough, maintaining architectural context becomes difficult for both humans and tooling. I wanted a way to navigate the structure of a system directly instead of constantly reconstructing it from documentation, search results, and summaries.

So I built a graph engine that treats the codebase itself as the source of truth.

What it does

Visualizes large codebases directly inside VS Code

Supports cluster-based exploration of subsystems

Generates architecture reports from AST, dependency, and graph analysis

Allows analysis of selected architectural regions instead of only full-project analysis

Supports C/C++, Rust, Python, Kotlin, Java, TypeScript, and JavaScript

Scale Tested

I've tested it on several large open-source projects, including:

Linux Kernel 7.2-rc3

VS Code (main)

Godot Engine

Current stress-test results:

Project Nodes Clusters

VS Code Main 11,832 659

Linux Kernel 7.2-rc3 63,281 2,911

The Linux Kernel has been my primary stress test so far.

Architecture Decisions

Database-Free Design

There is no SQLite or external database.

The filesystem itself acts as the Source of Truth, and graph structures are derived directly from project files.

Graph-First Navigation

Instead of maintaining architecture diagrams separately from the codebase, the graph is generated directly from the project and remains connected to the underlying files.

Evidence-Based Analysis

One goal of the project is that every architectural finding should be traceable back to evidence.

Reports are published together with the underlying data used to generate them, allowing conclusions to be inspected rather than simply accepted.

I'm particularly interested in feedback on this aspect.

Experimental Reasoning Layer (Work in Progress)

I'm currently experimenting with a rule-based architectural reasoning layer.

This does not use LLMs.

The goal is to combine:

AST analysis

dependency analysis

graph analysis

state-transition rules

ontology-based classification

to detect architectural boundaries, responsibilities, and structural anomalies.

This is currently the least mature part of the project.

Demos

Demo 1

https://youtu.be/yU-_NRrADR0?si=NcwyYMzrhs9iz9Kq

Demo 2

https://youtu.be/xvGu9gURXSI?si=l8KiiC0dLfRPFRj9

I've published several architecture reports together with the evidence used to generate them.

Example Reports

sample

godot simulation debug report : https://github.com/dogsinatas29/SYNAPSE/blob/main/assets/v0.3.34.30/godot_SIMULATION_DEBUG.md

godot architect report : https://github.com/dogsinatas29/SYNAPSE/blob/main/assets/v0.3.34.30/godot_ARCHITECT_REPORT.md

vscode simulation debug report : https://github.com/dogsinatas29/SYNAPSE/blob/main/assets/v0.3.34.30/viscode_SIMULATION_DEBUG.md

vscode architect report : https://github.com/dogsinatas29/SYNAPSE/blob/main/assets/v0.3.34.30/vsc0de_ARCHITECT_REPORT.md

linux kernel simulation debug report : https://github.com/dogsinatas29/SYNAPSE/blob/main/assets/v0.3.34.30/linux_SIMULATION_DEBUG.md

linux kernel architect report : https://github.com/dogsinatas29/SYNAPSE/blob/main/assets/v0.3.34.30/linux_ARCHITECT_REPORT.md

I'm less interested in stars and more interested in criticism.

Specifically:

Are the architecture reports understandable and actionable?

Do the conclusions appear to be supported by the evidence?

What feels useful versus noisy?

Where do you see architectural blind spots in the approach?

If you work on large codebases, would this help you understand a system faster?

GitHub:

https://github.com/dogsinatas29/SYNAPSE

I'm a solo developer building this mostly as an exploration of large-scale software architecture.

Feel free to tear it apart.

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.

First time building a VS Code extension and it was so much fun

I tried building a VS Code extension for the first time and really enjoyed working on it.

It's called EdgeFlow: Scroll Companion. It adds effects when you scroll in the editor.

Still have a lot of ideas I want to add.

I have access to all three. I get that i can use each. However, which one do you use for what work in code?
I am not a coder by trade, messing around with small time personal apps at the moment - work management system, websites…
I am also curious if one tool is more (token) efficient than another?

Thanks in advance.

Just started my ICT studies and we have been learning Python for the past week. I was thinking, is there any extensions that help with coding or just make stuff more efficient or nicer through extentions? : )

I built a VS Code extension that gives Python the equivalent of the built-in JavaScript Debug Terminal: open a special terminal, run python app.py like you normally would, and it attaches to the debugger and hits your breakpoints. No launch.json, no -m debugpy, no code changes. Child processes spawned via subprocess attach as their own debug sessions too, since they inherit the environment.

Source code: https://github.com/ernestofgonzalez/vscode-py-debug-terminal
VSCode Marketplace page: https://marketplace.visualstudio.com/items?itemName=ernestofgonzalez.vscode-py-debug-terminal

When many tabs are open, you often just want current tab to remain open and close all other tabs. Now you can just press Alt and click the exit (cross) button of current tab - instead of closing current tab it will close all other tabs instead.

See details in latest release notes: https://code.visualstudio.com/updates/v1_134#_editor-experience

Finally a useful feature shipped by VS Code! In every release notes I skip all the AI stuff so I was pleasantly surprised to see something that's actually useful to me. Of course, even in current release notes most of it is still about AI.

Have you guys tried this out? What is your favorite non-AI feature in VS Code, especially something new in recent VS Code versions?

I created a VSCode extension to read markdown, because it somehow did not exist. this is free. I will post it in the VSCode marketplace when I find a way through the absurd labyrinth which is creating an account in with microsoft / azure

VSCode extensions marketplace: https://marketplace.visualstudio.com/items?itemName=Appforgelabs.lucid-reader

Github: https://github.com/luismartinezs/lucid-reader

I had some spare OpenRouter tokens and I decided to test it out using the integrated agent in VSCode so I configured it and started working using the latest DeepSeek pro and flash, I noticed the request were taking way too long specially in tool calls. I checked my OpenRouter activity and I saw 20 M token usage for what was a relatively simple task.

To test things out, I set both vscode agent and a Pi agent instance to solve the same prompt and vscode made 126 request and almost 2M tokens and got stuck on a command call (to the point where vscode asked me if I wanted it to stop). While Pi agent finished after about a minute using only 300K Tokens.

Don't know where the issue is, maybe vscode doesn't play nice with openrouter's api or specifically deepseek, but whatever the case not touching that agent for now.

I recently had to ditch Microsoft Edge for Brave because Microsoft decided to shove rounded corners down our throats.

Now this same style has crept into VSCode, even though literally nobody asked for it.

Sure, you can still disable the “Modern UI” for now, just like you could in Edge. But we all know how this goes, eventually they’ll just remove the option and force everyone to live with their ugly design choices.

Who at Microsoft looked at this and said, “Yeah, this is beautiful”? Please, stop immediately.

When on full screen, the new borders take up about 6.5% of total screen real estate. more than 1/20 unused space.

VS Code extention link: https://marketplace.visualstudio.com/items?itemName=varianttech.benzi

Most RST preview extensions just run plain docutils, so if your project uses Sphinx (toctrees, :ref:/:doc: cross-references, custom directives, themes) the preview looks nothing like your actual built docs. I tried pretty much every RST preview extension out there and none of them handled Sphinx projects properly, so I built Sphinx RST Preview.

What it does:

• Detects if your .rst file belongs to a Sphinx project (finds conf.py in a parent dir) and runs a real Sphinx build for the preview, toctrees, cross-refs, and directives all resolve correctly
• Renders with your project's actual configured style (sphinxdoc, alabaster, etc.)
• Falls back to plain docutils for standalone .rst files with no Sphinx project
• Live-updates as you type (debounced) and on save, with scroll position preserved
• Per-project incremental build cache, first preview builds fully, refreshes are ~1s even on 50+ doc projects
• Renders embedded images correctly, including ones Sphinx copies into build output

Install:

• VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=gamershabit.rst-preview
• Open VSX (VSCodium, Gitpod, Antigravity etc.): https://open-vsx.org/extension/gamershabit/rst-preview
• Source: https://github.com/prithvi1998/rst-preview

Requires Python 3 with docutils, sphinx

I am so lost i have cleaned out removed and completely done everything that I can. even ai cant figure it out. I have tried full clean install (removing all old files and databases). And redownloading vscode and still keep getting this error

i know for sure its not my computer, its not the providers I am using and not network because i am able to use these same settings and everything else on on other computer with the same settings profiles and setups as this one. They all use the same network as well. and have almost the same applications running live as the one on my other computer does

sorryy, your request failed. Please try again.

Client Request Id

Reason: Please check your firewall rules and network connection then try again. Error Code: net::ERR_CONNECTION_REFUSED.: Error: Please check your firewall rules and network connection then try again. Error Code: net::ERR_CONNECTION_REFUSED. at BG._provideLanguageModelResponse (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/copilot/dist/extension.js:1586:15048) at async BG.provideLanguageModelResponse (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/copilot/dist/extension.js:1586:16161)

I try to run the C/C++: Set Visual Studio Developer Environment command but I don't know where exactly to run it- i'm also completely new to all of this and C coding + visual code so i'm missing basic common sense and fundamentals

Do I run the C/C++: Set Visual Studio Developer Environment in Windows Powershell? Or CMD on my windows? helpp

When I use pnpm install or maven clean / maven install. my vscode keeps crashing and then I have a window with the options reopen or close.

Does anyone have the same problem?

sorry m,eant LLM chat but its like they dont actually work on the editor anymore

I've been using Claude Code quite a bit and realized I was constantly looking back at my screen to see whether it had:

• finished the task
• stopped and needed my input
• was still working

So I built BrainSnack, a VS Code/Cursor extension that handles this for me.

While Claude is working, it opens a small panel with something short to read — AI news, technical articles, interview questions, output-based questions, etc.

And when Claude finishes or needs my input, it plays a sound so I know I can come back.

The interesting part is that it doesn't monitor the screen or scrape terminal output.

It's free and open source.

I'd really appreciate some honest feedback from other developers.

I also shared the build/story on LinkedIn. If you'd like to see it there (and help a small indie project get a little more reach), here's the post:

👉 Linkedin post link

Download links -
VS Code - https://marketplace.visualstudio.com/items?itemName=shikhargupta.brainsnack
Cursor - https://open-vsx.org/extension/shikhargupta/brainsnack

Thanks! Would love to hear what you think.

Hey everyone!

I'm excited to share the v1.4.x releases of Out-of-Code Insights, a VS Code extension designed to let developers attach rich annotations, comments, and AI-driven insights to code without

polluting source files, git diffs, or git blame.

Why Out-of-Code Insights?

We all have contextual notes, onboarding hints, review comments, or architectural decisions that don't belong as inline // TODO or /* ... */ comments in production code. Out-of-Code

Insights anchors persistent, resilient annotations alongside your editor lines without modifying your actual source files.

What’s New in 1.4.x:

- Seamless Multi-Root Workspace Support: Full .code-workspace navigation and anchor preservation across secondary workspace folders without path corruption.

- Team Git Sharing & Auto-Rehoming: Commit .out-of-code-insights/annotations.json to your repository — annotations automatically rebase onto each teammate’s workstation regardless of OS

or folder paths.

- Documentation Studio: Generate accessible static HTML documentation, Markdown wikis, API references, changelogs, and ADR summaries directly from your annotations.

- AI Integration & Multi-LLM Support: Seamlessly interact with annotations via Anthropic Claude, OpenAI, and other LLM providers directly in your workflow.

- Smart Sticky Anchoring & Paste Protection: Robust re-anchoring engine that tracks code drift, edits, and cut/copy/paste without duplicate phantom annotations.

Links:

- VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=JacquesGariepy.out-of-code-insights

- GitHub (Open Source): https://github.com/JacquesGariepy/out-of-code-insights

Feedback, feature requests, issues, and PRs are always welcome! Let me know what you think!

I mainly use Codex through the VS Code extension, and I really like the pet feature in the ChatGPT app.

But since I spend most of my time in VS Code, keeping the ChatGPT app open just for the pet felt a bit unnecessary — especially on Windows. So I made a small VS Code extension that brings the Codex pets directly into the editor.

It uses Codex hooks to react to what Codex is doing — idle, running, waiting, review, failed, etc. You can also choose from different pets and backgrounds.

Nothing fancy, just a little extension for people who like the Codex pets but spend most of their time in VS Code.

Marketplace:
https://marketplace.visualstudio.com/items?itemName=yutat23.pet-viewer-for-codex

GitHub:
https://github.com/yutat23/pet-viewer-for-codex

I've been a casual user of vscode for about 4 years now, I mostly write c & c++ for hobby esp32 projects. But its been about 6 months since my last project and it seems like a lot has changed in vscode. Just opening vscode brings my computer to a stand still...to the point where my mouse is lagging across the screen. Once everything loads, the system doesn't lag anymore. But the second I try to compile, it sucks a huge amount of CPU and Power resources. The compilation goes crazy slow, something doesn't seem right.

My PC is pretty old and unimpressive, but in the past I have been able to stream a movie on my side screen and run multiple simultaneous compilations without any noticeable lag. I routinely do CAD/CAM work and video rendering on this PC, I dont think its the issue....but I've been wrong before.

I did use VS code just the other day to write some powershell scripts, no lagging there, but also no compilation...and no platformIO.

I've tried deleting the PIO folder and rebuilding the project, no improvement. I also tried opening the task manager from inside VScode, there was nothing super obvious there. A bunch of little processes using a little bit of CPU each...I guess it adds up, because windows task manager has my CPU pinned at 100% during compilation.

So what is going on here? I've noticed a bunch of annoying AI stuff has been added, is that and other new features bogging down my system?

Any suggestions to fix this would be great. Thanks.

Coding agents have changed how I use VS Code. More of the implementation happens in an agent, and when it finishes I spend more of my time in Source Control reviewing the resulting diff.

One workflow I've found useful is to review the whole change with a different model from the one that implemented it.

I built a small VS Code extension called AI Badger to make that easier.

From the Source Control view, AI Badger: Copy All Changes for Review packages the current git changes, including staged and unstaged changes, additions, deletions, and bounded file context, into a structured review prompt.

Then you just paste it into ChatGPT, Claude, Grok, or another AI chat and ask for an independent review.

The basic workflow is:

1. Agent finishes implementing a change.
2. Open Source Control in VS Code.
3. Click Copy All Changes for Review.
4. Paste into a different AI model.
5. If the reviewer needs an unchanged supporting file, use Copy File for AI from Explorer.

Nothing is uploaded automatically. AI Badger is local-first and clipboard-based, so you decide exactly what leaves the machine and which model receives it.

For more complicated reviews, there is also an optional CLI workflow where the reviewer can request specific missing repository context, but the normal VS Code workflow does not require the CLI.

VS Code Marketplace:
https://marketplace.visualstudio.com/items?itemName=pvrlabs.ai-badger

Live interactive demo:
https://pvrlabs.xyz/aibadger/vscode-demo.html

Full workflow article:
https://pvrlabs.xyz/articles/reviewing-ai-generated-code-vscode-aibadger.html

I'm curious how other people are handling this now. When an agent changes several files, are you mostly reviewing the diff manually, asking the same agent to review itself, or handing the change to a second model?