Troubleshooting

Common issues and solutions for MyClaude buyers — installation, purchases, downloads, CLI, and account problems.

Each entry follows the pattern: symptom, cause, fix. If your issue is not listed here, contact support using the guidance at the bottom of this page.

Installation issues

Product files exist but Claude Code does not detect them

Symptom: You installed a product and the files are in .claude/, but Claude Code does not recognize the skill, agent, or workflow.

Cause: Claude Code reads the .claude/ directory at startup. Files added mid-session are not detected automatically.

Fix: Restart your Claude Code session. If the product still does not appear, verify the files are in the correct subdirectory — for example, skills must be in .claude/skills/{product-name}/, not .claude/{product-name}/.

myclaude install fails with "EACCES permission denied"

Symptom: The CLI throws a permission error when writing files to the .claude/ directory.

Cause: The current user does not have write permission to the project directory or the .claude/ subdirectory.

Fix: Check directory permissions with ls -la .claude/. On Unix systems, run chmod -R u+w .claude/ to grant write access. On Windows, right-click the folder, go to Properties, and adjust permissions under the Security tab.

myclaude install fails with "product not found"

Symptom: The CLI reports the product handle does not exist in the registry.

Cause: The handle is misspelled, the product was unpublished by the creator, or the product is in a different registry region.

Fix: Double-check the exact handle on the product page at myclaude.sh. Handles are case-sensitive and follow the @creator/product-name format. If the product page loads on the web but the CLI cannot find it, run myclaude login to refresh your session.

Installation succeeds but the product does not work correctly

Symptom: Files are installed and detected, but the product behaves unexpectedly or throws errors.

Cause: Version mismatch with your Claude Code version, missing dependencies, or a product bug.

Fix:

1. Check the product page for version compatibility notes.
2. Run myclaude update @creator/product-name to ensure you have the latest version.
3. Read the product's included README or documentation for configuration requirements.
4. If the issue persists, leave a review describing the problem or contact the creator through their profile page.

Purchase issues

Stripe Checkout page does not load

Symptom: Clicking Buy redirects to a blank page or shows a Stripe error.

Cause: Browser extensions (ad blockers, privacy tools) may block Stripe's hosted checkout domain. Alternatively, Stripe may be temporarily unavailable in your region.

Fix: Disable ad blockers and privacy extensions for checkout.stripe.com, then retry. If the page still does not load, try a different browser. Stripe availability by country is listed at stripe.com/global.

Payment completed but no order appears in my dashboard

Symptom: Stripe charged your card, you received a Stripe email receipt, but the order does not appear at myclaude.sh/dashboard.

Cause: The Stripe webhook that creates the order may be delayed. Under normal conditions this takes under 10 seconds, but network issues can extend it to a few minutes.

Fix: Wait 2 minutes, then refresh your dashboard. If the order still does not appear after 5 minutes, contact support with your Stripe receipt email — it contains a payment ID that can be used to locate and reconcile the order.

Duplicate charge for the same product

Symptom: You see two charges on your bank statement for a single product.

Cause: This is rare but can occur if you clicked Buy twice in quick succession before the first checkout session completed.

Fix: Contact support with both charge references from your bank statement. Duplicate charges are refunded within 5-10 business days after verification.

Refund not received

Symptom: Support approved a refund but the amount has not appeared on your statement.

Cause: Refunds are processed through Stripe and typically take 5-10 business days to appear, depending on your bank.

Fix: Check your Stripe receipt email for the refund confirmation. If more than 10 business days have passed without the refund appearing, contact your bank with the Stripe refund reference.

Download issues

Download button does not appear after purchase

Symptom: You completed payment but the product page still shows Buy instead of Download.

Cause: The order confirmation webhook has not yet been processed.

Fix: Wait 30 seconds and refresh the page. If the button does not change within 2 minutes, try logging out and back in to refresh your session. Check your dashboard — if the order appears there, the product page may need a hard refresh (Ctrl+Shift+R / Cmd+Shift+R).

Signed URL expired before download completed

Symptom: The download starts but fails partway through, or the browser shows an access denied error.

Cause: Signed download URLs expire after 5 minutes. Large files on slow connections may not complete in time.

Fix: Return to the product page and click Download again to generate a fresh signed URL. There is no limit on how many times you can request a new URL.

Downloaded ZIP file is corrupted

Symptom: Extracting the ZIP fails with a CRC error or "unexpected end of archive."

Cause: The download was interrupted or the file was partially transferred before the signed URL expired.

Fix: Delete the corrupted file and re-download from the product page. If corruption recurs, try a different browser or use the CLI (myclaude install @creator/product-name), which includes integrity verification.

CLI issues

myclaude command not found

Symptom: Running myclaude in the terminal returns "command not found" or "not recognized."

Cause: The myclaude CLI is not installed globally, or the npm global bin directory is not in your system PATH.

Fix:

$ npm install -g @myclaude-cli/cli

If the command is still not found after installing, check your PATH:

$ npm config get prefix

Ensure the bin/ subdirectory of that path is in your system PATH. On macOS/Linux, add it to your shell profile (~/.bashrc, ~/.zshrc). On Windows, add it via System Environment Variables.

myclaude login opens browser but authentication does not complete

Symptom: The browser opens to the MyClaude login page, you sign in, but the CLI never receives the confirmation.

Cause: The local callback server that receives the auth token may be blocked by a firewall or the browser redirect failed.

Fix:

1. Ensure no firewall or antivirus is blocking localhost connections on the port the CLI uses (shown in the terminal output).
2. After signing in on the web, check if the browser shows a "You may close this tab" message. If it does, return to the terminal — the CLI should have received the token.
3. If the CLI is still waiting, press Ctrl+C and try myclaude login again.

myclaude update reports "already up to date" but the product page shows a newer version

Symptom: The CLI says no updates are available, but the web interface shows a newer version number.

Cause: Registry cache. The CLI caches the product registry locally to reduce network requests.

Fix:

$ myclaude cache clear
$ myclaude update @creator/product-name

myclaude repair does not detect manually installed products

Symptom: You placed product files manually in .claude/ but myclaude repair does not find them.

Cause: The repair command identifies products by their manifest file (vault.json or .vault-manifest). If the product was extracted without this file, repair cannot recognize it.

Fix: Re-download the product from the web or CLI to get a complete package with the manifest. Alternatively, create a minimal vault.json in the product directory:

{
  "name": "@creator/product-name",
  "version": "1.0.0",
  "category": "skills"
}

Then run myclaude repair again.

Account issues

Cannot log in — "account not found"

Symptom: You enter your email and password but MyClaude says the account does not exist.

Cause: You may have registered with a different authentication provider (Google, GitHub) than the one you are trying now.

Fix: Try all available sign-in methods on the login page. MyClaude supports email/password, Google, and GitHub authentication. If you registered with Google, clicking "Sign in with Google" will find your account.

Username change not reflected on published reviews

Symptom: You changed your username in settings but your old username still appears on reviews you wrote.

Cause: Username propagation to existing reviews may take up to 24 hours.

Fix: No action needed. The update propagates automatically. If your old username still appears after 24 hours, contact support.

Cannot access purchases after changing email

Symptom: You changed your email address and can no longer see your purchase history.

Cause: Email changes do not affect your account identity — purchases are tied to your account UID, not your email. This symptom usually indicates you accidentally created a second account with the new email instead of updating the existing one.

Fix: Log out and sign in with your original authentication method. If you have two accounts and need them merged, contact support with both email addresses.

Error codes

If the CLI or API returns a numeric error code, use this table to identify the cause:

Contact support

If your issue is not covered here or the suggested fix does not resolve it:

1. Visit myclaude.sh/dashboard and click Support in the navigation.
2. Describe the issue, including: what you were trying to do, what happened, and any error messages or codes.
3. Include your MyClaude username and, for purchase issues, the Stripe receipt email or payment ID.

Support responds within 48 hours on business days.

Related pages

• Installing via CLI — CLI installation tutorial
• Installing via Web — web download and manual install
• Purchasing Products — payment flow and receipts
• Managing Products — update, list, and uninstall
• Ratings and Reviews — leaving and editing reviews