Runtimes and models

Choose a local runtime#

The composer model chip opens Model and reasoning. The basic view presents the available effort levels; the advanced view exposes Runtime, Model, and Intelligence. Runtime choices come from the local runtime library and from the capabilities reported by each installed tool. A model or effort option can be unavailable when its provider does not advertise that combination.

For full setup, open View → Settings → Runtimes & Models. The page describes the local CLI route and provides a runtime library with Install, authenticate, and update actions. Install appears for a missing runtime. An installed runtime can expose a sign-in action or Update. Check all refreshes the visible runtime status. Favorite runtime can be set to Last used or to an available runtime, so new chats follow a predictable route.

Set defaults#

Each available runtime can have its own defaults. Select Edit defaults for <runtime>, then choose Preferred model and Preferred effort from the options reported by that runtime. A missing model catalog leaves model selection unavailable until the provider becomes ready. The composer remains the final place to inspect the active route before a task message is sent.

Read availability states#

The runtime library distinguishes connected, login required, not installed, probing, and degraded states. A login-required runtime needs authentication through its vendor flow. A not-installed runtime needs local installation. Probing and degraded states indicate that the route is not ready for dependable task execution. The composer disables choices that the current runtime cannot support instead of presenting a misleading universal list.

Expect runtime differences#

Permission, delegation, model, effort, resume, and structured tool behavior can differ by runtime. For example, Antigravity and custom runtime routes do not expose delegation controls, and Antigravity does not support Ask as needed. Fast appears only when the selected model advertises that mode. These differences are part of the runtime’s supported capability set and can change as a provider or local installation changes.

Runtime vendor accounts and subscriptions remain with the vendor. Code does not convert them into AI Integrator Chat credits, and Chat’s account-backed model choices are a separate surface. Models, Settings, Usage, and Troubleshooting cover adjacent configuration and status questions.