As it is, "cm ls" and the Items view will not show cloaked items after an initial update/switch in a new workspace, since metadata for the cloaked items has not been fetched.

If you perform a "cm update --cloaked" and then delete the cloaked items, they will still show up in "cm ls" and in the Items view (as "Cloaked / Not on disk"), since the metadata has then been fetched into the workspace.

Besides consistency and always having a simple way to see that there are cloaked items, this actually makes a practical difference when having multiple cloaked items in the same directory and you want to update just one of them. (If metadata is fetched you can perform a "cm update --cloaked <item>" to update just one item at a time. However, if metadata is not yet available you can only do the update on the parent folder, which would update all the cloaked items at the same time.)

I suggest always fetching metadata for cloaked items, to improve consistency. For cloaked folders, it would be sufficient to fetch metadata for the folder itself, not for the sub-tree below it (for performance reasons).