Supported models

Model	Checkpoints	Inputs
Gemma 4	google/gemma-4-E2B-it, -E4B-it, -12B-it, -31B-it	text, images
Intern-Decision	internlm/Intern-Decision-4B, -2B, -0.8B	text
OneJev	OmniJev/OneJev1.6-0.8B, -4B, -9B, -27B	text, images, video
Open-Jev	ZefanCai/Open-Jev-2B, -9B	text
Qwen3.5	Qwen/Qwen3.5-0.8B, -2B, -4B, -9B, -27B	text, images
torchcast	torchcast-ai/torchcast-decision-27b	text

Any chat model on Qwen3.5 or Gemma 4 serves as it is; their rows name the official ones. The other rows are decision models, each read the way its release reads it, and all of them come with Flide.

Flide picks the family from the checkpoint. A checkpoint that names its family in decision_config.json gets that family, a checkpoint another family recognizes gets that one, and any other chat model is read at the first token of its reply. --format picks one by name, and flide formats lists the installed ones.

A new family is one folder in plugins/ and one line in pyproject.toml; a separate package can also join through the flide.formats entry point. Add a model family walks through one.