Automatic vs Manual AI Model Selection: Which Should You Use?

Direct answer: Start with automatic selection when your problem is model-choice fatigue. Switch to manual selection when provider identity, a specific capability, predictable behavior, or a controlled comparison matters more than convenience.

Fact-checked September 23, 2026. This page owns the Auto-versus-manual decision. It complements the automatic model selection pillar and exact Magicdoor Auto policy.

The short decision table

Choose Auto to remove repeated work

Magicdoor Auto chooses among DeepSeek V4.1 Flash, GPT-6 Luna, GPT-6.1 Sol, and Claude Opus 5.5. It is useful when one conversation moves from a rewrite to Python analysis, then to a recommendation, then back to formatting. The previous answer model does not lock the next turn, although saved file or container history can constrain compatible routes.

Auto does not always pick the best model. It applies the current quality-first-v7 policy under uncertainty.

Choose manually for control

Manual model selection bypasses Jev. Use it when you need a provider outside Auto's pool, want consistent behavior across repeated work, already know the required capability, want a fixed model comparison, or prefer direct cost control. The models page shows the wider lineup, and the model selection guide covers general task fit.

Worked choices

• Mixed daily work: Auto can route routine expression, execution, and judgment independently.
• Provider-specific review: choose Claude, GPT, or another named model manually.
• Strict cost exploration: choose manually because Auto can fail closed to Sol for incompatible effective context or Opus 5.5 for compatible text.
• Uncertain capability: Auto keeps code execution, PDFs, non-image files, and hard OpenAI requirements on Luna or Sol according to Jev signals; effective saved history can prevent an Opus handoff. Selecting Sol does not guarantee code-interpreter use.

Cost and privacy tradeoffs

Auto is not a priced model. Usage is billed against each concrete DeepSeek, Luna, Sol, or Opus answer-model attempt. If provider recovery runs, separately metered attempts are recorded separately. Jev routing usage is operational telemetry, not added to answer-model usage.

Manual choices bypass the Auto routing payload. Auto sends up to six recent user/assistant text messages plus the latest request and a capability flag, capped at 16,000 UTF-8 bytes. Files, file URLs, tool payloads, system messages, separate reasoning, and think blocks are excluded, but user text can contain sensitive strings or URLs. This is not full redaction.

A practical default

1. Use Auto for mixed work.
2. Check the concrete answer model when behavior or cost matters.
3. Switch manually for provider-specific work, controlled comparisons, or strict cost choices.

Compare the categories directly: OpenRouter Auto vs Magicdoor Auto, ChatGPT automatic selection vs Magicdoor Auto, the published router ranking methodology, and when a multi-model workspace beats separate subscriptions.

Try Experimental Auto in chat

FAQ

Should I use automatic or manual AI model selection?

Use automatic selection when a conversation changes task type and you do not want to choose a model for every message. Choose manually when you need a specific provider, behavior, capability, or repeatable comparison.

Does manual selection bypass Magicdoor Auto routing?

Yes. Selecting a model manually bypasses Jev and uses the chosen model path, subject to its normal capability and access rules.

Is Auto always cheaper than choosing manually?

No. Auto may choose economical DeepSeek or Luna routes, but substantive compatible text can use Opus 5.5, while OpenAI-required work or routing failures can use Sol. Usage is billed against each concrete answer-model attempt, including separately metered recovery attempts.

Sources

Accessed September 23, 2026.

• Current Magicdoor registry, routing policy, router, capability checks, and answer-model accounting.
• TypeSafe Noul documentation for probability and threshold semantics.