Official support

Need help with ClipGate?

Use this page for support questions, install issues, and release feedback. The public site is the right place to find docs and downloads, while official installs stay aligned across the site, PyPI, and Homebrew.

Docs first

If you are installing or updating, check the Docs, Release Notes, and the install tabs on the home page first.

Common Questions

Is ClipGate free to use?

Yes. ClipGate is free to use through the official install channels today. If advanced paid features are added later, the goal is to add value for power users and teams without blocking the core CLI.

Can I use ClipGate at work or in an enterprise environment?

Yes. ClipGate is designed to feel comfortable in professional environments where stability, transparency, and controlled usage matter. If your organization needs commercial terms, procurement details, or support assurances, contact support.

Does ClipGate keep my clipboard data local?

Yes. ClipGate is designed to be local-first, and the official install channels all resolve back to the same packaged local tool. The browser extension also keeps its data local in the browser unless a future feature explicitly says otherwise.

How do I install or update ClipGate safely?

Use the installer from the home page, pip install clipgate, brew install clipgate/tap/cg, or visit Release Notes for versioned binaries and checksums. For updates, use the same official channel you installed from unless the docs say otherwise.

How does ClipGate classify copied content?

ClipGate inspects copied content and assigns it to developer-relevant types like errors, commands, paths, JSON, URLs, and secrets. That makes retrieval semantic rather than purely chronological.

Are secrets stored on disk?

Sensitive content is treated differently from normal clipboard history. Secrets should stay memory-only where possible, avoid unnecessary output, and respect the tool's protective handling instead of being written into long-lived history by default.

What is the difference between the CLI and the browser extension?

The CLI is for terminal-first workflows, scripting, and local automation. The browser extension is for in-browser capture and browsing workflows, with its own local storage and browser-native experience.

How do I get help fast?

Start with the docs and release notes, then send support the exact command, version, and error you saw. That makes it much easier to tell whether the issue is install-related, environment-specific, or a product bug.