Troubleshooting

Most problems fall into one of the buckets below. If yours doesn't, file an issue on the public GitHub tracker or email support@vibeless.pro — start the subject with [urgent] if it's blocking your work.

My agent says Vibeless is unavailable

Your editor's MCP connection needs the Vibeless desktop app running.

1. Open the Vibeless app. The connection recovers automatically on the next tool call — no editor restart needed.
2. If the app is running and the agent still can't connect, restart the Vibeless app. On every start it re-checks the MCP configs of all installed agents and silently repairs a changed port or token.
3. Still stuck? Start a fresh agent session so your editor re-reads its MCP config.

Vibeless tools don't appear in my editor at all

• Confirm the install: Project Settings → Connected Agents should show your agent as installed. If not, click Install.
• Restart your editor (or open a new session) after any install — editors read MCP config at session start.
• If you moved or reinstalled the Vibeless app, click Reinstall in Connected Agents so the configs are rewritten in one pass.

"Project token rejected" or authorization errors

The token in your agent's config no longer matches the project. The usual cause is a token rotation.

• Open Project Settings → Connected Agents and click Reinstall for the affected agent.
• After any Rotate token, every previously installed agent needs the one-click Reinstall all the rotation dialog offers — and live agent sessions must reconnect.

AI features stopped working

The MCP tools your agent uses are local and never consume credits — but the AI features in the app (VibeCoder, architecture generation, imports) run on your plan's monthly credit budget.

• Out of credits: AI features pause until your next billing cycle or an upgrade. Your budget and usage are shown in the app; plan sizes are on the pricing page.
• Payment past due: the app shows a banner with a link to fix the payment.
• Offline: the AI features need an internet connection; everything else works offline.

A project is locked

If you moved to a smaller plan, projects over the new limit are locked — never deleted. Choose which projects stay active in the app; locked projects unlock instantly when you upgrade again or free a slot.

Installer concerns

Every installer is code-signed — Windows through Azure Trusted Signing, macOS signed and notarized by Apple. If Windows SmartScreen or macOS Gatekeeper flags a download, verify you got it from vibeless.pro/download and check the publisher on the warning dialog before proceeding.

Manual (Generic MCP) setups

If you configured an editor by hand and it can't find Vibeless, the bridge is failing to read ~/.vibeless/manifest.json — most often in cross-filesystem setups (WSL, sandboxed installs). See the manual-setup section of MCP & Hooks for the VIBELESS_MANIFEST_PATH override.

Where the logs are

The app log lives at ~/.vibeless/logs/app.log (older rotations are kept as app.log.1, app.log.2, …). Attaching the tail of this file to a support email speeds things up considerably.