In Azure DevOps/TFS web ui, click on your user picture in top right -> Security -> Personal access tokens -> New Token.

• In the organization dropdown, select "All accessible organizations"
• Either provide a "full access" scope, or more granular access that should include:
  • Build - Read and execute
  • Code - Read, Status (for getting pull requests)
  • Graph - Read
  • Identity - Read
  • Project and Team - Read
  • Release - Read
  • Test management - Read
  • User Profile - Read
  • Work Items - Read and Write
• You can set a long expiration time to avoid repeating this process frequently (e.g. 1 year)

In

To troubleshoot complex issues, our support team might need extended application logs.

Here is how you can collect them:

1. Go to edit menu/settings/advanced and check "Enable extended logging". This will turn on the logging of requests and responses from the server. Sensitive data will be masked.
2. Repeat the action that you had trouble with (e.g. connecting to a new server).
3. Put the log folder into an archive and attach this archive to a private support ticket. Location of the log folder:
   • Windows: %AppData%\CatLight\logs
   • MacOS: ~/Library/Application Support/Catlight/logs
   • Linux: ~/.config/Catlight/Logs

See also:  information about CatLight log files.

Windows 11 introduced "Focus assist" feature that can hide notifications from apps.

If you don't get any toast notifications from CatLight, try disabling it by searching for "Focus assist" in the Windows search menu, and then turning it off.

If you have "Priority only" option selected, you can click on "Customize priority list", and add CatLight app to it.

Some users experience authorization/authentication problems when they try to connect to Azure DevOps from CatLight. They can get an error message "Unauthorized" or 302 HTTP code.

This usually happens when the user has multiple Microsoft accounts(e.g. personal and work accounts), and the wrong account gets used during connection.

CatLight uses the default web browser to authenticate to Azure DevOps. This browser can have a different Microsoft account authenticated in it. For example, you use Chrome in day-to-day work and sign in using a work account there. But, the default browser is Internet Explorer or Safari, and it might have your

If you experience problems with starting the application, you can reset it by deleting configuration files. This will remove all your CatLight settings and preferences, and will revert the app to the factory state. Before deleting the configuration files, exit the app.

Location of configuration files on different platforms

Windows:

Mac OS:

Linux: 

If you have a problem with the app, you can inspect the application logs. They will often provide a detailed description of the problem and can also point to the specific project or build that is causing trouble.

Logs are written in two groups of files: 

• Log.txt – this is the log file of the background process that contains most of the app logic. It is usually the most useful, so check it first.
• TrayLog.txt – this is a log file of the UI process. If the application does not start, this log can contain details about the problem.
• NetworkLog.txt - trace of HTTP

If your build server is using a self-signed certificate, CatLight may not be able to connect and will show a message like "SSL connect error". This happens because the SSL certificate of your server is not trusted by your operating system. 

Add this certificate as trusted to resolve the problem, and try connecting again.

Instructions for Windows: https://blogs.technet.microsoft.com/sbs/2008/05/08/installing-a-self-signed-certificate-as-a-trusted-root-ca-in-windows-vista/ 

For OS X: http://www.robpeck.com/2010/10/google-chrome-mac-os-x-and-self-signed-ssl-certificates 

For Linux: http://askubuntu.com/questions/530056/install-root-certificate-on-ubuntu-14-04-64-bit