Troubleshooting

When something doesn't work — log locations, reset paths, where to file a bug.

This page collects the things that go wrong most often, with the recovery steps that actually fix them.

Logs

If you launched Vibehaus by double-clicking it from /Applications, the app’s messages flow to Console.app. You can read them with:

log stream --predicate 'subsystem CONTAINS "vibehaus"' --info

If you launched Vibehaus through the bundled launchd installer (install.sh), stdout and stderr are also tee’d to:

~/Library/Logs/Vibehaus.log
~/Library/Logs/Vibehaus-error.log

“My Vault is empty after I signed in on a new Mac”

This is almost always iCloud Keychain hasn’t delivered the master key yet. See Cloud Sync → First sign-in on a new device for the full mechanism.

Recovery:

  1. Wait 30 seconds with the app open. iCloud Keychain usually catches up by then.
  2. If the app shows the timeout overlay, tap Sign out and sign back in. That nudges iCloud Keychain into syncing.
  3. If you still see “X items couldn’t be decrypted”, your master key on this Mac doesn’t match the one used to encrypt the rows. The most common cause is signing in with a different Apple ID than the one that originally created the Vault.

”My dev server doesn’t die when I press Stop in a Flow”

The Stop / Reset path tries to walk every daemon’s child process tree and terminate each one, which fixes the common case where npm run dev reparents the actual node / next-server to launchd. If a process is really stuck, find it by port and kill it directly:

lsof -i :3000
kill -9 <pid>

“Sign in with Apple opens a browser instead of a native dialog”

This is intentional. Vibehaus completes the Apple sign-in in your default browser and then deep-links you back to the app. You should be back inside Vibehaus within a second of finishing the Apple flow.

Resetting the app

Three escalating reset paths, from least to most destructive:

  1. Sign out (Settings → Account → Sign out). Clears auth tokens and the active session. Your Vault entries, master key, projects, and notes are kept so the next sign-in feels continuous.

  2. Sign in as a different user on the same Mac. Triggers a heavier wipe — the previous user’s vault values, master key, and local data are cleared from this Mac. The previous user’s data is not cleared from the server (it stays decryptable when they sign back in).

  3. Manual nuke (when nothing else works). Quit Vibehaus and run:

    defaults delete com.vibehaus.app
rm -rf ~/Library/Application\ Support/Vibehaus
rm -rf ~/Library/Containers/com.vibehaus.app
security delete-generic-password -s com.vibehaus.app

    Then relaunch. You’ll go through onboarding from scratch.

A one-click “Wipe all local data” button in Settings → Advanced is on the roadmap.

Reporting a bug

The fastest path is the in-app feedback link (Settings → About → Feedback), which opens vibehaus.dev/feedback in your browser.

When filing a bug, include:

  • App version (Settings → About → Version, or visible at the bottom of the sidebar).
  • macOS version (Apple menu → About This Mac).
  • What you did + what you expected + what happened instead.
  • The relevant tail of ~/Library/Logs/Vibehaus-error.log if you launched via the launchd installer.

For wider support discussion, write to hello@vibehaus.dev.

  • Cloud Sync — diagnosing decryption errors and sync timeouts.
  • Vault — what’s actually stored where.
  • Getting Started — re-do onboarding after a reset.