# Cognition — FrontierCode 2.0

- Company: Cognition (cognition.com)
- Announced: 2026-10-27T17:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://cognition.com/blog/frontier-code-2.0
- Record: https://forck.live/items/28360-frontiercode-2-0
- Subject: Devin / SWE
- Models affected: Opus 5.5, Luna, Haiku, Sol, GPT-6.1 Sol

Cognition introduced FrontierCode 2.0, a coding benchmark built with more than 20 open-source maintainers to test whether agent output is actually mergeable. The company says existing coding benchmarks saturate quickly and miss the gaps its own Devin experience exposed, such as inferring user intent and respecting unstated constraints. Tasks now come from 55% more repositories and carry 43% more blocking criteria, with reference solutions touching 67% more files and 89% more lines than FrontierCode 1.1 in codebases 25% larger. Cognition says the benchmark is far from saturated: the top model, Opus 5.5, scores only 45%, and open-source models, especially western ones, have significant room to improve. The Pareto frontier spans Opus 5.5 at the high end and Luna, Haiku and Sol at the low-cost end, with GPT-6.1 Sol offering strong performance relative to its cost. In 80% of tasks the reference solution differs from the upstream pull request, up from 60% in FrontierCode 1.0, a change Cognition attributes to stricter auditing of prompts, solutions and grading criteria.

## Evidence

Verbatim from https://cognition.com/blog/frontier-code-2.0:

> Recent progress in AI has made software engineers dramatically more productive. However, our experience building and deploying Devin suggests that agentic software engineering remains far from solved. Models struggle to infer user intent, respect unstated constraints, and anticipate long-term consequences of their changes, forcing human intervention.
> 
> Most existing coding benchmarks fail to capture these gaps and tend to be saturated quickly. We are excited to introduce FrontierCode 2.0 , a new generation of our coding benchmark series and our best attempt yet to evaluate user experience.
> 
> In FrontierCode 1.0, elite open-source maintainers crafted rigorous criteria to measure code mergeability. FrontierCode 2.0 builds on this methodology with several key improvements:
> 
> Broader coverage : the tasks are drawn from more repositories and span more categories, including security patches and performance optimizations, to better reflect the real distribution of coding work.
> 
> Higher mergeability standards : grading criteria impose more extensive correctness and design requirements, with added emphasis on thoroughness.

---

Record: https://forck.live/items/28360-frontiercode-2-0
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md