Common Issues
Signal Issues
Signal Not Appearing
Symptoms: No Signal cards appear even when coding.
Possible causes and solutions:
-
Detection not triggered
- Signal triggers after 2 seconds of inactivity
- Try pressing
Option+Cmd+E(macOS) orAlt+Ctrl+E(Windows/Linux) to manually trigger
-
Monthly quota exhausted
- Check your usage in Account settings
- Consider upgrading your plan or purchasing a Request Pack
-
No issues detected
- Signal only appears when it finds actionable problems with clear solutions
- Some code patterns may not trigger Signal detection
Signal Card Disappeared
Symptoms: Signal card vanished before you could act on it.
Possible causes:
- Auto-dismissed after 3 minutes of no interaction
- Code was manually fixed (AI detected issue no longer exists)
- You pressed
Escaccidentally
Solution: Trigger Signal detection again with Option+Cmd+E.
Chat Issues
Chat Not Responding
Symptoms: Sent a message but no response appears.
Possible causes and solutions:
-
Network connection
- Check your internet connection
- Try refreshing VS Code
-
Quota exhausted
- Verify your monthly Requests haven't been used up
- Check Account settings for usage details
-
Server issues
- Wait a moment and try again
- Check Enia status page for any outages
Chat Context Lost
Symptoms: Enia doesn't seem to remember earlier conversation.
Note: Enia maintains one continuous conversation. If context seems lost:
- Try referencing specific context with
@Fileor@Task - Quote the relevant previous message using right-click → Quote
Login & Account Issues
Cannot Log In
Symptoms: Login fails or keeps redirecting.
Solutions:
- Clear browser cookies and try again
- Try a different browser for the OAuth flow
- Check if your Enia account is active
- Contact support if the issue persists
Quota Not Updating
Symptoms: Usage shows incorrect numbers after purchasing.
Solutions:
- Wait a few minutes for the system to sync
- Sign out and sign back in
- Contact support with your purchase confirmation
Performance Issues
VS Code Slow After Installing Enia
Symptoms: Editor becomes sluggish.
Solutions:
-
Reduce indexed files
- Add large directories to
.eniaignore - Example:
node_modules/,dist/,build/
- Add large directories to
-
Restart VS Code
- Sometimes a fresh start resolves performance issues
-
Check extension conflicts
- Disable other extensions temporarily to identify conflicts
High Memory Usage
Solutions:
- Add non-essential directories to
.eniaignore - Close unused editor tabs
- Restart VS Code periodically for long sessions
Getting More Help
If your issue isn't listed here:
- Check the FAQ for additional answers
- Contact us at contact@eniacode.com with:
- Your VS Code version
- Enia extension version
- Steps to reproduce the issue
- Any error messages