Skip to content

Server logs

Server logs are a live, decrypted feed of what your app is doing on the edge: Programmable Agent runs and database writes, streamed into the developer portal as they happen. There’s nothing to install and no SDK call — it’s a portal feature you read with your developer session.

In the developer portal, open an app and click the developer tools button (the wrench, bottom-right on every app page). The Server logs panel connects automatically and starts streaming.

Use the Environment toggle (Live / Test) to switch between the activity of your production and test deployments — they’re separate streams, just like your per-environment keys. It defaults to Live; switch to Test when your app is running on a test key.

Each entry is a structured event with a level (info, success, warn, error), a source, a message, and an optional detail line:

SourceExamples
agentan agent reply, with its model, the tools it called and tokens spent
dba row inserted, updated, or deleted

The panel keeps the most recent activity in view and highlights errors, so it’s the fastest way to confirm an agent actually replied. The platform does not yet write entries for serverless function runs or request errors, so a function won’t appear here; return the details you need from the function itself.

The log stream is a ring buffer: it keeps the most recent 1,000 events per environment and trims the oldest automatically, so it stays bounded and clears itself over time. It’s built for live debugging and recent history, not long-term archival — if you need durable records, write them to your app database.