Troubleshooting

The verne command isn’t found

Verne installs its CLI at ~/.local/bin/verne on first launch, but that directory may not be on your PATH.

Add it to your shell profile (~/.zshrc, ~/.bashrc):

$ export PATH="$HOME/.local/bin:$PATH"

Then restart your shell or source the file. See Installation for more detail.

My agent isn’t detected / shows no status

Check that you’re running one of the agents Verne recognizes. The full list is on Supported agents. Any other command still runs fine in a Verne terminal; it just shows the raw foreground process without agent-specific status.

Also confirm the agent was launched inside a Verne terminal tab, not in an external terminal. Verne only tracks processes it owns.

An MCP agent shows “Needs approval”

Some agents require you to approve the MCP server connection before it connects. Either approve it inside the agent when prompted, or use Copy install commands in Settings › Agents to register the MCP server manually. See Hooks & MCP setup for the exact steps.

A daemon restart overlay appeared

The background daemon that owns your sessions restarted. Verne reconnects on its own and your workspaces and layout are preserved. You can dismiss the overlay once reconnection completes. Read more about how sessions persist in Persistent sessions.

Editor language features aren’t working

The TypeScript, JavaScript, and Vue language server can be toggled in Settings › Editor. If completions, diagnostics, or go-to-definition are missing, confirm the language server is enabled there. See Code editor for the available options.

Next steps