Skip to main content
Join waitlist

Troubleshooting

Solutions for common issues. If you don't find your answer here, reach out to us through the contact form.

Desktop Connector Shows "Not Paired"

If the MobileVibe tray icon still shows "Not Paired" after you've completed setup, try these steps:

  1. Right-click the tray icon and select Restart
  2. Wait a few seconds, then right-click again and select Sign In / Pair
  3. Sign in and select your workspace

If you previously paired this PC but it lost its pairing (for example, after a reinstall), you may need to remove the old workspace from the dashboard and create a new one.

Can't Reach Your Workspace

If your workspace can't be reached, check these common causes:

  • PC is off or asleep — Wake or turn on your computer.
  • Desktop Connector isn't running — Look for the MobileVibe icon in your system tray. If it's not there, launch MobileVibe from the Start Menu.
  • No internet connection — Make sure your PC is connected to the internet.
Tip: You can check if the Desktop Connector is running by hovering over the MobileVibe tray icon. It should show your workspace name.

Project Won't Come Online After Launch

If a project doesn't come online after you tap Launch, one of these might be the issue:

  • VS Code failed to open — Make sure VS Code is installed and accessible from the command line. Try launching it manually to confirm it works.
  • Folder doesn't exist — Double-check that the project path you entered actually exists on your PC.
  • Not launched through MobileVibe — VS Code must be opened through MobileVibe (via the Launch button) for remote access to work. Opening VS Code directly from the Start Menu or taskbar won't connect it.

If the project launched before but stopped working, try tapping Restart on the project card to close and relaunch VS Code.

VS Code Opens But Your Agent Doesn't Appear

If VS Code opens on your desktop but the agent interface doesn't appear in MobileVibe:

  • Install the extension — Make sure your agent's extension (Claude Code or Codex) is installed in VS Code. Open VS Code, go to Extensions, and search for it.
  • Wait a moment — Extensions can take a few seconds to load after VS Code starts. Give it 10-15 seconds and refresh.
  • Restart the project — Tap Restart on the project card to close and relaunch VS Code.
Note: If you're using Codex instead of Claude Code, make sure you selected the right agent type when creating the project. You can remove and re-add the project with the correct agent if needed.

Restarting the Desktop Connector

If things aren't working and you've tried the steps above, restarting the Desktop Connector often fixes the issue:

  1. Right-click the MobileVibe tray icon
  2. Select Restart
  3. Wait about 10 seconds for it to come back online

This restarts the background service without losing your workspace or project configuration. Your projects will show as OFFLINE briefly and you'll need to re-launch them.

Notifications Not Working

Push notifications require installing MobileVibe as an app. If you're not receiving them:

  • Chrome (desktop or Android) — Install MobileVibe as a PWA. Open app.mobilevibe.com in Chrome, click the install icon in the address bar, and make sure notifications are allowed.
  • iOS — Use the MobileVibe app from the App Store. Push notifications work automatically once you're signed in.
  • Check notification permissions — Make sure notifications are allowed for MobileVibe in your device or browser settings.
  • Check Do Not Disturb — Your device's Do Not Disturb or Focus mode may be blocking notifications.

Known Limitations

MobileVibe is in early alpha. Here are the current limitations we're working on:

  • Windows only — The Desktop Connector currently only runs on Windows. macOS and Linux support is planned.
  • Apple and Google sign-in — Additional sign-in methods are planned for a future release.
  • Claude Code and Codex — These are the supported AI agents. Support for additional tools (Cursor, Windsurf, etc.) is on the roadmap.

MobileVibe is actively improving. If you run into something not listed here, please let us know through the contact form — your feedback helps us prioritize fixes.

More Help