Common issues

The errors we see most often, and the fix for each.

Auth failures

Symptom: 401 Unauthorized from any command that requires a token.

Check:

If it says "not logged in" or shows an outdated email:

1. Visit /settings → CLI tokens.
2. Revoke the old one if it's compromised.
3. Generate a new one.
4. heroprompt logout && heroprompt login --token <new>.

If auth status looks fine but you still get 401s, your token may have been revoked server-side. Generate a fresh one.

Pack install fails

Symptom: heroprompt pack install <id> errors out.

Two common causes:

• Pack already installed. The CLI refuses to overwrite by default. Re-run with --force.
• Network / API down. Retry. If it persists, check status.heroprompt.store (if you have one) or open an issue.

If install starts then fails mid-write, no partial state is left — the CLI stages files in a temp dir and only renames into place once everything's written.

Skills not showing in Claude Code

Symptom: heroprompt pack install developer succeeded, but Claude Code doesn't see the new skills.

Fix: Claude Code only scans ~/.claude/skills/ at session start. Quit your session (Ctrl+C twice or /exit) and start a new one. The skills load on next launch.

Verify the files actually landed:

If the folder is missing, the install didn't write where you expected — re-run with --verbose to see the target paths.

Sync looks out of date

Symptom: /dashboard/packs shows "Update available" but pack sync says everything is current.

The dashboard reads the server registry; pack sync reads your local ~/.heroprompt/installed.json. They drift if you've manually edited the local file or installed packs on multiple machines.

Fix:

Re-fetches every installed pack regardless of local version state.

Still stuck?

• Open an issue: github.com/heroprompt/promptkit/issues
• Email: support@heroprompt.store

Please include: OS + Python version (python --version), CLI version (heroprompt --version), and the full command + output.