If you run into issues while using Hopsule, check the common scenarios below. If your problem persists, reach out to our Support team.Documentation Index
Fetch the complete documentation index at: https://docs.hopsule.com/llms.txt
Use this file to discover all available pages before exploring further.
Common Issues
CLI / IDE Authentication Failed
CLI / IDE Authentication Failed
Issue: You get a
410 Gone error when trying to authenticate the CLI or VS Code/Cursor extension.Solution: Device verification codes are short-lived and expire after exactly 10 minutes for security reasons. Simply restart the authentication process (hopsule login) and visit the URL immediately.Project Brain Import is Taking Too Long
Project Brain Import is Taking Too Long
Issue: The GitHub repository import seems stuck.Solution: Hopsule processes files in parallel (10 concurrent downloads, 5 chunking operations). A medium repo (1,000 files) takes about 3-4 minutes, while a large repo (10,000 files) can take 30-40 minutes. If it exceeds this time, check your project’s
Settings -> Brain to retry the import.Cursor / AI is not respecting my decisions
Cursor / AI is not respecting my decisions
Issue: A decision is accepted, but the assistant still suggests code that conflicts with it.Solution: Reload the latest Capsule in the IDE add-on and confirm MCP is connected to Hopsule. Assistants are advisory; they need up-to-date Capsule and MCP context to align with your rules.
API Errors
Hopsule API always returns a consistent error format. If you are building a custom integration or reporting a bug, please check theerror code and provide the requestId to our support team.