VS Code Extension Link Portability

Refactor non-portable extension paths in VS Code settings.json to tilde-based references.

1|Updated Nov 26, 2025

Search Tags:#vscode #extension #settings #portability #portable #path-refactor #tilde

Ready to run

npx skills add https://github.com/Baneeishaque/ai-suite --skill vs-code-extension-link-portability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: VS Code Extension Link Portability
Source: https://github.com/Baneeishaque/ai-suite/tree/main/.agents/skills/vscode_extension_portability
Command: npx skills add https://github.com/Baneeishaque/ai-suite --skill vs-code-extension-link-portability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VS Code often stores extension-generated paths in settings.json that are machine-specific and non-portable. This leads to broken references after environment changes or when sharing configurations.

Core Features & Use Cases

Detection & Refactor: Identifies extension-created paths that rely on temporary caches or absolute user prefixes and normalizes them.
Portable Mapping: Rewrites paths to use the tilde home reference (e.g., ~) and redirects to a stable internal storage location for extensions.
Use Case: Migrating a developer profile to a new machine or sharing a VS Code setup across teammates without breaking links.

Quick Start

Execute the refactor script against your settings.json to rewrite non-portable extension paths to portable tilde-based references.

Frequently Asked Questions about VS Code Extension Link Portability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix non-portable VS Code extension paths in settings.json?▼

To fix non-portable VS Code extension paths in settings.json, identify and refactor machine-specific paths generated by extensions, replacing temporary cache directories or absolute home prefixes with tilde-based references mapped to a stable internal storage location.

Why do my VS Code settings break with absolute paths like /Users or /var/folders after migrating machines?▼

VS Code settings break after migrating machines because extensions often store absolute paths like /Users or temporary /var/folders caches in settings.json, creating machine-specific references that fail when the environment changes or configurations are shared.

What is the best way to make VS Code extension configurations portable across different machines?▼

The best way to make VS Code extension configurations portable is to rewrite non-portable absolute paths in settings.json to use tilde home references, redirecting extension links to a stable internal directory such as ~/.antigravity/extensions/.

Does VS Code settings portability require mapping to a specific internal extension directory?▼

Yes, VS Code settings portability requires mapping refactored paths to a stable internal extension directory, such as ~/.antigravity/extensions/, to satisfy portability requirements and ensure extension links remain intact across different environments.

Can I refactor temporary cache directories out of my VS Code settings.json automatically?▼

Yes, you can refactor temporary cache directories out of VS Code settings.json by executing a refactor script that targets paths generated by extensions and normalizes them into portable tilde-based references for consistent configuration sharing.