Tabby
Self-hosted, open-source AI coding assistant (Copilot alternative) shipping as a single…
Self-hosted, open-source AI coding assistant (Copilot alternative) shipping as a single binary/Docker with built-in admin and IDE extensions, plus an agent preview. The go-to self-hosted/on-prem coding assistant for data-residency teams; large GitHub following and broad IDE coverage (VS Code, JetBrains, Vim, Eclipse). Self-
Roadmap
Status
SDK / Library
Pattern
Rust
Runtime
Not yet published
SDK version
Readiness
What “Roadmap” means for Tabby
On the integration roadmap. The platform-side spine for this framework's pattern is already shipped — what remains is the per-framework adapter. Selecting it in the dashboard opens the “Get notified” path rather than creating an actor.
How it attaches
SDK / Library.
Install the trustvice-actor-tabby package and call witness.attach() once during agent initialisation.
Install the Trustvice adapter package from npm, PyPI, or cargo and call witness.attach(agent) in your application.
cargo add trustvice-actor-tabby
- 1
Install the adapter
Add trustvice-actor-tabby to your project from cargo.
- 2
Issue a workspace API key
Generate a twk_-prefixed key in the dashboard under Settings → API Keys, scoped to the workspace and environment this agent's data should land in.
- 3
Attach the witness
Call witness.attach(agent) once when you initialise your Tabby agent. The adapter registers the framework callbacks, handles retries, and performs the workspace handshake.
- 4
Verify
Trigger one agent run. The dashboard's Witness page shows the canonical record within ~1 second of the agent emitting it.
cargo add trustvice-actor-tabby
Tabby is on the roadmap. The steps above describe how the integration works on the SDK / Library pattern — whose platform-side spine is already shipped — but the Tabby-specific adapter isn't generally available yet. Tell us you're running it and we move it up the queue.
Coverage
Coverage pending.
The captured-event list is published once the Tabby adapter ships. Every adapter normalises into the same canonical Witness record, so the dashboard, queries, exports, and lens evaluations are identical regardless of which events a given runtime emits.
The full pattern guide
SDK / Library — end to end.
Every framework on this pattern shares the same platform-side spine, endpoints, and gotchas. The pattern guide covers them in full.
Read the SDK / Library guideNeed help landing Tabby?
Talk to the integration team.
We help you land the integration end to end — including the parts that live in your environment.
Request integration help
Trustvice 360Declare the rules. Have every run checked.
Agents, evidence, governance, commerce and disclosure are all in Trustvice 360. Sign up free and open every suite from one dashboard.