Data as of September 28, 2026 · How the score is built
LFG-3
Decision readingLFG-3 is tracked, but not publicly ranked yet. The profile exposes 0 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Released Aug 6, 2026 — see all recent releases
LFG-3 will be repriced, updated or retired. Get each notice with its source and date. Follow model changes
Share or export
Voice benchmark evidence
VoiceBench is an owner-defined voice evaluation. Its result stays separate from BenchLM's weighted text-model ranking.
Lineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
Base entry
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not publishedglenn2 model documentation
- Context window
- N/A
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not sourced yet
- Availability
- Published weights or implementation resources are linked from the model card.
- Cloud regions
- Not tracked yet
- Lifecycle
- Current
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing recordglenn2 model documentation
- Self-host
- Open weights available; hardware estimate not sourced
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track LFG-3, but no weighted text-model benchmark result is published on the site yet. This page shows the metadata and separate protocol evidence we can verify now; a BenchLM score will appear only if compatible public evaluations land.
LFG-3 is a open weight model with a N/A context window. No explicit reasoning mode is documented in this profile.
Published weights or implementation resources are linked from the model card.
LFG-3 is tracked because it appears in voicebench. Voice-protocol results remain separate from BenchLM's weighted text-model ranking.
The profile has no source-displayable benchmark row yet.
Last updated September 28, 2026. Runtime fields remain blank until a sourced snapshot exists.
Deployment options
Self-host and provider-specific paths stay separate from benchmark evidence so operating constraints are visible before a score becomes the whole decision.
Published weights are available, but BenchLM does not yet have a sourced parameter and VRAM profile for this exact model. Hardware cost estimates stay unavailable until that sizing record is complete.
Estimate VRAM from known parametersQuestions
How does LFG-3 perform overall in AI benchmarks?
LFG-3 does not have any source-displayable benchmark rows yet, so this profile does not assign a public score or rank. Documented specifications remain visible, while score-led charts and claims stay unavailable until a published evaluation can be attached to the exact model.
Is LFG-3 open source?
LFG-3 is an open-weight model from glenn2. Its weights can be downloaded for local or hosted deployment, subject to the published license. Open weight does not automatically mean open source: training data and training code may remain private, and commercial restrictions can still apply.
Does LFG-3 have full benchmark coverage on BenchLM?
No. LFG-3 currently has 0 source-displayable rows across 486 tracked benchmark slots. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of LFG-3?
LFG-3 has a reported context window of N/A in the exact-model catalog record. The value stays visible, but the profile marks its source link as unavailable instead of presenting it as directly documented. Maximum output length remains separate because providers often publish a different limit.