# Modeless: stop picking models

> Modeless picks the model for your coding agent. Auto routes each session to the model it needs; Fusion combines several models into one answer. Model cost + 5%.

Source: https://modeless-web.vercel.app

Stop picking models. Go modeless.

A new model takes the lead every few weeks, and keeping up is nobody's job. Point the agent you already use at Modeless and it makes that choice for you while you work.

No credit card · OpenAI-compatible · Live in 60 seconds. [Get started](https://console.modeless.ai/sign-up) · [Set up your agent](https://modeless-web.vercel.app/integrations)

## Results

- **Auto**: 30% lower cost per task than Claude Opus 5.5 (SWE Pro, DeepSWE v1.1, Terminal-Bench 4.0)
- **Fusion**: 10% higher score than Claude Opus 5.5 (DRACO)
- **Fusion**: 50% lower cost per task than Claude Opus 5.5 (DRACO)

## Two ways to use many models

- **[Auto](https://modeless-web.vercel.app/auto)** (`model: "auto"`): One model string picks the right model for every request, so you stop paying frontier prices for easy work. Best for long coding-agent sessions where most turns are routine.
- **[Fusion](https://modeless-web.vercel.app/fusion)** (`model: "fusion"`): Several models answer in parallel. One model reads them all and writes the reply. Best for design reviews, hard questions and plans, where the answer has to be right.

## Works in the agent you already use

Claude Code, Codex CLI, OpenCode, Cline and Cursor. See [setup guides](https://modeless-web.vercel.app/integrations).

## Why this exists

A new model takes the lead every few weeks, on one benchmark, for one kind of task. Checking which one to use is a job nobody was hired to do. So most people pick the strongest model and pay for it on every turn, including the turns where it reads a file or lists a directory. Modeless makes that choice for you while the work goes on.

## Pricing

Model cost + 5%. Example: $1.00 model cost + $0.05 Modeless fee = $1.05. Pay as you go. See [pricing](https://modeless-web.vercel.app/pricing).

## Questions

### Is Modeless right for every task?

No. If every request needs the strongest model available, call that model directly. Auto pays off on long agent sessions where most of the work is routine; Fusion pays off when one answer has to be right and you can wait a little longer for it. Test on your own workload before you switch.

### How should I evaluate it?

Take a real workload with a clear success criterion: tests that pass, a reviewer who signs off. Run it on your current model and on Modeless, then compare quality, latency and cost per finished task, not per token.

### Will Auto switch models mid-conversation? Will my cache break?

Auto changes model at most once per session, when it decides the task needs a stronger model. That one switch starts a new prompt cache; every turn after it stays on the same model and the cache stays warm. The one exception is a model failing before it answers: that request falls back to another model.

### What happens if a model fails after streaming starts?

Modeless only moves to another model before the first byte of a reply reaches you. Once a reply has started, it never splices a second model's output into it; you get the error in your protocol's own format instead.