🗺️ Roadmap

We continuously work on updating our roadmap and we love to discuss those with our community. Feel encouraged to participate.

Q4 2024

🚀 Enhanced Answer Engine Experience
- Fine-grained step by step visibility: e.g., step to search source code, to extract directory structure.
- Richer source visualization: e.g., GitHub issue status can be visualized.
🛠️ Improved Debugging / Admin Experience
- Enhance background job visibility.
- Enhance model backend status visibility.

Archived

👥 Team Collaboration:
- Thread sharing.
- Activity feeds.
🧩 Richer Integrations:
- Integration with Slack.
- Integration with Notion.
📈 Enhanced Robustness and Efficiency:
- Improved robustness and efficiency of background jobs, such as source code indexing.

🎊 Supports embedding api for document context related use cases: https://github.com/TabbyML/tabby/issues/790
📋 Client side context in IDE / Extensions, e.g recent viewed buffer, local changed files

🔧 Improve RAG by deeper integration with Treesitter using custom query. This will bring LSP-like understanding to Tabby's code index.
🎁 M1/M2 GPU support by utilizing llama.cpp/ggml's inference infrastructure. This will make Tabby much faster on Apple devices.
📘 Improve the documentation and tutorials for Tabby. This will make it easier for people to learn how to use Tabby.
💡 Explore more creative ways of interacting with Tabby. Tabby currently only supports generating text in code completion scenarios, but we plan to add support for other use cases, such as interactive chat in diff mode and Q&A with multiple virtual engineers.