3.14 Configuration guide
For your first setup, configure a model under Settings → Models, complete an ordinary conversation, then add the knowledge, skills and tools your colleagues need. After that, adjust only the settings relevant to the work at hand.
1. Find the right settings
| What to change | Where to go | Guide |
|---|---|---|
| Language, theme and developer tools | Settings → General | Change the relevant preference; developer tools enable features such as reviewing file changes |
| Models and API keys | Settings → Models | Configure models and credentials |
| Local working directory | Settings → Execution locations | Choose the working directory; see Runtime configuration and data locations for local and container paths |
| MCP, native plugins and runtime capabilities | Settings → Connections and runtime | Use native runtime capabilities |
| Runtime mode for new sessions | Settings → Agent presets | Choose a mode and execution method; existing sessions retain their preset |
| A colleague's role, knowledge, skills and tool permissions | Colleagues → Open the colleague | Create and manage AI colleagues |
| Skills, connections and extension inventory | Capabilities | Manage capabilities and connections |
| Automatic experience and memory updates | Settings → Auto Dream | Automatically organize work experience |
Use Component status to investigate loading or runtime problems. For plugin installation and configuration, start with Connections and runtime.
2. Save connections and runtime settings
Enter model, credential or connection details on the relevant page, then use its save, connect or enable action. If a host restart is required, wait for active work to finish first.
Installed, enabled and connected are different states. An installed plugin may still need its components enabled, credentials configured or local dependencies prepared. Inspect the actual status of the item you configured; saving successfully does not establish that a call has succeeded.
3. Assign capabilities and permissions to colleagues
Open the colleague's profile and check its role, knowledge scope, skills and available tools. When an edit requires the colleague to be paused, pause it first, save the change, then return it to work.
A Skill describes how to work. An MCP connection provides tools. Business authorization determines which tools and resources a colleague can use and when approval is required. Installing or enabling a plugin does not expand colleague permissions. See Skills, knowledge, connections and authorization.
4. Verify with a small task
Verify an ordinary conversation first, then assign the target colleague a small task with a clear scope. For example, ask it to read a specified document, summarize three points and name the source. Inspect tool results, items requiring your attention and the final deliverable in the task record.
If ordinary conversations work but a colleague's task fails, check that colleague's model, runtime preset, tool permissions and error record. For connection failures, check the service address, credentials and host network first. See Troubleshooting for more help.
Teloa manages business and colleague configuration. Models, native tools and runtime environments are saved through the Harness configuration services. Everyday setup happens on the corresponding product pages; developers can read Business capabilities and execution engine boundaries.