Clipboard

Clipboard installed: first hour

Close detail of the stack-clip underline and sand sheet edge on cool gray paper.
Stack-clip detail for the clipboard mark used across this install guide. Ledger Ink original stack-clip geometry for factory-clipboard (not a CopyQ logo).

You reached this page after installing CopyQ for a clipboard job. The next hour is about proving the tray, setting one hotkey, and writing down the update door so next month is calm.

1. Confirm the tray icon

Launch CopyQ if it is not already running. Find the tray icon, open the main window, and keep that window visible while you run the next checks for this clipboard session.

2. Copy three harmless strings

Copy alpha, then beta, then gamma from a text editor. Open CopyQ and confirm all three appear. Paste beta into a note to prove reuse works.

3. Set a show-window hotkey

Open Preferences and choose a show-window shortcut you will remember. Avoid combinations already taken by other apps so the clipboard window appears on the first try.

4. Decide how many items to keep

Pick a retention size that fits your desk. More items help search; fewer items reduce how long secrets linger in the tray after a busy day.

5. Optional start at login

If you want the clipboard tray every morning, enable start-at-login in Preferences when the option is present on your OS build. Skip it on shared kiosk accounts.

6. Clear a test secret

Paste a fake token into the tray on purpose, then delete that item. Practice clearing so real secrets do not sit around after support calls.

7. Write the update door

Note whether you used winget hluk.CopyQ, copyq-*-setup.exe, brew cask, a dmg, or the AppImage. That note is the clipboard update path for this computer.

8. Bookmark Releases

Save the hluk/CopyQ Releases URL. When search ads push Softonic-style clipboard pages, you still have a typed door that publishes named assets.

Success is beta pasting correctly, the hotkey opening the window, and the update door written down.

OS notes

  • Windows winget users can confirm hluk.CopyQ in the package log.
  • macOS dmg users should finish the Applications drag before hunting icons.
  • Linux AppImage users must mark the file executable.

More detail: first run, hotkeys, safety, update and uninstall.

Related cluster pages: for this computer, download safely, releases.

Keep this checklist nearby for the next laptop. The steps stay the same even when the CopyQ tag number changes for your clipboard install.

Operations notes

Teams that standardize early spend less time arguing about Softonic buttons. Put the Releases URL and the winget id on the same internal wiki line so every new hire installs the same way on day one.

Checksum discipline matters when security review asks for evidence. Pair the published hash with the exact filename from the tag, store both on the ticket, and refuse renamed blobs that claim to be the same build.

Guest networks and hotel Wi-Fi sometimes inject download interstitial pages. If a browser rewrite changes the file you expected, delete it and fetch again from a cleaner path before you run anything.

Evidence on tickets

  • Store hashes beside filenames.
  • Keep the previous installer one week.
  • Verify the tray before retiring the old binary.

Accessibility needs a keyboard path to the main window. A tray icon alone is not enough for every desk. Confirm the show-window hotkey works from a browser, a terminal, and a rich text editor.

Backup habits beat heroic recovery. Export or copy the configuration folder when you invest time in tabs and commands, then store that backup beside other machine notes you already trust.

Language stays boring on purpose. Job words, product names, and portal names should not swap places mid-paragraph, because support tickets become impossible to search later.

When a major version arrives, skim the upstream release notes once before you push a fleet-wide bump. Most point releases only refresh binaries, yet behavior changes still deserve a quick read.

Clipboard note 1

If paste into a nested remote session fails, isolate layers. Prove local reuse first, then test the remote channel, then change elevation only when policy allows it.

Donated hardware must lose the tray data. Uninstall the app and clear the profile folders so the next owner does not inherit private snippets from your old sessions.

Finally, keep one written rollback plan: previous installer retained for a week, new tray verified with three strings, then remove the old binary. Calm updates are the goal.

Teaching the door

Send coworkers a Releases link rather than a binary through chat. People remember the job word and forget which vendor page was trustworthy last month.

  • Windows: winget or setup.exe
  • macOS: brew or dmg
  • Linux: AppImage

Internal screenshots should show the GitHub filename, not a portal landing page. Visual habits matter as much as written policy when desks are busy.

If search ads outrank Releases for a week, your bookmark still wins. Type the URL.

Closing checklist

  1. Asset name matches the tag.
  2. Tray lists a test string.
  3. Hotkey opens the window.
  4. Update door is written down.