Skip to main content
Server logs show what’s happening behind the scenes on your app’s backend. When something isn’t working right, logs tell you exactly what went wrong. They show error messages, warnings, and the step-by-step execution of your code on the server.

​
What server logs show

Server logs capture everything that happens on your app’s backend:
  • Server startup messages
  • Activity from your database
  • Errors and warnings from the backend
  • Package installation output
  • Backend operations as they happen
This is different from what happens in the browser. Server logs focus on the backend—the part of your app that handles data, processes requests, and manages the database.

​
When server logs help

Server logs are useful when: The page is blank or stuck loading
Server logs show if the backend crashed or failed to start. Data isn’t appearing
Server logs reveal database errors or issues fetching information. Forms aren’t submitting
Server logs show where the request failed on the backend. The agent is debugging for you
When the agent investigates an issue, it checks server logs to understand what’s happening behind the scenes. Logs give the agent context to find and fix problems faster.

​
How to enable server logs

By default, server logs are hidden to keep the interface simple. Turn them on when you need to debug.
  1. Click the Settings icon in the sidebar
  2. Go to the Appearance tab
  3. Toggle “Enable Logs” on
Once enabled, a panel appears below your app preview with two tabs: Server Logs and Browser Logs.

​
Using the logs panel

Expand or collapse the panel
Click the chevron button on the left side of the panel to show or hide logs. Switch between log types
Click the “Server Logs” tab to see backend output, or “Browser Logs” to see frontend output. Read the logs
Logs appear in chronological order with timestamps. The panel scrolls automatically as new logs arrive. Scroll up to pause auto-scroll and read older logs.

​
Understanding log messages

Server logs use colors to indicate the type of message:
ColorWhat it means
Gray or whiteNormal output—everything is working
YellowWarning—something might be wrong
RedError—something failed
BlueInformation message
Most logs show technical details about what’s running. You don’t need to understand every line. Look for red error messages or yellow warnings when something isn’t working.

​
What the agent sees

The agent doesn’t automatically see your logs. It checks them when debugging using its own tools. When something isn’t working, the agent retrieves server logs to understand what went wrong. Logs are part of the agent’s standard debugging process. Enabling logs in your settings doesn’t change whether the agent can check them—it only controls whether you see the logs panel in the interface.