Skip to Content
ReferenceTroubleshooting

Troubleshooting

Fast fixes for common issues.

Quick checklist

  1. Run dotpack build
  2. Confirm generated output exists (.gemini/, .cursor/, .claude/)
  3. Restart/reload your AI tool so it picks up config changes
  4. Re-run your command with a more specific request (files + acceptance criteria)

Installation

dotpack: command not found

npm install -g dotpack dotpack --version

If it’s still not found, ensure your global npm bin is on PATH:

npm config get prefix export PATH="$PATH:$(npm config get prefix)/bin"

Permission errors (macOS/Linux)

Use a Node version manager (recommended), or configure a user-writable global install dir.

License & Activation

Activation limit reached

  • Deactivate on an old machine: dotpack deactivate
  • Then re-activate: dotpack activate DOTPACK_xxxxx

Network errors

  • Confirm you’re online for activation/refresh
  • Retry activation

Commands not available in your tool

  1. Confirm generated output exists: .gemini/, .cursor/, .claude/
  2. Regenerate: dotpack build
  3. Restart the tool so it reloads configuration

Output quality issues

  • Use a more structured request (constraints + references + acceptance criteria)
  • Run /plan first for complex work
  • Encode repeated preferences into skills/commands, then regenerate with dotpack build

Support

Support & feedback: https://dotpack.featurebase.app/ 

Last updated on