Skip to content

Tenstorrent: allowlist MistralForCausalLM and gate it on-device (BACKEND-TENSTORRENT-MISTRAL) #670

Description

@localai-bot

What

MistralForCausalLM is not in the Tenstorrent platform allowlist, so a Mistral checkpoint falls through to CPU on a Blackhole board even though every op it needs is registered.

Tracks the work in PR #431: add the architecture to TenstorrentPlatform::supports_model_architecture, and gate it with an on-device near-tie parity run against committed device goldens.

Why it needs an issue

It didn't have one — the row, its spec and its claim all landed referencing PR #354, which is a merged PR rather than an issue. AGENTS.md requires an open issue linked in three places that agree: the issue table in .agents/roadmap_v1.md, the row's spec, and the PR body. This issue is that link.

Noted while reviewing #431: the whole BACKEND-TENSTORRENT lineage has this gap, so sibling rows likely want the same treatment rather than only this one.

Scope

Oracle

The device goldens are teacher-forced by transformers, not vLLM — vLLM has no Tenstorrent backend at all. That is now the sanctioned path under AGENTS.md "When vLLM has no implementation", with transformers and tt-forge both in the oracle registry. The spec and the in-code comments must name the oracle that actually produced the committed files.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions