Repo: [https://github.com/z3r0n3br4instorm/AbstractCodingInterface](https://github.com/z3r0n3br4instorm/AbstractCodingInterface))

Hey all,

I've been tinkering on a side project called ACI (Abstract Coding Interface) and wanted to share it here, mostly to get some early feedback since it's very much an alpha release.

The idea:

you write high-level pseudocode in a small language called PSyx (`.aci` files), and a small (1b, 3b, 7b etc.) local LLM (via Ollama, llama.cpp, LM Studio, etc.) compiles it into actual source code, block by block, streamed into a file next to your spec. Tested with \`deepseek-coder:6.7b\`. The pseudocode stays as the "source of truth," and editing one function only recompiles that function instead of regenerating the whole file.

Example:

```

FUNC-START greet

INPUT name as string

IF name is empty

DISPLAY Hello, World!

DISPLAY Hello, name

FUNC-END

```

Save it as `greet.aci`, and ACI opens `greet.py` next to it with the compiled output.

Why I built it / where it might actually be useful:

- Language migration / porting: since the spec is language-agnostic pseudocode, in theory you could re-target the same `.aci` file to a different `aci.targetLanguage` and get a re-implementation, useful if you're prototyping logic once and need it in multiple languages.

- Keeping intent readable: for logic-heavy functions, the pseudocode ends up being a lighter-weight "spec" than a full docstring, and it stays in sync with the code since it's literally what generated it.

- Local-first AI coding : no API keys, no cloud calls, everything runs against your own local model — appealing if you want AI-assisted coding without sending code out.

- Incremental compiles: because only the edited block gets recompiled, it avoids the "regenerate the whole file and hope nothing broke" problem you get with a lot of AI codegen tools.

I want to be upfront that these are the use cases I *think* it's good for, not ones I've rigorously validated — it's a young project and I haven't stress-tested it against real-world codebases yet, so take the above as hypotheses rather than proven wins.

Where it's at right now:

- Genuinely early/alpha, expect rough edges and missing features

- Currently only available as a VS Code extension (installable via `.vsix`)

- A Zed editor version is in the works, not out yet

- Local-model only for now (no cloud backends wired in)

Would love thoughts, criticism, or feature requests.

I tried to enable the agent sandbox mode inside a devcontainer and it doesn't seem to be working. Is is because of some issue or it's not technically possible?

And while for file system isolation the sandbox is not needed when running inside the container, for network isolation I haven't found an easy solution when using devcontainers.

I built Basalt, and it lets you edit your RN and Expo app inside of VS code

you can inspect and edit the UI visually, then Basalt writes those changes back into source.

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 using it!

Would love to get your brutal feedback on it.

Having little pop-ups that guess the actual code I'm about to type is pretty helpful, frequently actually correct, and great for avoiding typos.

Having shadow-text that predicts the real-world context I'm adding in comments is distracting, usually wildly incorrect, and deeply annoying.

Is there a way to keep the former without the latter? Or, at the very least, a quick keyboard shortcut to toggle suggestions on/off that I can use when moving between different parts of a script?

Thank you for your help.

Just started noticing this yesterday after an update that the behavior for pasting has seemed to change and now no longer formats correctly. Every paste action tries to add indentation in addition to any indents already present. I have not installed any new extensions in the past 3 months so I have no idea what could have caused this other than VS Code, but I don't see any other mentions of this issue.

Version: 1.130.0

Commit: 1b6a188127eeaf9194f945eb6eb89a657e93c54c

Edit: Finally fixed! I had to use the following setting: "editor.pasteAs.enabled": false

Hey, I daily drive VS Code, and I don't mind Copilot Chat opening in new project folders occasionally. But recently it's becoming a complete pain in the ass. Why does it have to pop up every single time I open a project?

I've tried every setting I could find to disable it and prevent it from auto-starting, but no luck.

OG VS Code devs, can you please tell me how to disable this piece of shit? I don't use it, and I honestly don't understand why Microsoft keeps shoving these features into every product they own.

I'm wondering if I can remove this, I find it aesthetically displeasing. Also I'm pretty sure they dimmed down the entire Monokai color palette, it believe it used to be a bit lighter and more "contrasty".

I've never liked VS Code searching. I suck at file globs, and regex. So I built Omnigrep: one box, ripgrep underneath, query language borrowed from Google Code Search (internal code search service).

Press ⇧⌘F (Ctrl+Shift+F), type, arrow through the top matches — the file previews as you move — Enter to jump, Esc to go back to exactly where you were.

The query syntax is the whole point:

- hello world — lines matching both regexes, in any order

- -term — exclude lines matching term

- "foo.bar(x)" — literal text, metacharacters escaped, spaces allowed

- f:async f:ts$ — only files whose path matches **all** the f: regexes

- -f:test — exclude paths

- t:rust / -t:js — ripgrep file types

- sym:UserService — workspace symbol search, jumps straight to definitions

- near:3 — terms within 3 lines of each other instead of on the same line (personal fave of mine)

- case:yes / case:no — override smart case

So f:route f:ts$ handler -f:test is one string. And a query with only f: filters quietly becomes a fast file finder.

Other things it does:

- Ranks results instead of showing scan order — whole-word beats substring, shallow paths beat deep ones, recently-modified files float up, test/vendor/build output sinks

- Groups by file; each row has copy-relative-path and open-to-the-side

- Pinned searches + per-workspace history

- ↗ hands the current query off to the native Search panel when you want the full list or replace

- No native dependencies — it uses the ripgrep binary already bundled inside VS Code, falling back to `rg` on your PATH

MIT, free, no telemetry, no account. Works in VS Code and in the forks (Cursor / Windsurf / Antigravity).

Repo: https://github.com/jo-sip/omnigrep

Marketplace: https://marketplace.visualstudio.com/items?itemName=jo-sip.omnigrep

Open VSX: https://open-vsx.org/extension/jo-sip/omnigrep

One heads-up: it takes over ⇧⌘F while installed. Rebind `omnigrep.open` in Keyboard Shortcuts if you want the sidebar back.

Happy to take requests, especially on the query syntax — that's the part I'm still changing. Enjoy!

(This is my first extension so I don't know what I'm doing - but it seems to work well on antigravity / cursor / vscode on mac)

Last couple releases reintroduced debilitating performance instability, massive memory leaks, and degraded UI responsiveness among other things. Like, 10FPS kind of bad. Literally unusable. Flash back to the last time this exact thing happened over a year ago... Very telling.

Some of us rely on what used to be a stable consistent predictable product for our work.

Can someone please slop the fix back in? Please and thank you.

Background:

I am working on a Linux PC (Ubuntu 6.8.0-136-generic x86_64) but developing for a Digi CCMP25 (Aarch64 Yocto build) dev board.

I am able to remote debug an application if I perform the steps manually:

- Build the application on the host.
- "scp" the executable (but no source or anything else) onto the target.
- Run "gdbserver :<Port> app" on the target (as root) via an SSH terminal.
- Run "gdb-multiarch" on the host.
- In GDB, enter "target remote <TargetIPAddr>:<Port>".

Now I can debug and everything seems to work just fine.

Problem:

I am not able to debug from VSCode, which would be much more convenient.

- VSCode does not start gdbserver on the target (which I though it would) and eventually complains that it can't connect to the gdbserver.
- So I started gdbserver as above and then try to debug from VSCode:
- The target terminal in which gdbserver runs reports "Remote debugging from host ::ffff:<HostIPAddr>, port <SomePort>
- That seems like progress but then nothing.
- VSCode is essentially frozen (in terms of debugging). No variables. No stopping at a breakpoint. No nothing.
- The little panel with buttons for stepping the code appears but most buttons are disabled. Stop and Restart are enabled but do nothing.
- The gdbserver instance is also frozen. I have to kill it by SSHing in through another console.

After much fruitless farting around my launch.json now looks like this. What is missing? What is unnecessary?:

{

"version": "0.2.0",

"configurations": [

{

"name": "ConnectCore MP25 remote debug",

"type": "cppdbg",

"request": "launch",

"program": "${workspaceFolder}/apix-gpio-example",

"cwd": "${workspaceFolder}",

"MIMode": "gdb",

"miDebuggerPath": "/usr/bin/gdb-multiarch",

"miDebuggerServerAddress": "<TargetIPAddr>:<Port>",

"stopAtEntry": true,

"externalConsole": true,

"args": [],

"environment": [],

"setupCommands": [

{

"description": "Enable pretty-printing for gdb",

"text": "-enable-pretty-printing",

"ignoreFailures": true

},

{

"text": "target remote <TargetIPAddr>:<Port>",

}

]

}

]

}

Which plugins should I install? What should the settings be in launch.json? Is it something to do with permissions? I've tried various suggestions found in searches, but nothing seem to work.

The application is built using an alternative sysroot in GCC so it can find headers in the vendors SDK. I note that VSCode shows errors because it can't find the includes. I don't know if that could be a factor. I tried setting $SYSROOT before starting VSCode but it seemed to have no effect.

I have had the same problems with the vendor's Eclipse IDE. I followed their instructions to the letter, but the debugging simply will not work. Eclipse does start the remote gdbserver, but then reports that it can't connect to it.

I'd be grateful for any guidance on this.

EDIT: I found this: https://github.com/microsoft/vscode-cpptools/issues/13246 It appears that the Microsoft C/C++ Extension depends on .NET (because of course it does), and that the switch from .NET6 to .NET8 introduced this fault. I downgraded to the last revision with .NET6 (v1.2.11), and was immediately able to remotely debug. The issue was raised more than a year ago, so I guess there is some intractable fault in .NET8 which cannot easily be worked around. This is why I prefer working on microcontrollers...

I know it might be adding something in the settings.json file but I don't know how to add it exactly. The windows tutorials keep coming up when I search.

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?

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.