Tabby
TabbyML/tabby
Self-hosted AI coding assistant — autocomplete and assistant features on your infra. GitHub: TabbyML/tabby (~34k stars).
GitHub repository
Overview
Tabby (TabbyML/tabby) is listed in LimeDock Directories as an AI agent resource. Self-hosted AI coding assistant — autocomplete and assistant features on your infra. Group: coding-agents. Community size: ~34k GitHub stars. Repo (copy/paste): https://github.com/TabbyML/tabby This page is a plain-English guide so searches for the GitHub project can land on how teams actually use it.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Agents are a starting point. LimeDock turns the workflow into production automation your SaaS team owns — not another prompt library.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Open the GitHub repository, then follow the README for your stack.
Official GitHub repository: https://github.com/TabbyML/tabby GitHub path: TabbyML/tabby
How to open it: 1. Copy: https://github.com/TabbyML/tabby 2. Clone or follow the README for your OS/stack. 3. Start with the smallest example before production use.
How to use it
**Simple example** Security wants coding AI without sending code to a public SaaS.
1. Deploy Tabby. 2. Point the IDE extension at your Tabby server. 3. Index allowed repos only.
Example prompts
- “Deploy Tabby for our eng team’s self-hosted autocomplete.”
- “Tabby vs cloud Copilot for compliance?”
- “Which repos should be excluded from indexing?”
Use cases and examples
- Evaluate TabbyML/tabby as an AI agent building block
- Pilot Tabby on one staging workflow
- Compare against agents you already pay for
- Document a team playbook after the pilot
Prerequisites
- GPU/CPU server
- IDE extensions
- Access control
Tips
- Scope indexed code carefully.
- Measure suggestion accept rates.