Raycast Clipboard History: Retention, Snippets, and AI Handoffs

You copy a useful public documentation excerpt on your Mac. A moment later, another copy replaces it. Raycast clipboard history gives you a way back to that earlier text, but retrieving it doesn't decide where it belongs next. Perhaps it needs a source-linked research note. Perhaps a response you've refined deserves a Snippet. Sending copied text to AI needs its own review.

The best clipboard setup is rarely the one that remembers the most. Start with what you need to recover, then decide what deserves to stay.

This Mac guide draws on Raycast's documentation. The examples are illustrative and unexecuted. No personal clipboard was inspected, and no settings were changed. Exports and AI requests were not tested either. Treat the workflows as guidance to review against your own setup.

Choose what Raycast records and how long it stays

Start with the copies you actually need back

In Settings > Clipboard History > Keep history for, the current manual lists 1 Day, 1 Week, 1 Month, and 3 Months, plus Pro options of 6 Months, 1 Year, and Unlimited. Longer Pro retention is not enabled automatically; you must select it.

Start with the shortest window that covers your recovery needs. Unlimited is an option, not a recommendation. If you only need today's overwritten excerpts, retaining older copies adds little to that job. A longer window keeps more material available, but it still doesn't give you a maintained source record.

Check which apps can add to history

Open Disabled Applications before relying on history. The Clipboard History settings documentation describes source-app exclusions and lists Passwords and Keychain Access as common included examples. Review the list against the apps you copy from. Your organization's handling rules may call for further exclusions.

The boundary is the source application. Excluding a password manager does not establish that Raycast will detect a password copied from a browser or terminal that remains eligible for capture. For private customer material, settle whether routine capture is permitted before choosing a retention window.

Apple Universal Clipboard is a separate mechanism. Raycast documents saving external Apple-device items after you paste them by default in its Universal Clipboard settings. Save Universal Clipboard Items Immediately is an optional, default-off local setting that does not sync between Macs. Do not confuse it with Raycast Cloud Sync or infer Windows or iOS feature parity from this Mac guide.

Recover an excerpt and paste it into the right destination

Recover the passage, then keep its source

In this hypothetical example, a second harmless copy has replaced your public excerpt. Open Raycast and find Clipboard History through Root Search. Search for wording you remember from the excerpt. Select the intended entry; Command-K opens its Action Panel. This sequence follows the documented actions and has not been executed for this guide.

Keep the original URL alongside research notes when attribution matters. Finding the words again doesn't recover all their context. Optijara's Zotero guide to source-linked notes and citations explains how to connect a passage to the consulted document and the claim it supports.

Check app focus and choose plain text deliberately

Before pasting, look at the receiving application and input field. Raycast's Primary Action setting distinguishes Paste to Active App, which inserts into the focused app, from Copy to Clipboard, which restores the selected item to the clipboard. Changing that setting changes what the primary action does. Don't press Return from habit.

The same manual documents Paste as Plain Text and Prefer pasting as plain text. Use these when you want the wording without its original rich formatting. The preference is not proof that the receiving app honored it; the manual also lists plain-text paste failures in troubleshooting. Inspect the inserted result before moving on.

Plain text can still contain confidential wording. It also says nothing about whether a quotation is accurate or a terminal command is safe. If a paste lands in the wrong field or looks incomplete, stop. Work out which entry and action you selected, then correct the destination before trying again.

Promote reusable text into maintained Raycast Snippets

Save a non-sensitive response or prompt scaffold

A useful response deserves editing before it becomes reusable text. Use Save as Snippet from an appropriate history entry, or find Create Snippet through Root Search. Give it a name you'll recognize later. The Snippets manual covers creation and management, including optional keywords.

An illustrative scaffold named Public excerpt review could contain:

> Summarize the supplied public excerpt. Separate stated facts from uncertainties. Preserve source URLs.

This wording is an unexecuted example, not a validated prompt. It contains no private records or credentials and doesn't insert the clipboard dynamically. Saving a prompt doesn't prove it works for your task or model.

Choose a distinctive keyword and review expansion settings

Consider ;;publicbrief as an illustrative keyword. Check it against existing keywords and your normal typing before adopting it. Unusual wording can still collide. Raycast supports immediate expansion and delimiter-based modes, with a separate option for expansion within words. Review these in Snippets settings.

Automatic expansion is optional; you can keep manual search and insertion. Snippets' Disabled Applications controls expansion. Clipboard History has its own capture exclusions, so check both lists. Where Teams sharing is available, decide whether the text belongs to you or the organization before sharing it. Update saved wording when its assumptions change. Delete versions you no longer want people using.

The Keep, Reuse, Review playbook for everyday copied text

Use a destination decision table

