Mirendil lanza Fern 0.1, su primer modelo, con ventana de contexto de 10 millones de tokens

Este es el extracto disponible del feed. Puede estar abreviado o en el idioma original.

Mirendil has released Fern, its first AI model. Mirendil Fern is a from-scratch coding model with a context window of up to 10M tokens. Mirendil explains how that equals about 23 MB of code, or roughly half a million lines. That is a codebase on the scale of Megatron-LM, held in context at once. Fern 0.1 is the first version, built from Mirendil-Base after a short round of post-training. For developers, its like, you load a whole repo, a full training log or days of agent traces at once. TL;DR Size: 0.1 to 0.5T parameters (exact count and active params not disclosed); context up to 10M tokens. Runs on: Hosted early access only; no open weights or quantized builds announced. Performance: Strong long-context retrieval, mid-pack agentic coding versus open-weight models, well behind frontier models. Best: 100% on RULER single-needle retrieval at every length from 32K to 10M tokens (base model). Worst: 6.1% on Terminal Bench 4.0, versus 66.4% for Claude Opus 5.5 in Mirendil’s own table. What is Mirendil Fern? Fern is a language model from Mirendil, an AI R&D lab. Fern is aimed at AI R&D work, not general chat. Mirendil lists 6 target uses: Working across larger codebases Agentic coding that runs commands until tests pass Research code: training loops, data pipelines and evaluations Debugging training runs from long logs and stack traces Reading full agent or training traces end to end Auditing pretraining shards for duplicates, contamination and junk How was Fern built? Fern sits on Mirendil-Base, which Mirendil says one researcher pretrained in 3.5 months. Total compute was under $10M, including experiments, agent token spend and data processing. AI agents wrote over 99% of the code. The researcher chose what to try and when to intervene. Training data came only from public sources: GitHub, public code, web pages and public datasets. Mirendil says it used no distillation, no synthetic data and no licensed data. The code was written from scratch on PyT