Skip to main content
This is preview documentation. The official release is not yet available.
Hosted configuration has three layers: Host connectivity/capacity, provider parameters in Runtime Profiles, and Agent instructions/model overrides. Start with Runtime Host installation.

​
Connection settings

This exposes the selected providers. Their CLIs must already be installed, authenticated and executable. The default file is ~/.agentscope/runtime-host/config.json. Its controlPlane, tenant, namespace, pool, capacity, workspaceRoot, stateRoot and providers fields describe the connection. credential is private identity material. Check active work before changing a running Host, then restart and probe again.

​
Agent versus Profile

Agent system defines responsibilities and model provides an optional override. A nonempty Agent model takes precedence over Profile model. When both are empty, the provider uses its own default. runtimeProfileId selects provider configuration; runtimePoolId selects the Host pool. Most authors select a discovered Runtime in the console while administrators maintain Profiles and pools. Raising Host capacity does not increase model quota or remove Agent/task policy limits.

​
Provider parameters

These fields belong to Runtime Profile configuration, not to connect and not to a universal provider schema. Model identifiers, reasoning levels and account availability depend on the installed provider. Saving a Profile does not install models, authenticate accounts or grant external permissions.

​
Definition conflicts

Host translates portable instructions, skills and supported MCP/tool definitions into provider configuration. Unsupported requested capabilities fail before execution. See the provider matrix. Custom arguments are argv entries. Reserved arguments controlling workspace, model, output protocol, MCP and permissions cannot be freely overridden. Configure Codex native tools through Profile sandbox/approval settings; Managed built-in tool policies do not transfer to it.