Logs and diagnostics

Logs describe Core, plugin, connection and automation activity. Use Runs for a step-by-step captured execution and Logs for surrounding lifecycle messages.

Investigate

Filter by relevant source, severity and time. Match a connection attempt or run to the observed problem. Core Settings → Diagnostics can open the current Core log location and copy a safe summary.

The Editor's workspace status can report a command error separately from runtime logs. Preserve the safe error code and whether the command result was confirmed or unknown.

Share carefully

Review logs, event payloads and attachments before reporting a problem. Remove credentials, private messages, prompts and unrelated data. Automatic secret masking does not make every retained viewer message suitable for sharing.

See Crash reports.