Executors and external agents
A session executor determines which runtime executes an EvoX conversation. An external-agent connection exposes EvoX capabilities to another agent tool. Their entry points, scope, and verification are different.
Choose the object to configure
| Goal | Entry point | What it does not do |
|---|---|---|
| Choose an EvoX session runtime | Settings > Kernel | Install missing runtimes or provision model accounts |
| Connect EvoX to an external agent | Settings > My agents (AI coding tool connections) | Import external conversations or replace host authorization |
| Define a specialist for a subtask | Subagents in Extensions | Change the default session executor |
Model services determine the model requested; executors run tasks. Changing a model does not change the executor.
Detect and select an executor
- Open Kernel in Settings and wait for conversation-executor detection.
- Check availability, capabilities, limitations, and billing for the target executor.
- Resolve dependency or readiness errors, then recheck.
- Select an available executor in the default-selection area. It appears when alternative executors exist or a non-native choice is saved.
- Create a conversation with a small task and check the actual executor and result.
Native and external executors have separate capabilities and governance boundaries. Names do not prove full tool support. Local selection cannot bypass organization restrictions.
A failed detection shows an error and retains previous results or the native entry. An old list does not prove an external runtime remains available. After an initial run fails, resolve the cause and recheck before retrying.
Connect an external agent
- Open Settings > My agents and choose the project directory.
- Check detected hosts and installation status.
- Read the project or user scopes supported by that host, select the scope, and connect.
- Check connection and lifecycle-skill status; run a small, bounded task in the external host.
- Verify the selected project and connection, rather than relying on another project's result.
Project scope connects the selected project. Claude Code also has an All projects for this user entry for the current OS user. Codex lifecycle connections are managed in the selected project; do not apply the Claude Code user-level flow to them. Check host support before installing, updating, or uninstalling its connection and lifecycle skills. Use Import experience to migrate external conversation material; migration is separate from connection.
Disconnect and recover
Check the host, project, and scope before disconnecting, and finish tasks that depend on the connection. Use the host entry’s disconnect or uninstall action and inspect the resulting state. For a Claude Code user-level connection, follow the project-removal notice; disconnecting one project does not prove every project is disconnected. Disconnection does not delete the project or external host history. Check the project, host detection, and status before resetting unrelated model services.
See Subagents for specialist definitions and usage, and Model selection and routing for model assignments.