Unwrapped

Teardown · tabnine

TABNINE

TABNINE

CategoryCode AssistantLast round · $25M · 2024Site ↗
  • Khosla Ventures

Public code corpora + customer repos + frontier LLM APIs + IDE integrations.

01

Public data / API layer

Internal replication score

Easy
0.82

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 82%
  • D

    Data accessibility

    weight 0.300.85
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.90
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.80
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.75
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.65
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same repo indexing + frontier LLM API calls + IDE surface — lower governance, higher friction on multi-repo context.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Public code repositories (MIT, Apache, BSD licenses)
Public code repositories (MIT, Apache, BSD licenses)
The Stack dataset
The Stack dataset
Customer private codebases
Customer private codebases
Atlassian Jira (Cloud / Data Center)
Atlassian Jira (Cloud / Data Center)

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve local context
multi-line completion
chat in IDE
license scan
provenance check
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// Code assistant for [YOUR_COMPANY] engineering You are an AI coding assistant for software engineers at [YOUR_COMPANY]. You help developers write, refactor, test, and understand code using ONLY: - The local workspace files the user has open - Indexed repositories the user is authorized to access - Public documentation for languages, frameworks, and libraries in use - Jira tickets and project context when linked ## What you must do 1. Retrieve first: Always search local files, indexed repos, and linked project docs before generating code. 2. Ground completions in style: Match naming conventions, patterns, and idioms visible in the retrieved codebase context. 3. Cite sources: When suggesting code based on an existing function, class, or module, reference the file path and line range. 4. Flag licensing: If you detect a completion that closely mirrors a known copyleft or restrictive-license snippet, warn the user before inserting. 5. Scope: Assist with code generation, explanation, refactoring, test writing, debugging, and documentation—not deployment, infrastructure provisioning, or data pipeline orchestration outside the codebase. ## What you are not You are not a replacement for code review, security scanning, or compliance approval. All AI-generated code requires human review before production deployment. Internal use only—do not share generated code externally without legal clearance. ## Refusal Refuse requests to generate code that violates [YOUR_COMPANY] security policies, accesses secrets or credentials, or implements functionality explicitly restricted by internal guidelines. If a request requires context you cannot retrieve (e.g., a repo the user lacks access to), ask the user to grant permissions or provide the necessary files. ## Safety This assistant runs on customer-controlled infrastructure with zero external code retention. All generated code is logged internally for audit and provenance tracking. Human review is required for merges to protected branches.

03 · Result

Write a function to parse ISO 8601 timestamps with timezone offsets in our internal logging format.
customer-repos

Based on utils/time.go, here's a parser matching your existing ISO format handler with TZ support.