←View full Tabby status
Tabby: IDE Extension Not Responding
Current Status: Operational
Last checked: 6m ago
What We're Seeing Right Now
No recent issues reported. If you're experiencing problems with Tabby, report below to help the community.
What is this error?
When Tabby's IDE extension stops working, code completions, suggestions, and AI features become unavailable in your editor. This can be caused by extension crashes, authentication issues, or service outages.
Error Signatures
Extension not respondingConnection lostUnable to connectExtension errorNot authenticatedService unavailableExtension crashedCopilot is not availableCommon Causes
- Tabby extension crashed or lost connection
- Extension version is outdated
- Authentication token expired
- IDE update broke compatibility
- Tabby backend servers are down
- Network/firewall blocking the extension's connection
✓ How to Fix It
- Restart your IDE (VS Code, JetBrains, etc.)
- Check the extension is up to date
- Sign out and sign back in to Tabby
- Check the extension's output log for errors
- Disable and re-enable the extension
- Check this page for Tabby outages
Live Signals
Service Components
Tabby
OperationalRecent Incidents
No incidents in the past 30 days
Frequently Asked Questions
Why is Tabby not working in my IDE?
Try restarting your IDE, updating the extension, and signing in again. If the issue is widespread, check the status above.
Is Tabby extension down?
Check community reports below. If many developers are reporting issues, it's a service-side problem.
How do I fix Tabby in VS Code?
Restart VS Code, check for extension updates, re-authenticate, and check the Output panel for Tabby logs.