Code and tools
Does the model need to work on software?
Start here for coding, terminal tasks, tool calls, and agent workflows where the model has to do more than answer a short prompt.
See this starting pointAI Resources
A practical map for comparing model choices by the job in front of you, where they run, what they can see, and how hard it would be to switch later.
Start with the guidance, then use the cards below to open LifeHubber notes and original sources before trusting context length, licenses, pricing, privacy, moderation, access, or terms.
Choose by situation
These paths organize source-linked Resources by the question they can help you investigate. They do not rank products or cover every option.
Code and tools
Start here for coding, terminal tasks, tool calls, and agent workflows where the model has to do more than answer a short prompt.
See this starting pointLong inputs
Use this path when context length, multi-step reasoning, or keeping track of a larger body of work is the main constraint.
See this starting pointLocal and smaller hardware
Compare smaller models, local formats, and hardware paths when on-device tests or a fallback route matter.
See this starting pointMedia and documents
Use this path when the input or output is not only text, or when document handling and moderation constraints shape the choice.
See this starting pointSpecialist work
Start here for forecasting, robotics, Earth observation, translation, and other tasks where domain evidence matters more than broad chat claims.
See this starting pointCoverage and freshness
These groups are selective starting points, not a complete directory. The date reflects the newest included Resource’s LifeHubber added date, not a recheck of every linked source. Check the original source for current setup, terms, limits, privacy, access, costs, and behaviour.
Fresh in this topic
Recently added Resources from the groups below.
Coding and agentic work
Use this group when the model choice affects coding agents, terminal work, tool use, or software projects that need to be debugged outside one chat app.
deepreinforce-ai/Ornith-1.0
Ornith spans checkpoints from 9B to 397B, with GGUF and FP8 variants, so the coding-model choice can account for both scale and a realistic serving format.
CohereLabs/North-Mini-Code-1.0
North Mini Code activates 3B of its 30B parameters and targets terminal work, putting the active-compute tradeoff directly into an agentic coding decision.
JetBrains/mellum-2
Mellum2 pairs a software-engineering focus with 131K context notes and several checkpoints, a useful combination when repository length may rule out a smaller coding model.
zai-org/GLM-5.2
GLM-5.2 brings 1M-context positioning and local-serving paths to long-horizon coding, putting deployment alongside the question of whether the project can stay in context.
moonshotai/Kimi-K2.7-Code
Kimi-K2.7-Code keeps reasoning across tool calls and offers an INT4 route, exposing the choice between multi-step execution needs and a lower-bit serving option.
moonshotai/Kimi-K2.6
Kimi-K2.6 covers visual input as well as long-horizon coding and tool use, adding a comparison point for work that moves between screenshots, code, and commands.
Qwen/Qwen3.6-35B-A3B
Qwen3.6-35B-A3B combines open weights, multimodal input, tool use, and long context, bringing local weight access into the software-workflow decision.
Qwen/Qwen-AgentWorld-35B-A3B
Qwen-AgentWorld supplies simulated MCP, terminal, web, Android, and OS environments, shifting the question from code completion to behaviour inside interactive software settings.
meituan-longcat/LongCat-2.0
LongCat 2.0 combines coding, long-context, and agent-oriented work with base, FP8, and INT8 model pages, keeping both the software task and serving format in the comparison.
Long context and reasoning
Use this group when long documents, larger codebases, or multi-step work are the comparison problem. Check how each source describes context, thinking modes, tool use, and access paths.
MiniMax/MiniMax-M3
MiniMax-M3 puts 1M context, multimodal input, and separate thinking modes in one model, clarifying the tradeoff between a very large workspace and controllable reasoning behaviour.
deepseek-ai/deepseek-v4
DeepSeek-V4 brings long-context reasoning, coding, and agentic evaluation into one family, giving several multi-step workloads a shared-model comparison point.
tencent/Hy3
At 295B parameters with public weights and serving notes, Hy3 makes the infrastructure cost of a large deployable reasoning model part of the choice.
stepfun-ai/Step-3.7-Flash
Step-3.7-Flash pairs 256K context with BF16, FP8, NVFP4, and GGUF variants, letting context requirements be weighed against different serving footprints.
CohereLabs/command-a-plus-05-2026-w4a4
Command A+ W4A4 applies low-bit quantization to a long-context, multimodal tool-use model, bringing hardware requirements into a broader agent-workload decision.
arcee-ai/trinity-large-thinking
Trinity-Large-Thinking centres coherent multi-turn behaviour, constrained instructions, and clean tool use for long interactions that need the model to follow the same task and rules across multiple turns.
inclusionAI/Ling-2.6-1T
Ling-2.6-1T makes the scale decision explicit: demanding multi-step reasoning comes with trillion-parameter weights, multi-GPU serving notes, or a hosted access route.
Local and fallback paths
Open this group when fallback, local tests, edge deployment, or smaller hardware needs matter more than chasing the largest hosted model.
google/gemma-4
Gemma 4’s 12B dense checkpoint handles visual and audio input, covering local fallback jobs that need more than text without a separate encoder stack.
LiquidAI/LFM2.5-230M
At 230M parameters with GGUF, ONNX, and MLX variants, LFM2.5-230M offers a compact route for testing extraction or lightweight agent work on-device.
LiquidAI/LFM2.5-350M
The 350M checkpoint provides a direct step beyond the family’s 230M option, helping readers judge how much on-device model capacity their task needs before moving to billion-parameter hardware.
LiquidAI/LFM2.5-8B-A1B
LFM2.5-8B-A1B activates 1.5B of its 8.3B parameters, putting the balance between tool-use capacity and active on-device compute in view.
OpenBMB/MiniCPM5-1B
MiniCPM5-1B combines a 1B-class footprint with 131K context and several local runtimes, exposing the tradeoff between a compact assistant and long inputs.
Zyphra/ZAYA1-8B
ZAYA1-8B activates 760M of 8.4B parameters, making reasoning capacity versus per-token activation the central local-model tradeoff.
Multimodal, document, and moderation
Use this group when a model has to handle images, video, OCR, document parsing, or moderation checks. The data path and source constraints matter as much as the feature list.
thinkingmachines/Inkling
Inkling accepts text, images, and audio with adjustable reasoning effort, making cross-media input and reasoning control the comparison.
nvidia/Nemotron-3.5-Content-Safety
Nemotron 3.5 Content Safety separates moderation into its own model layer, with prompt, image, and response checks against standard or custom policies.
OpenMOSS-Team/moss-vl
MOSS-VL separates continuous video, offline multimodal work, and further training across Realtime, Instruct, and Base checkpoints, making the intended video workflow easier to choose.
google-deepmind/tips
TIPS is an encoder rather than a full conversational model, providing reusable image-text and spatial representations as an upstream layer.
deepseek-ai/DeepSeek-OCR-2
DeepSeek-OCR-2 targets image and PDF conversion to Markdown with dynamic resolution, putting document extraction ahead of general visual conversation.
zai-org/GLM-OCR
GLM-OCR focuses the choice on complex document parsing and deployment efficiency, rather than asking a general multimodal model to handle structured pages.
baidu/Unlimited-OCR
Unlimited-OCR handles long documents in one shot and supports batch image and PDF inference, addressing workloads that may strain page-by-page OCR.
bytedance-research/Lance
Lance covers image and video understanding, generation, and editing in one workflow; its stated 40GB VRAM requirement keeps the hardware tradeoff visible.
Specialist domains
These entries are reminders to compare the task shape, domain evidence, data type, and deployment assumptions before borrowing a specialist model into a wider workflow.
google-research/timesfm
TimesFM brings forecast-specific checkpoints and a supported BigQuery ML path to time-series work, rather than relying on general language reasoning.
nvidia/gr00t-n17
Isaac GR00T N1.7 connects perception and instructions to robot actions through a vision-language-action model and LeRobot-format fine-tuning workflow.
allenai/olmoearth
OLMoEarth is trained around satellite imagery, band extraction, and planetary-scale mapping, matching Earth-observation work that needs domain-specific representations.
AngelSlim/Hy-MT1.5-1.8B-1.25bit
Hy-MT1.5 combines 33-language offline translation with a 1.25-bit GGUF route, bringing multilingual coverage into an Android or similarly constrained device decision.
LiquidAI/lfm-jp
LFM JP groups Japanese-tuned text, tool-use, structured-output, transcription, speech-generation, and speech-to-speech models for workflows where Japanese language coverage is the specialist requirement.
Also in AI
Keep the thread going with AI Guides for decision habits for messy AI choices, AI Access for free and low-cost ways to compare AI model access, AI Ballot for a clearer view of what readers are leaning toward.