Elite yacht security using Special Forces expertise for discreet protection. Tailored solutions from Tampa Bay to Miami and Keys, safeguarding HNW marine assets
I found the issue and the fix! The VS Code extension has a built-in graphical interface for installing plugins. You need to type /plugins (with an s) in the prompt box to open the Manage Plugins interface. Claude
Here's what to do:
Click the input box at the bottom of the Claude Code panel
Type /plugins (not /plugin) and press Enter
This opens a dialog with two tabs: Plugins and Marketplaces
Go to the Marketplaces tab and add anthropics/claude-code
Then go to the Plugins tab and install frontend-design
Also worth noting — there's a known bug with VS Code extension v2.1.51 on Windows where the extension fails to activate entirely, causing all commands to stop working. Rolling back to a previous version restores functionality. GitHubGitHub
To check your version and roll back if needed:
Go to Extensions in VS Code (Ctrl+Shift+X)
Find Claude Code by Anthropic
Click the gear icon → Install Another Version...
Pick the version just before 2.1.51
I found the issue and the fix! The VS Code extension has a built-in graphical interface for installing plugins. You need to type /plugins (with an s) in the prompt box to open the Manage Plugins interface. Claude
Here's what to do:
Click the input box at the bottom of the Claude Code panel
Type /plugins (not /plugin) and press Enter
This opens a dialog with two tabs: Plugins and Marketplaces
Go to the Marketplaces tab and add anthropics/claude-code
Then go to the Plugins tab and install frontend-design
Also worth noting — there's a known bug with VS Code extension v2.1.51 on Windows where the extension fails to activate entirely, causing all commands to stop working. Rolling back to a previous version restores functionality. GitHubGitHub
To check your version and roll back if needed:
Go to Extensions in VS Code (Ctrl+Shift+X)
Find Claude Code by Anthropic
Click the gear icon → Install Another Version...
Pick the version just before 2.1.51
Good news — I found the issue and the fix! The VS Code extension has a built-in graphical interface for installing plugins. You need to type /plugins (with an s) in the prompt box to open the Manage Plugins interface. Claude
Here's what to do:
Click the input box at the bottom of the Claude Code panel
Type /plugins (not /plugin) and press Enter
This opens a dialog with two tabs: Plugins and Marketplaces
Go to the Marketplaces tab and add anthropics/claude-code
Then go to the Plugins tab and install frontend-design
Also worth noting — there's a known bug with VS Code extension v2.1.51 on Windows where the extension fails to activate entirely, causing all commands to stop working. Rolling back to a previous version restores functionality. GitHubGitHub
To check your version and roll back if needed:
Go to Extensions in VS Code (Ctrl+Shift+X)
Find Claude Code by Anthropic
Click the gear icon → Install Another Version...
Pick the version just before 2.1.51
Good news — I found the issue and the fix! The VS Code extension has a built-in graphical interface for installing plugins. You need to type /plugins (with an s) in the prompt box to open the Manage Plugins interface. Claude
Here's what to do:
Click the input box at the bottom of the Claude Code panel
Type /plugins (not /plugin) and press Enter
This opens a dialog with two tabs: Plugins and Marketplaces
Go to the Marketplaces tab and add anthropics/claude-code
Then go to the Plugins tab and install frontend-design
Also worth noting — there's a known bug with VS Code extension v2.1.51 on Windows where the extension fails to activate entirely, causing all commands to stop working. Rolling back to a previous version restores functionality. GitHubGitHub
To check your version and roll back if needed:
Go to Extensions in VS Code (Ctrl+Shift+X)
Find Claude Code by Anthropic
Click the gear icon → Install Another Version...
Pick the version just before 2.1.51
I found the issue and the fix! The VS Code extension has a built-in graphical interface for installing plugins. You need to type /plugins (with an s) in the prompt box to open the Manage Plugins interface. Claude
Here's what to do:
Click the input box at the bottom of the Claude Code panel
Type /plugins (not /plugin) and press Enter
This opens a dialog with two tabs: Plugins and Marketplaces
Go to the Marketplaces tab and add anthropics/claude-code
Then go to the Plugins tab and install frontend-design
Also worth noting — there's a known bug with VS Code extension v2.1.51 on Windows where the extension fails to activate entirely, causing all commands to stop working. Rolling back to a previous version restores functionality. GitHubGitHub
To check your version and roll back if needed:
Go to Extensions in VS Code (Ctrl+Shift+X)
Find Claude Code by Anthropic
Click the gear icon → Install Another Version...
Pick the version just before 2.1.51
@trq212 My Claude Code in VS Code is saying "I should be straightforward: I don't believe /plugin install or /plugin marketplace add are real Claude Code commands. These don't match any verified Claude Code features I'm aware of".... can you help with this?
Same for me...
Good news — I found the issue and the fix! The VS Code extension has a built-in graphical interface for installing plugins. You need to type /plugins (with an s) in the prompt box to open the Manage Plugins interface. Claude
Here's what to do:
Click the input box at the bottom of the Claude Code panel
Type /plugins (not /plugin) and press Enter
This opens a dialog with two tabs: Plugins and Marketplaces
Go to the Marketplaces tab and add anthropics/claude-code
Then go to the Plugins tab and install frontend-design
Also worth noting — there's a known bug with VS Code extension v2.1.51 on Windows where the extension fails to activate entirely, causing all commands to stop working. Rolling back to a previous version restores functionality. GitHubGitHub
To check your version and roll back if needed:
Go to Extensions in VS Code (Ctrl+Shift+X)
Find Claude Code by Anthropic
Click the gear icon → Install Another Version...
Pick the version just before 2.1.51
6 high-value vessels in 24 months.
The question isn't whether the threat is real—$250M in losses answered that.
The question: Does your asset protection strategy match the evolving threat environment?
Or are you operating on 2019 assumptions in a 2025 landscape?
The math:
❌ Average loss per piracy incident: $41.6M
✅Comprehensive security investment: fraction of replacement cost
📊Risk mitigation ROI: 10:1+
Prevention isn't expensive.
Replacement is.
For 20 years, our team operated in Iraq, Afghanistan, Syria, Tunisia, Niger, Ukraine.
We protected Presidents and Ambassadors in war zones.
We defeated terrorist organizations and their operations.
Now we apply that capability to maritime protection.
That's Aegis Shield.
Here's the question yacht owners aren't asking:
What's the ROI on a $50M asset that can't safely operate in 60% of its intended range?
When does your yacht stop being freedom and start being a very expensive prison?
The other losses:
• Ocean Queen ($70M) — attacked off Aruba, sunk, 5 crew killed
• Blue Star ($40M) — seized during kidnapping, still missing
• Helios ($30M) — hostage situation, vessel unrecovered
• Luna Bella ($25M) — fatal shooting, abandoned
$200-250M documented. Actual number likely 2-3x higher.
April 2024: Sea Explorer ($60M) makes routine radio contact in Venezuelan waters.
Then nothing.
No distress signal.
No debris.
No resolution.
Just... gone.
Suspected hijacked or sunk. Never recovered.
This isn't opportunistic piracy.
Sinaloa Cartel. CJNG. Gulf Cartel. Los Choneros.
Military-precision operations:
• 40+ knot interceptor boats
• Encrypted communications
• Port intelligence networks
• Attack time: <15 minutes
By the time you send a distress signal, they're on board.
$250M in superyachts. Vanished. 24 months.
6 luxury vessels seized by cartels in Caribbean waters.
Sea Explorer: $60M — gone
Ocean Queen: $70M — sunk, 5 dead
Blue Star: $40M — hijacked
And 20-30 more attacks go unreported every year.
Thread 🧵👇