Configuration basics
Choose the models, response preferences, and tool connections EvoX uses, and save lasting working requirements for each project.
Configure everyday options in the desktop app. Connect one working model first, then adjust other options as your work requires. You do not need to fill every setting before starting a task.
Configuration entry points
Open Settings from the application menu, or press ⌘ + , on macOS or Ctrl + , on Windows. Choose the entry for the object you want to change:
| Configuration | Entry and guide |
|---|---|
| Model services, credentials, custom APIs | Settings > AI services; Model service connections |
| Default model, task tiers, summary model | Settings > Model strategy; Model selection and routing |
| Conversation executor | Settings > Kernel; Executors and external agents |
| External coding-tool connections | Settings > My agents; Executors and external agents |
| Theme, language, text size, sound, notifications | Settings > Appearance; Appearance and notifications |
| Collaboration profile, styles, adaptive responses | Settings > Personalization; Profile and reply style |
| Conversation profile, memory, recall | Memory; Memory management |
| Lasting project requirements | Cowork workbench > Project details > Working rules; Project working rules |
| Skills, plugins, manual server connections | Their pages in Extensions; Skills, Plugins, MCP |
| Search channels and credentials | Settings > AI services > Web search; Web search |
| Browser identity and session storage | Settings > Cowork > Browser; Browser settings |
| External messaging accounts and bots | Settings > Connections; Messaging channels |
| Permission rules and simulation | Settings > Permissions; Permissions and approvals |
| Proxies, keep-awake, energy settings | Settings > Advanced; Network and background operation |
| Optional features and diagnostic switches | Settings > Labs; Feature switches |
Project rules belong to the selected project; credentials belong to their connection instance. Check the object before changing it. Success with one project or account does not verify another.
How configuration takes effect
EvoX settings control model selection, task context, presentation, and operation permissions separately. Each applies within its own scope; they do not form one list that overrides everything below it.
- Organization restrictions constrain access. Personal settings, project rules, and task instructions cannot bypass organization restrictions.
- The current task defines its deliverable. State sources, output language, format, and save location in the request. Lasting preferences should not replace these specific requirements.
- Project rules follow project membership. Enabled rules participate in their project's Cowork context. Selecting a different project in the sidebar does not change an existing conversation's membership.
- Memory participates according to its purpose. The conversation profile supplies stable preferences; entries are recalled by relevance. Saving an entry does not mean every answer uses it.
- Expression settings have specific overrides. With the preset's Reply tone scope enabled, its tone takes precedence over the response style in the conversation profile. Enabling “Always reply in this language” makes the profile language override the input language.
- Actions still require authorization. Rules, memory, skills, and connected tools do not replace authorization to access files or perform external actions.
For example, with “Be concise by default” saved as a lasting preference, a task can request “Explain in detail and cite a source for each point.” If the task also specifies a reply language, check “Always reply in this language” for a conflict.
Common configuration options
Build your first setup in this order, then add capabilities as tasks require them. Each linked guide explains its fields and maintenance.
Default model
Connect one service, complete a real request, and choose the default model and account. Start here before configuring other task capabilities.
Connect a model service · Set a default model
Switch models by task difficulty
Leave switching off for a single model. Configure tiers and summarization when tasks need different cost and capability choices, rather than filling every tier before starting.
Configure model tiers and routing
Interface and reading
Choose a readable theme, text size, and interface language, then set sound and notifications for your working environment.
Adjust appearance and notifications
Reply language and style
State one-off output requirements in the task. Save lasting communication preferences in the conversation profile or a style preset. Start with one concrete preference and check its scope.
Configure the collaboration profile and reply style
Project working rules
Add rules for requirements that must remain consistent within a project. Verify them in a conversation belonging to that project instead of maintaining the same requirement in several settings.
Memory and lasting background
Check existing background for accuracy before adding facts worth retaining. Memory supplies context, not project requirements or task authorization.
Manage memory, scope, and recall
Skills and tool connections
Add skills for reusable steps. Connect plugins, MCP, browsers, or messaging when a task needs external data or actions. Configure and verify one capability before adding another.
Skill management · Plugins and app connections · MCP servers
Permissions and approvals
Define files, accounts, and external effects within scope. Rule management and simulation inspect configuration; they do not replace runtime confirmation requests.
Maintain permission rules and inspect approvals
Check that configuration took effect
Change one kind of setting at a time. Reopen its panel to check the saved value, then validate it with a small, bounded task.
| Setting to check | How to check it |
|---|---|
| Model connection and selection | Check account and model, send a request, and inspect the real response |
| Model routing | Use a new conversation; check tier assignments and the summary tier separately |
| Project working rules | Check a specific requirement in the project's Cowork conversation |
| Reply language and style | Use a new conversation to check the language switch, preset, and scope |
| Memory | Inspect the original entry and recall results, then check the background used in the answer |
| Plugin or MCP | Inspect connection and tools; complete a read-only operation first |
For “saved but not applied,” use the panel's retry or service-status action. Saving configuration, applying it in the service, and completing a task are separate outcomes.
Configure standalone Evolver
Standalone Evolver has its own launch arguments and environment settings; these do not replace Desktop configuration. See Standalone Evolver for identity, Hub connectivity, evolution strategy, and runtime directories.