Short answer
A Smart Collection is a saved set of rules. It does not move or duplicate your clipboard items.
Choose whether it should search History, Favorites, or both. Add rules for text, source, type, domain, date, tags, size, or file-snapshot state, then decide whether every rule or any one rule must match.
When to use this method
Use a Smart Collection when you repeatedly ask the same question, such as "recent links from my browser" or "Favorite images tagged project." Use a normal Favorite category when you want to choose and arrange lasting items manually. Use a pin when a single history item should survive routine cleanup.
How we checked this guideRule behavior, live membership and the difference from a stored copy.
- What we reviewed
- Reviewed Smart Collection rules for source, domain, type, date, size, tags, pin and snapshot state, including live result updates, against the current Osenpa Clipboard Manager source.
- What we confirmed
- Smart Collections are saved queries over local history. Their membership changes with clip properties and does not create a separate protected copy.
- Important limit
- A collection for tag:client can become empty when the tag is removed; the clip still exists in history. Use pinning or retention choices separately when preservation matters.
Understand what a collection can and cannot do
It remembers a question
The collection stores its name, scope and matching rules. When you open it, the app asks the current History and Favorites for items that satisfy those rules.
It does not make a protected copy
A regular history item can disappear from a collection because its tag changed or because cleanup deleted the underlying item. Collection membership alone does not pin, favorite, snapshot or encrypt anything.
Deleting the collection is safe for its results
Editing or deleting a Smart Collection changes only the saved query. It does not delete the History or Favorite items that appeared in the results.
Turn a recurring query into a view
Define one retrieval purpose
State the question in plain language before opening the rule editor. "Links from example.com" is clear. "Useful things" is too vague to test. Give the collection a name that still makes sense a month later.
Choose the collection scope
Select History for captured items, Favorites for lasting copies, or Both. Remember that a Favorite is its own saved snapshot, so History and Favorites can contain related but separate records.
Add the narrowest useful rules
Start with the strongest fact you know: a text term or exact phrase, source application, content type, date, tag, link domain, item size, pin or Favorite state, or whether a copied file has a snapshot. You can also use the advanced search query. Add a second rule only when the first produces a known false match.
Save and inspect membership
Choose All when every rule must be true. Choose Any when one matching rule is enough. Save, read the result count, and open at least one expected item and one surprising item. Item details shows the metadata needed to explain why it matched.
Change one test item
Use harmless test data. Add or remove a tag, change a pin, or create a link with the chosen domain. Confirm that the result enters or leaves the view without being duplicated or deleted.
Build rules that answer one clear question
Recent links from one source
Scope the collection to History, require the Link type, select a source application and add a date condition. Add a domain only if links from that source are still too broad.
Reusable project material
Scope it to Favorites and require the project tag. Add a content type only if the collection is meant to contain, for example, images rather than every tagged Favorite.
Copied files with safe local recovery
Require the File type and snapshot state. This finds records whose bytes were copied into local snapshot storage. It does not prove the snapshot is current, so inspect the file card before restoring or sharing it.
Collection assumptions
- Treating a Smart Collection as a copied archive
- Combining All rules until no item can match
- Using Any when every condition was intended to be required
- Using a broad domain or source label without inspection
- Assuming rule membership protects an item from cleanup
Checkpoint: test membership
- Explain the rule in one sentence.
- Verify one expected member and one excluded clip.
- Change a test property and observe membership.
- Confirm the original history item remains the same record.
- Confirm All rules or Any rule reflects the intended logic.
- Delete a disposable test collection and confirm its matching items remain in History or Favorites.
If a Smart Collection is empty
Open the rules and read them as one sentence. Temporarily remove the last rule you added, check whether All or Any is selected, and make sure the collection searches the right part of the app.
Inspect a candidate item's source, type, date, tags, domain, size, and snapshot state. A collection cannot restore an item that retention already removed. Recovery requires an existing backup or Favorite.
Osenpa Clipboard Manager
Save dynamic views over History and Favorites without duplicating or deleting the items that match.