Repository navigation
[Bug]: Raycast and VS Code extensions can't connect since v5.11.0 #967
Description
Describe the bug
When attempting to open massCode on either Raycast or VSCode, I get:
massCode app is not running or port is not correct.
I checked and the Port on both VSCode and Raycast is 4321,
Enable API integrations is checked
To reproduce
- Open and search for snippet
App Version and Architecture
Current version v6.0.0
System info
System:
OS: macOS 27.0.1
CPU: (8) arm64 Apple M3
Memory: 233.84 MB / 24.00 GB
Shell: 5.9 - /bin/zshValidations
- Follow our Code of Conduct
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion.
Activity
antonreshetov commentedon Oct 7, 2026
Thanks for the report! This isn't a problem with your port or settings. In v5.11.0 we tightened the security of the local API: most endpoints now require authorization. When we did that, we completely forgot about the external extensions. The Raycast and VS Code extensions don't send any token, so the app rejects their requests, and the extensions show the generic "app is not running or port is not correct" message.
The "Enable API integrations" option doesn't help yet either. For now the integration token is accepted only by the clipper and MCP endpoints, not by the endpoints the extensions use.
We'll fix this in the app and update both extensions so they work with the integration token, the same way the web clipper does. Until then, the Raycast and VS Code extensions won't work with v5.11.0 and later. Sorry for the inconvenience!
[-][Bug]:[/-][+][Bug]: Raycast and VS Code extensions can't connect since v5.11.0[/+]pulpfree commentedon Oct 7, 2026
Thanks for the update!