FAQ

It crashes on launch

Start with the newest file in the log directory (paths are in Install and upgrade). Usual suspects:

• Old graphics driver: update it, or launch with --disable-gpu.
• Corrupt config: rename config.json and restart; Vibern rebuilds the defaults.
• Antivirus interference: allowlist the install directory.

It cannot find Claude Code

Vibern locates the CLI through PATH. If it works in your terminal but not in the app, the GUI process did not inherit your shell environment.

Fix it by setting an absolute path in Settings → Advanced → Claude Code path.

# Find the path first
which claude    # Linux
where claude    # Windows

Requests spin forever

Work through this order:

1. Check the status dot in the session header. Red means the connection never came up.
2. Try a different provider config. If that works, the original config is at fault.
3. Disable your proxy and retry.
4. Look for 401 or 429 in the logs: the first is a key problem, the second is rate limiting.

Large files hang

The editor loads big files in chunks, but two cases are still slow:

• One enormous line, such as minified JSON. Reformat it first.
• Files on a network share. Copy them locally.

You can tune the cutoff in Settings → Editor → Large file threshold; chunked mode kicks in above 50 MB by default.

Snapshots eat disk space

Snapshots live in .vibern/snapshots inside the project. To reclaim space:

• Use Settings → Time machine → Clean up to delete by age.
• Lower the retention count; the default keeps the last 50 changes.

Remote SSH will not connect

flowchart TD
    A[Connection fails] --> B{Does ssh work in a terminal}
    B -->|No| C[Fix your ssh config and keys first]
    B -->|Yes| D{Key or password}
    D -->|Key| E[Check the private key path and passphrase]
    D -->|Password| F[Confirm the server allows password auth]
    E --> G[Read the handshake error in the logs]
    F --> G

Jump hosts need an explicit ProxyJump. Vibern reads your ~/.ssh/config.

Remote control will not open

• Confirm the host firewall allows the configured port.
• Use the host IP on your LAN, not localhost.
• Both devices must be on the same network, or you need port forwarding.

Still broken

Open an issue on GitHub with a log excerpt, your OS version and repro steps.