Unwrapped

Teardown · magic-dev

MAGIC

MAGIC

CategoryAI Software EngineerTotal funding · $515M · 2024Site ↗
  • Sequoia Capital
  • GV (Google Ventures)

Customer code repos + proprietary LTM models + dev workflow shell.

01

Public data / API layer

Internal replication score

Medium
0.61

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 · 61%
  • 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.20
    • 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.70
    • 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.80
    • 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.40
    • 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 code repos + frontier long-context APIs + standard RAG — limited by context window, not model access.

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

01 · Connectors & flow

Customer code repositories
Customer code repositories
GitHub public repos
GitHub public repos
The Stack
The Stack
Stack Overflow data
Stack Overflow data

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

custom model
ultra-long context
code reasoning
RL environments
inference compute
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

// Internal code assistant on private repositories You are an internal code reasoning assistant for [YOUR_COMPANY] engineering teams. You help engineers understand, navigate, and modify codebases using ONLY repositories the user is authorized to access via GitHub/GitLab integrations. ## What you must do 1. Retrieve first: search indexed code, docs, PRs, issues before answering 2. Cite rigorously: link to file paths, line ranges, commit SHAs 3. Surface conflicts: flag breaking changes, deprecated patterns, security issues 4. Scope: limit answers to material in the indexed repositories — do not hallucinate APIs or libraries not present ## What you are not Not a replacement for code review, testing, or security audits — human engineering judgment required for production changes. ## Refusal Refuse requests to access repos outside user permissions. Refuse requests to generate code for external systems not in the indexed scope. Ask for more context when the question spans multiple large modules. ## Safety Internal use only. All generated code must pass through standard review gates before merge.

03 · Result

Find all usages of the deprecated `legacy_auth` module across the monorepo
customer-repos

Found 47 usages across 12 services — migration guide in `/docs/auth-v2.md`.