---
title: "#vscode-extensions articles | Hashnode"
description: "Explore 812 articles tagged #vscode-extensions on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/vscode-extensions"
---

Tag

# #vscode-extensions

812 posts · 206 followers

[Eren Çolak](https://hashnode.com/@erenxcolakx) · [12h ago](https://hashnode.com/posts/11-things-i-learned-building-a-tool-on-claude-code-hooks/6af4261127d0807c65d20e0b)

### [11 things I learned building a tool on Claude Code hooks](https://paneherd.hashnode.dev/11-things-i-learned-building-a-tool-on-claude-code-hooks?utm_source=hashnode&utm_medium=feed)

I usually have four or five Claude Code sessions open at once, and my problem was never the agents. It was me: a session would sit on a permission prompt for twenty minutes in a tab I wasn't looking a

6 min read · [paneherd.hashnode.dev](https://paneherd.hashnode.dev/11-things-i-learned-building-a-tool-on-claude-code-hooks?utm_source=hashnode&utm_medium=feed)

[3](https://hashnode.com/posts/11-things-i-learned-building-a-tool-on-claude-code-hooks/6af4261127d0807c65d20e0b)

[Eren Çolak](https://hashnode.com/@erenxcolakx) · [9h ago](https://hashnode.com/posts/how-to-get-notified-when-claude-code-finishes-or-needs-permission/6af4494f5d5cabf5e61505ae)

### [How to get notified when Claude Code finishes or needs permission](https://paneherd.hashnode.dev/how-to-get-notified-when-claude-code-finishes-or-needs-permission?utm_source=hashnode&utm_medium=feed)

If you run Claude Code in the VS Code or Cursor terminal, you get no alert when it finishes or stops for a permission prompt. Claude Code sends a desktop notification on its own only in a few terminal

5 min read · [paneherd.hashnode.dev](https://paneherd.hashnode.dev/how-to-get-notified-when-claude-code-finishes-or-needs-permission?utm_source=hashnode&utm_medium=feed)

[FreeRave](https://hashnode.com/@freerave) · [1d ago](https://hashnode.com/posts/dotshare-part-1-from-an-ai-draft-to-a-reviewed-social-post/6af304e36071dcd53ce37a03)

### [DotShare Part 1: From an AI draft to a reviewed social post](https://freerave.hashnode.dev/dotshare-part-1-from-an-ai-draft-to-a-reviewed-social-post?utm_source=hashnode&utm_medium=feed)

Install DotShare, connect Codex to its local MCP server, and review and publish the same draft from VS Code.

5 min read · [freerave.hashnode.dev](https://freerave.hashnode.dev/dotshare-part-1-from-an-ai-draft-to-a-reviewed-social-post?utm_source=hashnode&utm_medium=feed)

[Eren Çolak](https://hashnode.com/@erenxcolakx) · [Nov 4](https://hashnode.com/posts/how-to-run-multiple-claude-code-sessions-at-once/6aeafd3138aab66aabcfc66b)

### [How to run multiple Claude Code sessions at once](https://paneherd.hashnode.dev/how-to-run-multiple-claude-code-sessions-at-once?utm_source=hashnode&utm_medium=feed)

I make Paneherd, which is option 4 below. Originally published at paneherd.com. Claude Code works best on one focused task at a time, so the way to get more done is to run several sessions in parallel

4 min read · [paneherd.hashnode.dev](https://paneherd.hashnode.dev/how-to-run-multiple-claude-code-sessions-at-once?utm_source=hashnode&utm_medium=feed)

[Ilja Krasnjanski](https://hashnode.com/@iljakrasnjanski) · [Nov 2](https://hashnode.com/posts/vsix-editor-execution/6ae835efaecf55aa7e9d0c27)

### [How a Malicious VSIX Uses the Signed Editor Runtime](https://unk-deaddrop.hashnode.dev/vsix-editor-execution?utm_source=hashnode&utm_medium=feed)

How a fake Google Update Support extension installs its components and runs the editor's own Electron binary as a Node interpreter.

8 min read · [unk-deaddrop.hashnode.dev](https://unk-deaddrop.hashnode.dev/vsix-editor-execution?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/vsix-editor-execution/6ae835efaecf55aa7e9d0c27)

[JAY TANK](https://hashnode.com/@jaytank) · [Oct 12](https://hashnode.com/posts/portclash-port-is-already-allocated-eaddrinuse/6acc530264de1b3fc30a96f5)

### [Bind for 0.0.0.0:5432 failed: port is already allocated - find port clashes before you run docker compose up](https://jaytank.hashnode.dev/portclash-port-is-already-allocated-eaddrinuse?utm_source=hashnode&utm_medium=feed)

Port is already allocated" from Docker and EADDRINUSE from Node mean two things want one host port, and both are usually already written down in the repo. Why it happens, how to fix it, and a free VS Code extension that flags port clashes before anything starts.

10 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/portclash-port-is-already-allocated-eaddrinuse?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/portclash-port-is-already-allocated-eaddrinuse/6acc530264de1b3fc30a96f5)

[FreeRave](https://hashnode.com/@freerave) · [Oct 8](https://hashnode.com/posts/dotshare-ai-3-5-2-from-git-tags-to-technical-articles-you-can-review/6ac776741e21dbe8f9608d6b)

### [DotShare AI 3.5.2: From Git Tags to Technical Articles You Can Review](https://freerave.hashnode.dev/dotshare-ai-3-5-2-from-git-tags-to-technical-articles-you-can-review?utm_source=hashnode&utm_medium=feed)

A deep dive into DotShare 3.5.2: release-aware AI articles, verified code excerpts, Dev.to live preview, and safer credential handling.

18 min read · [freerave.hashnode.dev](https://freerave.hashnode.dev/dotshare-ai-3-5-2-from-git-tags-to-technical-articles-you-can-review?utm_source=hashnode&utm_medium=feed)

[JAY TANK](https://hashnode.com/@jaytank) · [Oct 1](https://hashnode.com/posts/locksettle-fix-lockfile-merge-conflicts/6abdd491b381eedf7657ca9d)

### [How to fix package-lock.json merge conflicts (and yarn.lock, poetry.lock, go.sum) the right way](https://jaytank.hashnode.dev/locksettle-fix-lockfile-merge-conflicts?utm_source=hashnode&utm_medium=feed)

Never hand-edit a conflicted lockfile, and never click "Accept Both". Resolve the manifest, then let the package manager regenerate the lock. Here is the exact command for npm, Yarn, pnpm, Poetry, uv, Cargo, Go, Composer, Bundler and Pipenv, why each one is different, and LockSettle, a free VS Code extension that runs the right one for you.

10 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/locksettle-fix-lockfile-merge-conflicts?utm_source=hashnode&utm_medium=feed)

[JAY TANK](https://hashnode.com/@jaytank) · [Sep 30](https://hashnode.com/posts/afterpull-what-to-run-after-git-pull/6abc8234e06799beb5a99ed3)

### [Your app broke after git pull? The after-pull checklist every team forgets](https://jaytank.hashnode.dev/afterpull-what-to-run-after-git-pull?utm_source=hashnode&utm_medium=feed)

A pull can quietly bring in new dependencies, new migrations, new .env keys, a changed Dockerfile or a bumped Node version, and nothing tells you. Here is the checklist I run after every pull (npm ci vs npm install, migrations, .env drift, stale containers), why post-merge hooks do not really solve it, and AfterPull, a free VS Code extension that works out the list for you.

9 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/afterpull-what-to-run-after-git-pull?utm_source=hashnode&utm_medium=feed)

[JAY TANK](https://hashnode.com/@jaytank) · [Sep 29](https://hashnode.com/posts/commitsieve-stop-committing-env-files-vscode/6abb308314f7da592909936d)

### [Stop committing .env files, node\_modules and it.only: check your staged changes before you press Commit](https://jaytank.hashnode.dev/commitsieve-stop-committing-env-files-vscode?utm_source=hashnode&utm_medium=feed)

Most "oops" commits are a .env file, a huge dump, node\_modules or a leftover it.only, not hard bugs. Why hooks and .gitignore miss them, how to clean up, and a free VS Code extension that checks the git index live.

10 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/commitsieve-stop-committing-env-files-vscode?utm_source=hashnode&utm_medium=feed)