Keep, Reuse, Review is this guide's original editorial playbook. It is not a Raycast feature or a tested method. Its purpose is to help you choose a destination for copied material, including deciding when clipboard history has done its job.

The diagram separates the decision about keeping material from any optional AI step. It describes a recommended human process, not an automation.

Apply it to a harmless public excerpt

For the illustrative excerpt, check the intended notes field before pasting as plain text. The reusable scaffold belongs in a separately maintained Snippet. An AI handoff remains optional and requires permission for the selected material. Recovering text should not automatically send it elsewhere.

A copied meeting action needs a different check: did anyone actually agree to it? The Granola guide to confirming actions before sharing covers that review before a summary becomes assigned work.

Before adopting the workflow, work through these checks.

• Inspect retention against actual recovery needs.
• Review source-app capture exclusions.
• Review Snippet expansion exclusions separately.
• Inspect the intended entry before acting.
• Confirm destination, primary action, and formatting.
• Review sync and export boundaries before moving data.
• Sanitize selected text before any permitted AI handoff.

The JSON records the editorial decisions in machine-readable form. It is a summary only; it cannot configure Raycast and does not document an executed test.

{
  "playbook": "keep-reuse-review",
  "temporary": "retention-matched-to-recovery",
  "reusable": "reviewed-non-sensitive-snippets",
  "handoff": "destination-permission-and-processing-reviewed",
  "evidence": "documentation-based-unexecuted"
}

If you review the workflow yourself, record what happens. A successful retrieval alone doesn't establish a productivity gain. The following measurement plan is proposed; no results have been collected.

Use a harmless public item for any permitted check of uncertain exclusions or keywords. Inspect what enters history and where expansion occurs before introducing working material. Keep credentials and private records out of that check. It has not been performed for this guide.

Separate local history, Cloud Sync, exports, and AI processing

Not Cloud Synced does not mean never exported

Local history, Cloud Sync, exports, and AI processing need separate answers. A restriction in one feature does not establish the same restriction elsewhere.

The Cloud Sync manual explicitly excludes Clipboard History from that feature. Snippets and AI Chat History are separate configurable categories requiring the applicable signed-in Pro setup. Turning off a category pauses its sync. Turning Cloud Sync off does not delete existing cloud or other-device data.

Exports cross a different boundary. The Import & Export manual lists Clipboard History among Export Settings & Data categories and describes passphrase-encrypted .rayconfig files. It separately states that Snippet JSON exports are not encrypted.

The same page also creates uncertainty. Its v1 migration paragraph says Clipboard History is extra data absent from .rayconfig exports. That conflicts with the category list. Check your installed version and actual export selections before relying on a backup or restoration. An encrypted export saved in a synchronized folder can also move beyond the device. Encryption doesn't control where you save it.

Review selected text before Send to AI Chat

The Clipboard History Action Panel documents Send to AI Chat as opening a chat with the entry as context. Pause before using it. Read the selected content and remove sensitive detail the task doesn't need. Proceed only if the handoff is permitted. You can stop at retrieval.

Raycast's AI privacy documentation describes forwarding input to provider APIs for Raycast-provided models. Its no-training statements are not a universal promise of no processing or storage. Retention depends on the route; chat sync, attachment storage, and memory add separate considerations.

Selecting a local model doesn't answer every privacy question. Chat-history sync and enabled AI Memory still need review. The same AI privacy policy says enabled Memory periodically processes recent chats from any model using a Raycast-hosted model. Check the current policy for your chosen route; assurances from another configuration may not apply.

Local clipboard storage is not a blanket network-isolation promise either. The clipboard manual documents fetching social-card images and favicons when link visual information is enabled. Discuss the specific feature and setting, not an unsupported claim that Raycast never communicates outside the device.

Common mistakes and limits of this guide

The mistake to avoid is treating one setting as an answer to several different questions. Unlimited retention doesn't turn history into a research library. A source-app exclusion doesn't establish universal secret detection. Disabling Snippet expansion says nothing about capture from that app. And exclusion from Cloud Sync doesn't prevent a separate export or AI handoff.

Vendor documentation supports the feature descriptions; it does not establish independent security assurance. No installation, settings change, clipboard inspection, export, AI request, benchmark, or security audit was performed for this guide.

Check the installed version and account plan, along with application compatibility and organizational policy. The export documentation conflict remains unresolved here. This Mac guide establishes neither Windows or iOS parity nor regulatory compliance. Budget time to review settings and maintain saved wording. Those costs belong in any assessment of whether the workflow helps.

Start small enough to inspect

Begin with a harmless public excerpt and a reusable response you are permitted to maintain. Follow the excerpt to its intended destination. Review the response before saving it. Expand the workflow only after you've checked those decisions against the settings you actually use.