FlowManner
Chat
Sign InGet Started
Flowmanner
Menu
  • Chat
  • Agents
  • Pricing
  • Docs
  • About
Products
  • Workflows
  • Templates
  • Changelog
  • Missions
Resources
  • Blog
  • API Reference
More
  • Careers
  • Contact
  • Security
  • Start
    • Quickstart
    • Your First Mission
    • Your First Eval
  • How-to
    • Connect Your Own Keys (BYOK)
    • Switch Models Per Task
    • Publish a Template
    • Run Evaluations
    • Chat with Artifacts & Previews
    • Automate via the API
    • Webhooks & Triggers
  • Concepts
    • Glossary
    • Execution Model
    • Models & Routing
    • Sandboxes & Previews
    • Memory & Privacy
    • Trust Model
  • Reference
    • Reference · API
      • Authentication
      • Missions & Runs
      • Chat & Sandboxes
      • Blueprints, Graphs & Templates
      • Evaluations & Feedback
      • Marketplace & Community
      • Files & Exports
      • Integrations & Webhooks
      • Agents & Orchestration
      • Auth, Workspaces & Billing
      • Memory & Knowledge
      • Notifications
      • Platform Services
    • Errors
    • Models
    • Limits

Switch Models Per Task

How assigned vs default model selection works, and what suffix matching does to your ids.

  1. Per mission, set the assigned model when creating/updating it (assigned_model parameter, app/services/mission_service.py:239). Without one, your default model resolution applies.
  2. Flowmanner matches keys tolerantly: if a BYOK key declares deepseek-chat/deepseek-v4-flash and you request a suffix match (deepseek-v4-flash), the key still wins the route (llm_router.py:858-870).
  3. The wire spelling follows the key: when routing matched only by suffix, Flowmanner sends the key's declared spelling upstream — strict gateways reject spellings they did not declare (llm_router.py:512-524). You keep seeing your original id in results.
  4. Reasoning-style models spend part of their window on internal reasoning; size budgets accordingly (Models).

Last updated 2026-08-25 (git-derived)