> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/app-builder/logs.md).

# Logs

The Logs panel is a sliding panel at the bottom of the App builder. It shows real-time output from your app — everything your backend prints, every API call, every error — so you can see what is happening as it happens.

## Opening the panel

Click the **Show logs** button (terminal icon) in the lower area of the workspace. The panel slides up from the bottom with a dark background and monospace text. Click the toggle in the panel header to close it again.

## What you see

Log entries appear newest first. Each entry shows:

* **Source** — `frontend` or `backend`
* **Severity** — the log level (info, warning, error)
* **Message** — the log text

## Controls

<table><thead><tr><th width="283.85272216796875">Control</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Filter field</strong></td><td>Type to narrow logs to lines containing that text</td></tr><tr><td><strong>Send logs to agent</strong> (wrench icon)</td><td>Copies the visible log entries into the Riff agent chat — the agent reads them and proposes a fix</td></tr><tr><td><strong>Clear</strong></td><td>Wipes the current log list to start a clean trace</td></tr><tr><td><strong>Hide toggle</strong></td><td>Closes the panel</td></tr></tbody></table>

## When to use it

* An API call is failing — check the backend logs to see the error before asking the Riff agent to fix it
* A form submission is not working — check frontend logs for browser errors
* Something looks wrong in the data — trace the backend calls that wrote it
* **Send logs to agent** is the fastest path to diagnosis: one click gives the Riff agent the exact error context it needs


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.riff.ai/reference/app-builder/logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.