The new version (5.1.18) of CCC deliberately excludes 1Password at the recommendation of Agilebits, 1Password developer.
The reason is that the 1P Updater detects extra copies of 1P on attached clones.
This issue has existed for years and never caused me a problem.
I feel excluding apps at developers request is a slippery slope and it is no longer possible to regard a CCC clone as a clone.
Why don't Agilebits simply change the updater to force the unmounting of detected clones before proceeding.
Exclusion by CCC is the wrong way of dealing with this issue.
The reason is that the 1P Updater detects extra copies of 1P on attached clones.
This issue has existed for years and never caused me a problem.
I feel excluding apps at developers request is a slippery slope and it is no longer possible to regard a CCC clone as a clone.
Why don't Agilebits simply change the updater to force the unmounting of detected clones before proceeding.
Exclusion by CCC is the wrong way of dealing with this issue.