> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daydream.live/llms.txt
> Use this file to discover all available pages before exploring further.
# Reporting Issues
> Use the built-in log panel and bug reporter to help us fix issues faster
# Reporting issues
Scope includes built-in tools that make it easy to capture logs, diagnose problems, and report bugs, whether you're running locally or on [Remote Inference](/scope/guides/remote-inference). This guide covers everything you need to submit a clear, actionable bug report.
***
## The log panel
Scope has a real-time log panel at the bottom of the interface that displays what's happening under the hood. This is your first stop when something goes wrong.
### Opening the log panel
Click the **terminal icon** in the bottom status bar to toggle the log panel open or closed. When the panel is closed and new logs arrive, a **badge** shows the number of unread messages.
### Filtering logs
The log panel has three filter tabs:
| Filter | What it shows |
| ---------- | -------------------------------------------------------------------------------- |
| **All** | Every log message, including info, warnings, errors, and cloud messages |
| **Errors** | Only errors and warnings, filtering out routine info messages |
| **Cloud** | Only logs from the remote inference server (visible when using Remote Inference) |
When troubleshooting, start with the **Errors** filter to quickly spot problems. Switch to **All** if you need more context around when the error occurred.
### Log colors
Logs are color-coded by severity:
* **Red** - errors that need attention
* **Amber** - warnings that may indicate a problem
* **Blue** - informational messages (normal operation)
* **Gray** - debug-level detail
Cloud logs are distinguished with a blue left border and a **CLOUD** badge.
### Copy and clear
Use the **Copy** button to copy all visible logs to your clipboard, which is useful for pasting into a bug report. The **Clear** button resets the panel.
***
## Reporting a bug
Scope has a built-in bug reporter that bundles your logs and opens a GitHub issue template in one flow.
Click the **gear icon** (top-right) and navigate to the **General** tab.
Click the **Report Bug** button. A dialog will appear with two steps.
Click **Copy Logs** in the dialog. This fetches your current session's log file and copies it to your clipboard. You'll paste these into the GitHub issue.
Click **Create Bug Report**. This opens a pre-filled issue template on the [Scope GitHub repository](https://github.com/daydreamlive/scope/issues). Paste your logs into the designated section and fill in the details.
The bug reporter works for both local and Remote Inference sessions. When running remotely, cloud logs are included automatically.
***
## Log files on disk
Scope saves logs to disk so you can access them even after closing the app.
* **Default location:** `~/.daydream-scope/logs`
* **File format:** `scope-logs-YYYY-MM-DD-HH-MM-SS.log`
* **Retention:** logs older than 1 day are cleaned up automatically
You can view or change the logs directory in **Settings** > **General** > **Logs Directory**.
If Scope crashes before you can use the built-in bug reporter, attach the most recent log file from this directory to your GitHub issue.
***
## Advanced: verbose logging
For harder-to-reproduce issues, you can enable more detailed logging:
| Method | How to use |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Environment variable** | Set `VERBOSE_LOGGING=1` before launching Scope |
| **Quiet specific loggers** | Set `SCOPE_LOG_QUIET_LOGGERS=scope.server.frame_processor,scope.core.pipelines.longlive` to suppress noisy loggers while keeping everything else verbose |
Verbose logging produces significantly more output. Only enable it when actively debugging as it can affect performance with high log volumes.
***
## Writing a good bug report
The more detail you provide, the faster we can fix the issue. A great bug report includes:
1. **What you expected** - describe the behavior you were trying to achieve
2. **What happened instead** - describe the actual behavior, including any error messages
3. **Steps to reproduce** - list the exact steps to trigger the problem
4. **Your environment** - OS, GPU model, Scope version, local or Remote Inference
5. **Logs** - paste the logs from the built-in bug reporter or attach the log file
Before pasting logs publicly, check that they don't contain any sensitive information like file paths or tokens you'd prefer to keep private.
***
## Where to get help
Report bugs, request features, and track known issues
Ask questions and get help from the community and team