Tabnine
https://docs.tabnine.com/main/getting-started/context-engine
Enterprise Context Engine builds a multi-dimensional knowledge graph from repos + CI/CD + PRs + tickets + docs at the org level. Individual completions stay session-scoped. Tabnine Agents (Nov 2025) adds team-shared agent context.
At a glance
- Type
- Org-level Context Engine + Tabnine Agents
- Tier
- T2
- Section
- Coding-agent memory
- Created
- 2023-11
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- Free + paid
- Funding
- $25M total Series B · 2023-11
Taxonomy
- storage
- graph
- retrieval
- graph-traversal
- persistence
- long-term
- update
- extraction
- unit
- document
- governance
- opaque
- conflict
- none
When to use
Optimised for: enterprise privacy + org-level Context Engine
Anti-fit: not for non-coding tasks
Pros & cons
Pros
Long-running enterprise coding assistant with on-prem option; memory respects enterprise data boundaries.
Cons
Slower model adoption than newer entrants; on-prem deployment is heavyweight.
Claims & capabilities
Cross-session memory only on enterprise tier (org-level).
Technical surface
- API surface
- not applicable — IDE plugin
- Backend storage
- custom
- Deployment
- Both
- Embedding model
- locked
- Multi-tenancy
- Deployment options: protected SaaS / single-tenant SaaS / VPC / on-prem Kubernetes / fully air-gapped
- MCP
- searched not found — no public MCP support documented as of 2026-05
- A2A
- searched not found
- OpenTelemetry
- searched not found
Similar systems
Other coding-agent memory in the catalog, ranked by inbound references.
- Aider T2
Appends conversation turns to .aider.chat.history.md in project root. restore_chat_history defaults to false — no automatic replay into new sessions. Community /session save command for JSON state snapshots. .aider.conf.yml carries static preferences.
- Augment Code T1
Real-time knowledge graph indexed from connected repos + commit history + CI/CD + tickets + docs. Separate Agent Memory layer (Sept 2025) captures session decisions/corrections/goals as discrete items with developer review/approval UI. MCP endpoint exposes the graph.
- Bolt.new (StackBlitz) T2
In-browser WebContainer (Rust-backed shared memory) is the implicit state store. No dedicated memory abstraction — project files are the state. Team plan adds shared workspaces + GitHub integration.
- Continue.dev Memory MCP T2
Official Memory MCP (Mar 2025) backed by a knowledge graph. Memory is injected via MCP rather than native to the Continue core. Scope depends on MCP server deployment (local or shared).
- Devin (Cognition) T1
Structured Knowledge items stored server-side. Three-tier scope: repo-pinned (always injected), global (recall by relevance), org/enterprise (visible to org members). Auto-generates Repo Knowledge from repo structure each session; reads past session trajectories for self-improvement; writes notes for recurring scheduled tasks.
- Lovable T2
Long-term context stored as files in /docs that the agent reads on each session. Agent Mode (default since July 2025) holds working context within session but doesn't persist cross-session beyond filesystem state.