The Log Viewer console is a live tail of everything happening inside Weave —
internal bridge calls, LLM API requests, backend console output, and optional external server
traffic. It keeps a rolling window of the last 1,000 entries across all log
types, behaving like a tail -f that spans the entire app.
Log types
Bridge
HTTP calls from the bundled Svelte frontend to the bundled Go backend. These are the internal RPC calls the UI makes to drive app behaviour — creating chats, fetching settings, streaming responses, and so on.
Many bridge calls happen on a polling schedule. The Hide Noise button filters these out so you can focus on traffic triggered by your own actions.
Weave is a single binary built with Wails — the bundled Svelte frontend and Go backend are both compiled into one executable. There is no separate server process; everything runs in-process.
LLM
Outbound calls to vendor LLM APIs. Each entry shows the HTTP status code, a summary of the inputs sent, and token counts — input tokens, output tokens, and cached read/write tokens where the provider reports them. Response bodies are omitted from the log due to their size.
Console
The stdout and stderr output of the bundled Go backend. Useful for seeing internal warnings, errors, and diagnostic messages emitted by the application itself.
EXT API
Request logs from Weave's built-in API server. Disabled by default — entries appear here only when the API server is enabled in settings.
EXT MCP
Traffic logs from Weave's built-in MCP server. Disabled by default — entries appear here only when the MCP server is enabled in settings.
Filtering
Beyond the Hide Noise button, you can right-click any log entry to exclude that entry type from the tailing window entirely — useful for permanently silencing a noisy call pattern without hiding all bridge traffic.
