Inspecting requests, tool results and connection errors.
Open the panel using the terminal icon in the header. It shows application events and information about model and tool requests.
This is not a full capture of browser traffic. Loading, CORS or network errors may also require the browser developer tools.
A server that has already started answering can only report a failure inside the stream itself (for example, an overloaded model or an upstream provider that does not respond). ZeroChat shows it in the chat as a server error and records it as an error in the log. If the server cuts the answer at the output token limit, the received text is kept with an incomplete-answer notice below it, and the log records a warning.
The panel toolbar lets you copy logs and clear the console. The log automatically follows new entries; scrolling up pauses it, and it resumes when you return to the bottom, switch tabs or open the panel.
Logs may contain messages, documents, arguments and tool responses. Review and remove private information before sharing; filtering credentials does not anonymize all content.
Enable Debug messages to inspect the prepared JSON before it is sent to the provider. You can edit and send it, send it while disabling the interceptor, or cancel with X.
Use it to check how messages, tools and parameters are packaged. An edit may invalidate the request or change what the model receives. Cancelling prevents that pending request but does not undo earlier requests or actions.
Raw displays request, response and streaming information recorded by ZeroChat. Entries are limited to contain panel size, so it should not be treated as a complete audit archive.
When reporting a failure, record the provider, model, action and error, and share only the necessary log excerpt.