r/vscode

Hello! 👋

We launched a free and open-source project for developers: DevGlobe 🌍

The idea: while you're coding, you appear on a globe so you can:

• Track your coding stats (per repo, per file, per branch, per language) with real insights into your patterns
• List your projects (open source, side projects, or startups)
• Build a public dev profile (stats + projects + activity, ready to share like this)
• Motivate yourself to code (goals, badges, private leaderboards with friends)

Already using WakaTime? The endpoint is WakaTime-Compatible, just point your existing client at it and you'll appear on the globe with no new extension needed.

Privacy first:

• Anonymous mode → a random city in your country
• Standard mode → only your city is shown (never your exact location)
• Private mode → completely off the globe (if you just want the stats, goals, leaderboards, or to showcase your projects)

100% free

100% open source

Your personal data and your code are never sent to the backend

🌍 The Globe: https://devglobe.xyz/space

💻 Source code: https://github.com/Nako0/devglobe-extension

📦 Marketplace: https://marketplace.visualstudio.com/items?itemName=DevGlobe.devglobe

If you are interested or have any questions, everything is explained on the website, but don't hesitate to ask, I will be happy to answer your questions!

recently a lot of LLM providers are starting to limit the coding plan with limited quota, and i wanted to know how much would i need to spend on API keys if i would use the same usage on daily/monthly basis.

i decided to make this extension to visualize all my token usage based on actual usage from kilocode, so i can model the estimated token usage cost correctly if I were to use the API keys.

i also added a statusbar to show the z.ai LLM provider quota usage before it resets

• https://github.com/sweetim/token-lens

Programming the ESP32 using ESP-IDF for the first time, coming from the Arduino IDE. I cloned a Zigbee Lamp repo on github, and had a lot of Include path's errors. Is it normal to have to go through all my files and manually add every single path? This was so annoying, definitely not built to be a programmer.

shadcn has a block for almost everything except the one widget that shows up in every real app — a tree-view. I just shipped one: @grida/tree-view, installable as a shadcn block. One line in your project and you've got the same tree-view shape behind Figma's layers panel, VS Code's file explorer, Notion's sidebar, and Finder's columns — themed with your own Tailwind tokens, like every other shadcn component.

npx shadcn@latest add https://grida.co/r/tree-view-row.json

Five live themed demos on the landing page so you can see the same engine wearing five different skins: https://grida.co/packages/@grida/tree-view Drop it in, restyle it, ship it.

Hello, I have been having performance issues when using vscode.

First: The auto complete is slow/sluggish as seen in the video, It used to appear instantly when I typed 1 letter now it waits for 2 or 3 seconds before even showing suggestions.

Second: If I keep using vscode for an hour or two, When I try saving a file it hangs and keeps loading for a while before actually saving.

I have tried re-installing vscode entirely, re-installing windows, disabling all extensions, And I still have the same behavior. Has anyone faced something like this before?

FYI for everyone wanting an alternative to GitHub Copilot subscription after June 1st hits, DeepSeek V4 Flash/Pro has a VS Code extension that natively integrates with VS Code. It even has image support if you link it up to another vision model like Gemini 2.5 Flash Lite (which you can pay either with GHCP or OpenRouter or anything).

https://api-docs.deepseek.com/quick_start/agent_integrations/github_copilot
https://github.com/Vizards/deepseek-v4-for-copilot

I do think that this is the best option after June 1st happens.

Hey,

Honestly I've been using Antigravity as my IDE, and I know it's a fork of VS Code.

Since I use Pi in the terminal, i need more vertical space for it and what I'm looking for is for a way to customize the layout as depicted. In Antigravity I havent found a way to do this... Is this possible with VS Code?

I try to use the sass command to convert the scss in homePage.scss to homePage.css and it keeps showing "Error: no such file" when it's clearly there. I tried changing the paths and the directories but it gives the same error.

I would really appreciate the help.

Hey,

Honestly I've been using Cursor as my IDE, and I know it's a fork of VS Code.

Since I use Claude Code in the terminal, i need more vertical space for it and what I'm looking for is for a way to customize the layout as depicted. In Cursor I havent found a way to do this... Is this possible with VS Code?

We’ve been working on Multimeter for about a year. The idea started from a simple question: what if API testing worked more like normal files in Git? Not exportable artifacts. Actual project files. The kind that makes life easier for developers, testers, teams, and probably AI agents too.

Multimeter is a VS Code extension for writing and running API tests as plain YAML, directly inside the editor. The goal is to make API testing feel less like managing a separate app full of hidden state and more like working with normal project files: readable, reviewable, reusable, runnable in CI, and at the same time, super friendly in the UI for everyday use.

We know there are already some solid Git-based API tools out there, but we wanted a different abstraction.

Instead of treating every request as a mostly standalone item, Multimeter lets you define APIs first and then build test flows on top of them.

So an API definition can describe things like login, create user, or get order, and then tests can call those APIs, pass inputs, assert outputs, chain responses, branch, loop, and run as suites.

A tiny API definition looks like this:

type: api url: https://test.mmt.dev/echo method: post format: json body: name: Multimeter message: Hello from mmt!

Then a type: test file can call that API as part of a flow instead of duplicating the whole request each time.

That was one of the main things we wanted: not just collections of requests, but reusable API building blocks, test flows, and suites that behave more like actual test automation.

Current features:

local-first: no cloud sync or account needed

HTTP, WebSocket, gRPC, and GraphQL requests

reusable API definitions with inputs and outputs

reusable test flows with calls, assertions, checks, conditions, and loops

test suites instead of only collections

environments and presets

mock servers

API docs generation

Postman/OpenAPI import

CLI runner for CI

beta load testing

The mental model is basically: “Docker Compose, but for API testing.” Not because YAML magically fixes life, but because boring files in Git are still one of the best collaboration tools we have.

We’d genuinely love feedback from people who build or debug APIs regularly:

Does the API-definition + test-flow model make sense?

Do suites feel more useful than collections for larger projects?

What would make you trust this in a real project?

What features or workflow improvements would you want?

Website: https://mmt.dev

Repo: https://github.com/mshobeyri/multimeter/

Demo: https://mmt.dev/demos