What problem does it solve? Running multiple Hermes profiles spawns a separate serve backend per profile, each launching its full MCP server list — roughly 60 node.exe processes consuming ~3.8 GB of RAM on a loaded Windows machine, causing system lag and stutter. ## Core Features & Use Cases - RAM Diagnosis: PowerShell commands to measure top memory consumers, count MCP node processes, and identify which profile serves are live before making changes. - Active-Profile Watchdog: A scheduled-task PowerShell script that kills serve backends for inactive profiles every 30 seconds while protecting the active profile, the default gateway, and any profile with a live session lease. - Config-Based MCP Scoping: An alternative fix that adds an empty mcp_servers: {} block to inactive profiles so they spawn zero node processes without killing anything. - Use Case: A user with 7 Hermes profiles notices their laptop lagging on launch; after setting the active profile and running the watchdog, free RAM rises from 3.4 GB to 8.5 GB while active sessions stay untouched. ## Quick Start Ask the agent to diagnose Hermes RAM usage on this Windows machine and set up the profile watchdog with 'vibe' as the active profile.