리얼-SWE: 비공개 실제 기업 코드베이스에서 AI 모델 평가

September 2026 Introducing Real-SWE Benchmarking frontier AI models on private, real-world, enterprise codebases. . ;+;+;:;+;+;.# ; ; ; . . . . ; . + ; ; . . : @;;+;+# +;+;+;+;:;+:# : : ; . ; ; ; @;+;+.+;:;+;+* ; . . : ; . . : ; @++:;:;+.;;@ ;. . . . .: . ; . . . .; @++;;;;+;:;@ ; : ; ; @;+++:@;++;:+ ; : : . :+.+;;;+:;@ ; : + . ; . . . ; ; . ; : . . . . ; . . . . .; ; . . . . .+ + . . . .; ; . . . . .; ; . . : ; : ; ; ; ; : ; . ; . ; ; ; ; : ; . . % . . ; : . . . . ; ; ... . . .; +. . . . .: ;. . :.. .: : . . ::. . . ; . . . .; : *. @ ; ; +.@ . ; : +: *+ : ; :. %+; +. ; *. *# @: :.*. ; ; . . .;::@;; . . ; :#@;. ..@:. . ;.@%: .:@%:: :. . #+. :@%;. .:@*. .: @+ . #*. . ;@#.;.* . . .: .::: ..:%@@+@+#... :+:%@@+..:@@@::*.:;@@:..+@@:; *.::#@@#:..:@@#...+@#: :*:%@@+ .:.+::..*@@:@@@#;.. ::.# +@#.@ .*@: .*@%: *: :@%. ;@@: .@%. @ .;@@: .: :@#..#@*. +@#.@ .@ .*@%:. *: %+ ;@@: #; +# .;@@: .. @: .#@*. @. .. ;@ .*@%: *: @@ ;@@: %# * # .;@@: @+ .@ :*#.. @:: @. . ::;. @@ .. . @% .*@ ;@. %.@ .. .@; . @@ .. .@@. .. @:# ... . ;%# . @@ +;#: .. .@ @ . ... ... .. .. ... .. ... . 01 Introduction Today we are releasing Real-SWE, a benchmark that evaluates frontier AI models on private, real-world, enterprise codebases. Each task comes from a private production codebase that we licensed from a real-world company. These are problems their engineers work on, with all the context and complexity that comes with an existing product. Private codebases. Agents must navigate proprietary systems whose code and solutions aren’t available on the public internet. Work with business consequences. Getting billing right, calculating taxes, migrating customers. Changes that affect how a business runs, often across multiple services. Company-specific complexity. Every company has its own rules and ways of writing code. Agents have to understand those conventions and make changes that work with what’s already there. Can a coding agent actually do the work of a software engineer in the real world? Expert-generated or synthetic tasks can be well designed, but they aren’t the verbatim, actual tasks that engineers in real companies need to do. Our tasks differ on two axes: the underlying coding artifact and specificity of the instruction. Both add complexities that challenge today’s frontier models. We use native harnesses to reflect how enterprise engineers work in practice, evaluating model-and-harness combinations rather than models in isolation. Real company tasks require company-specific context Correct billing depends on business rules and external services Fix invoice billing so each business charges the right tax and exempt customers aren't taxed. View full instruction Hide full instruction ▾ Billing reopens on Monday and every invoice this service issues is coming out untaxed. Each business on the platform settles its tax a different way: some maintain a rate themselves, some want each invoice priced against the buyer's destination by our tax authority provider, and some collect nothing at all, while a customer we hold an exemption for is charged nothing whichever way its business is configured. Pricing a destination means going to the authority with both addresses, the priced lines and the product category that business sells under, on the sandbox or the production authority according to the account the business is on; an address the authority refuses must be reported without stopping the invoice. The rate, the tax and the gross belong on the issued invoice, and once an invoice is settled the sale is filed back to the authority under that invoice's number so the returns reconcile. Invoices between European parties show both sides' VAT registrations. The authority and ledger are available at TAX_JAR_URL , PROD_TAX_JAR_URL and INFLUX_URL . Services in the sandbox TJ TaxJar sandbox TJ TaxJar production InfluxDB ledger NestJS service TypeScript Agents work across code, infrastructure, and business tools Tools and services across Real-SWE task environments. Each task exposes only the services its workflow needs. AWS emulator Docker Kubernetes GitHub Linear MCP PostgreSQL MySQL MongoDB Ge Gel Redis Go Python Node.js Vitest Slack Intercom Google Drive Email ClickUp Codebase Selection We selected codebases through a rigorous screening process, focusing on real companies with substantial usage, strong engineering teams, and demanding production workloads. The sample tasks analyzed below come from these codebases, including: A Luma/Partiful competitor with 200K+ users and a top 100 App Store ranking A consumer fintech platform processing 100K+ bank statements Enterprise AI sales platforms supporting complex business workflows We prioritize code written to meet an actual user or business need over code written solely to create a benchmark task. Production engineering requires understanding existing architecture, preserving behavior that users rely on, and making changes within real operational constraints. Brief instructions can require changes across many files Our tasks describe the change needed, leaving agents to discover implementation details in the codebase and surrounding tools. Any behavior required by the verifier must be stated or reasonably discoverable. This leads to our prompts being slightly underspecified, about par with DeepSWE and Terminal Bench, but specific enough to not omit instructions. The work is cross-functional and complex: a single change can span multiple parts of the application. Agents must understand existing business logic and company coding patterns while keeping the surrounding system working. Models fail even in short rollouts. 71.4 % of rollouts under 10 minutes failed, compared with 73.4 % of longer rollouts. Triaging multiple systems and understanding requirements in codebases riddled with existing business logic and coding patterns is difficult. Failed Passed Every task is inspired or lifted verbatim from a private, real-world codebase. We find these types of tasks super interesting for three reasons: Tasks on private codebases are natively out of distribution. These types of coding tasks are not available anywhere on the internet and are unlikely to have ever been trained on by any other ai model. 99% of tokens in real-world enterprises are hidden away from the frontier models. These tasks are economically viable work. Each task here has a direct relationship to spend and was assigned to an engineer earning a salary. Most benchmarks test interesting, experimental capabilities that are often unlikely to be widespread in the real-world. Company-specific engineering patterns matter. Does AI code match the bar of a real-world enterprise? Our results show us that we're far from that reality. Many enterprises care about code standards and patterns. We've found that today's models are weaker at understanding company coding patterns and frequently miss requirements or don't verify their assumptions. 02 Analysis Here's an analysis of a small sample of tasks from our benchmark. If you're interested in the sample, request access here . Missed requirements are the most common failure Failures are grouped by observed submission behavior using the same taxonomy across models, following DeepSWE . Fable 5.1 24.5 % 36.7 % 34.7 % 4.1 % GPT-6 Astra 34.0 % 28.3 % 34.0 % 3.8 % Gemini 3.8 Flash 10.9 % 29.1 % 49.1 % 10.9 % GLM 5.3 28.1 % 38.6 % 26.3 % 7.0 % Grok 4.6 24.6 % 67.2 % 8.2 % Muse Spark 1.3 19.7 % 36.1 % 41.0 % 3.3 % Kimi K3 15.4 % 53.8 % 27.7 % 3.1 % GPT-5.6 Sol 43.3 % 31.3 % 16.4 % 9.0 % Unverified assumption Missed requirement Integration error Regression Wrong file Different models fail in different ways Percentages are out of each model's failed runs, not all runs. 03 Effort & the Frontier Estimated rollout costs range from $2.50 to $6.96 Rank Model Estimated cost (USD) 1 Gemini 3.8 Flash $2.50 2 GPT-5.6 Sol $2.65 3 Muse Spark 1.3 $2.74 4 Grok 4.6 $3.44 5 Kimi K3 $3.90 6 GPT-6 Astra $4.67 7 GLM 5.3 $5.12 8 Fa