Logs

Read, filter, copy and export what Cliqer has been doing, with passwords, tokens, licence keys and stream keys removed before anything is saved.

The Logs window shows a running record of what Cliqer is doing: sign-in, the room, cameras and devices, Studio, outputs and your key, MIDI and OSC input. It is the first place to look when something does not behave, and the file to attach when you contact support.

Windows: the Logs window has the same levels, areas, search and redaction. Where it differs (how to open it, the toolbar, the time column and export), a Windows note says so.

Open the window

On macOS:

  • Help > Show Logs
  • Window > Logs
  • Settings > Advanced > Show Logs
  • Window > Show Control Monitor, which opens Logs already filtered to your control input (see below)

Windows: open it from the menu bar (Help > Show Logs, Window > Show Control Monitor; in Classic, under the Menu button), from the overflow menu of the command bar on the Room, Studio, Timer and Devices pages (Logs, and Show Control Monitor), from the Settings menu in the Studio top bar (Logs..., Show Control Monitor), or from Settings > Advanced (Open Logs, Show Control Monitor).

On macOS the window opens at 900 by 520 points. It has no keyboard shortcut of its own, because keys belong to External Control.

What is in the log

Cliqer writes one log. The app, the engine that runs rooms and Studio, and the libraries it uses all write to it, so you read one list in time order.

Secrets are removed before a line is stored, so the window, the file and every export are already clean.

Levels

Pick a Level to see that level and everything more severe.

LevelShows
ErrorsThings that failed.
WarningsErrors and things that look wrong.
InfoThe above and normal events. This is the default.
DebugThe above and detail for troubleshooting. Cliqer only keeps Debug lines while you ask for them.

Each line shows its level as a symbol and a word, never by colour alone.

Areas

Use Areas to look at one part of the app. The button reads All Areas, the area name, or " Areas". You can tick several. Ticking All Areas clears the selection.

AreaCovers
SessionSign-in, the room, presenters, reconnects
NetworkServer connections, proxies, network changes
RTCLive video and audio transport
DevicesCameras, audio devices, Bluetooth clickers, Stream Deck, USB
ControlClickers, Companion, Google Slides, presentation control and key and MIDI input
OutputsNDI, recording, streaming, MultiCorder, virtual displays
MediaMedia inputs, screen capture, the audio engine
StudioStudio and its compositor
LicencePlan, seats, sign-in credential, update feed
AppThe app itself: permissions, windows, and any library not listed above

The window

Toolbar

ControlWhat it does
LevelSee above. Tooltip: "Show this level and everything more severe".
AreasTooltip: "Which areas to show".
Pause / ResumePause stops new lines being added ("Stop adding new lines"); Resume reads the log again, so nothing is lost while paused.
Clear ViewEmpties the window. Tooltip: "Empty this view; the log file keeps every line".
CopyCopies the selected lines. Off until you select some. Command+C does the same.
ExportVisible Lines... saves what the window shows. Log File... saves a copy of the log file.
Reveal Log FileShows the log file in Finder.
Search LogsFilters the list by the message text or the area name, ignoring capitals.

Windows: the toolbar has Level and Areas (the button reads All areas or " areas"), Search logs, and the commands Copy, Export, Open Log Folder and Clear View. There is no Pause or Resume. Search also matches the level. Ctrl+A selects every line, Ctrl+C copies the selected lines and Escape clears the selection.

Table

Columns: Time, Level, Area, Message. The time is your local time with milliseconds. The message is one line; hover to read it in full. The table follows the newest line until you scroll up, and follows again when you scroll back to the bottom. You can select several lines.

Windows: the time column is headed Time (UTC) and shows UTC.

The bottom bar says " lines", or " of lines" when a search narrows the list, then ", selected". Paused shows while paused. On Windows it says " lines" and ", selected" only.

The window holds up to 10,000 lines. Older lines drop out of the window, but not out of the file.

Open and close

Cliqer only sends lines to the window while it is on screen. Closing or minimising it stops and empties the view; showing it again reads the log from the start and ends any Clear View.

Copy and export

On macOS, a copied or exported line looks like this:

2026-10-08 03:14:15.926  Info     Studio   message
  • Visible Lines... saves the lines you see, after your level, area and search filters, as a .log text file.
  • Log File... saves a copy of the current log file as it is on disk. It is off when there is no log file yet.
  • Both open a save panel with the name Cliqer-<date and time>.log.

Windows: Export saves the lines shown as a text file named cliqer-log-<date>.txt, and there is no Log File... choice. A line reads 2026-10-08 12:34:56.789Z WARN Rtc message (UTC, level in capitals), and a message of several lines continues on indented lines.

The log file is named cliqer.log. It rotates at 5 MB, and Cliqer keeps 5 files.

What is removed

Cliqer removes these before a line is stored:

RemovedWhat you see
Sign-in tokens, cookies and authorization headers[redacted]
Passwords and secrets in web addresses[redacted]
Values named token, secret, password, credential, key, signature, auth or one-time code[redacted]
The last part of an RTMP or RTMPS address, which is the stream key[redacted]
Your licence key****-****-****- and the last four characters

Control Monitor

Window > Show Control Monitor opens Logs with Areas set to Control and Level set to Debug. It lists each key press, MIDI message and OSC message Cliqer sees and what it did with it, or that no binding matched. Use it to find out why a control does nothing. The lines use developer wording, such as key names and action ids. On Windows, Show Control Monitor is in the places listed under Open the window.

Send logs to support

  1. Open Logs.
  2. If the problem is about one area, tick it; otherwise leave All Areas.
  3. Choose Export > Log File... and save it.
  4. Send the file to support.

Windows: choose Export and save the lines shown, or choose Open Log Folder and send cliqer.log from it.

External Control

Keys and MIDI for Studio.

Outputs

Stream keys are hidden in the logs.