📖 Overview

OmniMem displays the real RAM usage of your editor runtime (Main process, Renderers, GPU, Extension Host, and Helpers) directly in your status bar. It also scans your installed extensions folder to find duplicate versions lingering on disk.

Unlike existing memory monitors that hardcode binary names (breaking as soon as you switch to Cursor, Windsurf, Antigravity IDE, or Devin), OmniMem is designed from the ground up to be 100% fork-agnostic.

📸 Screenshots

Status bar preview showing real-time memory consumption:

✨ Features

• ⚡ Real-Time RAM in Status Bar: Sums the exact Resident Set Size (RSS / Working Set) of all processes belonging to this editor instance.
• 🎨 Configurable Display Formats: Choose how memory is formatted (used/total, usedOnly, percentage, or compact).
• 🔍 Duplicate Extension Detector: Scans your active editor's extensions directory and reports extensions with multiple leftover versions on disk.
• 🚀 Zero Runtime Dependencies: Pure Node.js & VS Code API with zero bloat (< 10 KB footprint).
• 🔄 Live Hot-Reloading: Configuration changes (refresh interval, format) apply immediately without restarting the editor.
• 🛠️ Click-to-Refresh: Click the status bar item anytime to force an instant memory refresh.

🌐 Supported Editors

Works seamlessly across all modern Electron / VS Code-based editors:

⚙️ Configuration

You can customize OmniMem via your editor's settings.json or through the Settings UI (OmniMem):

⌨️ Commands

Access these commands from the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows/Linux):

• OmniMem: Refresh Memory Usage — Instantly recalculates and updates the status bar.
• OmniMem: Check Duplicate Extensions — Checks your extensions folder for duplicate installed versions and opens a summary report.

🧠 How It Works (Under the Hood)

OmniMem identifies processes using runtime introspection rather than hardcoded process names:

• macOS: Electron ships helper processes (Renderer, GPU, Plugin Host) as sub-bundles inside the main .app bundle. OmniMem inspects process.execPath, resolves the .app root, and sums the RSS of all child processes running under that bundle root.
• Linux: Electron launches child processes from the main binary path with --type=... parameters. OmniMem tracks all processes matching the exact execPath.
• Windows: Queries process working sets via Get-CimInstance Win32_Process matching the active ExecutablePath.
• Duplicate Detection: Uses path.dirname(context.extensionPath) to automatically point to the current editor's extension storage (~/.cursor/extensions, ~/.windsurf/extensions, ~/.vscode/extensions, etc.).

Note on external tools: OmniMem tracks all processes managed by the editor application. External CLI tools and compilers installed globally on the system (outside the editor bundle) are not included.

📦 Installation

Marketplace Links

• VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=SergioSuarezGil.omnimem
• Open VSX Registry: https://open-vsx.org/extension/SergioSuarezGil/omnimem
• GitHub Releases (VSIX): https://github.com/SergioSuarezGil/OmniMem-IDE-RAM-Monitor/releases

From GitHub Releases (recommended)

1. Open the repository Releases section.
2. Download the .vsix attached to the version you want (for example omnimem-x.y.z.vsix).
3. Install it from your editor UI (Extensions -> Install from VSIX...) or with CLI.

From VSIX Package

1. Package or download the .vsix file:

   npm run package
   

2. Install it in your editor of choice via CLI or through the UI (Extensions → Install from VSIX...):

# VS Code
code --install-extension omnimem-x.y.z.vsix

# Cursor
cursor --install-extension omnimem-x.y.z.vsix

# Windsurf
windsurf --install-extension omnimem-x.y.z.vsix

# Antigravity IDE
antigravity-ide --install-extension omnimem-x.y.z.vsix

# Devin Desktop
devin-desktop --install-extension omnimem-x.y.z.vsix

🚀 Release Process

Development follows a lightweight Git Flow: feature branches are integrated into develop, releases are prepared locally, and only the maintainer promotes develop to main.

Required repository secrets

• VSCE_PAT: Personal Access Token for VS Code Marketplace publishing.
• OVSX_PAT: Personal Access Token for Open VSX publishing.

Preparing and publishing a release

Run the release script from a clean develop branch:

# Infer patch, minor, or major from commits since the latest version tag
npm run release

# Optionally request an equal or higher version increment
npm run release -- minor

The script verifies the branch history, runs tests, packages the extension, updates the version, and generates CHANGELOG.md. It does not commit, tag, push, merge, or publish anything.

After reviewing and committing the generated files, push develop and merge it into main. A push to main runs .github/workflows/release.yml, which validates the prepared version, publishes to both marketplaces, and creates the tag and GitHub Release.

About VS Code Marketplace vs other editors

• VS Code / Cursor / Windsurf / Antigravity IDE / Devin / Trae: many forks can install VSIX directly, and some also consume Marketplace-compatible sources.
• VSCodium usually relies on Open VSX, not Microsoft Marketplace.
• Publishing to both VS Code Marketplace and Open VSX maximizes compatibility and avoids manual duplication.

🛠️ Development & Testing

Prerequisites

• Node.js 20 or later. If you use nvm, run nvm use from the repository root.

# Install dependencies
npm install

# Run unit test suite
npm test

# Run tests with code coverage report
npm run test:coverage

# Build VSIX package
npm run package

Commit types and release impact

The release process uses Conventional Commit types to determine whether a new version is required and which version component to increment.

Add [skip release] to a commit message when a normally publishable change should not create a new release:

fix: adjust development-only diagnostics [skip release]

📄 License

MIT © 2026