Getting started
Install the app, import a license, and build the first context bundle.
Open docsSupport
Get help without exposing sensitive source code. Start with the docs, then send a minimal sanitized support report if you still need help.
Search docs first
The docs contain the fastest answers for install, license, repository, token, scanner, and Git issues. Use the docs sidebar or your browser's page search to narrow the topic.
Troubleshooting
Common fixes for install, repo scan, token count, Git diff, and scanner warnings.
TroubleshootFrequently asked questions
General product, privacy, LLM compatibility, pricing, install, and troubleshooting answers.
Read FAQCommon support topics
Choose the closest topic before sending an email. These links are safer than attaching source code or generated context bundles to a first support message.
Installation problems
Use this path for Gatekeeper prompts, DMG installation, checksum mismatch, macOS permissions, and first-launch issues.
View guidanceLicense activation
Use this path for license import, expired or invalid license files, paid plan status, and signed offline license questions.
View guidanceBilling and cancellation
Use this path for Pro subscription renewal, cancellation, Stripe receipts, invoice questions, and billing email mismatches.
View guidanceRepo scanning issues
Use this path when a repository will not open, files are missing, ignore rules behave unexpectedly, or macOS blocks folder access.
View guidanceSecret scanner false positives
Use this path when a test fixture, example value, or synthetic demo credential is flagged before copy/export.
View guidanceGit diff issues
Use this path for missing refs, shallow clones, large diffs, rename handling, deleted files, and base/head confusion.
View guidanceInstallation problems
Use this path for Gatekeeper prompts, DMG installation, checksum mismatch, macOS permissions, and first-launch issues.
Start here
License activation
Use this path for license import, expired or invalid license files, paid plan status, and signed offline license questions.
Start here
Billing and cancellation
Use this path for Pro subscription renewal, cancellation, Stripe receipts, invoice questions, and billing email mismatches.
Start here
Repo scanning issues
Use this path when a repository will not open, files are missing, ignore rules behave unexpectedly, or macOS blocks folder access.
Start here
Secret scanner false positives
Use this path when a test fixture, example value, or synthetic demo credential is flagged before copy/export.
Start here
Git diff issues
Use this path for missing refs, shallow clones, large diffs, rename handling, deleted files, and base/head confusion.
Start here
How to send a safe support report
A good first report is specific and sanitized. It should help reproduce the problem without exposing client-confidential material.
Include
- PastePrompt version and release channel.
- macOS version and Apple Silicon or Intel architecture.
- Which workflow failed: install, license, repo scan, scanner, Git diff, or export.
- Exact error text or a sanitized screenshot.
- Whether the repository is local, external drive, network drive, or synced folder.
- For Git issues, sanitized base/head ref names and whether the refs exist locally.
Do not include unless explicitly requested through a secure channel
- source code;
- private keys, API keys, tokens, passwords, or license secrets;
- client-confidential repository names, issue details, audit reports, or generated bundles;
- full filesystem paths that expose client names or private projects.
Still blocked?
Contact support with a sanitized report. Do not attach private source files, secrets, generated bundles, or client-confidential material in a first-contact email.