Connect models and runtimes

1. Choose an execution path

• Subscription CLI: Claude Code, Codex, Antigravity, Grok, Kimi Code, Cursor, and GitHub Copilot CLI appear in Desktop's supported CLI settings. Copilot uses ACP. Install and sign in to the chosen provider; an Agentlas sign-in does not sign you into that CLI.
• BYOK: choose the provider and model, then enter your own API key in the local credential controls. Confirm the account's quota and tool support.
• Agentlas serving: select an available served model and check your signed-in account's plan and usage. This is model execution, separate from private Agent Cloud package storage.
• Local: configure Ollama, LM Studio, MLX, or the Agentlas local model option available on your host. Start the local service and load a model; MLX requires compatible Apple silicon on macOS.

2. Connect and verify in Desktop

1. Open Settings and the model/runtime controls. Choose the runtime, then follow its Connect, install, or sign-in action. Some providers show a manual setup command.
2. Recheck the connection after sign-in. Installed, authenticated, available, and selected are different states.
3. Choose the model for the conversation or build. If separate orchestrator/worker controls are available, inspect both roles rather than assuming they use the same model.
4. Run a small read-only task and inspect the actual response. A connected badge alone does not prove a provider request succeeded.

3. Set up the independent Terminal

npm install -g agentlas
agentlas setup
agentlas doctor
agentlas roles
agentlas help roles

The published Terminal package requires Node.js 22.13 or newer. setup chooses language, runtime, and permission settings. doctor observes the current installation; provider sign-in and an actual run are still separate checks.

4. Check costs and credentials

A subscription CLI follows that provider's subscription and limits. BYOK follows the API provider's charges. Agentlas serving follows Agentlas usage terms. Local models use your machine's resources. Free Hub agent access does not make model inference free.

Keep keys in the host's credential controls. Do not paste them into a build brief, public package, chat example, or Cloud upload. An unavailable model must be resolved or explicitly replaced; inspect the selected runtime after reconnecting.