Capabilities
Capability pages explain the tools EvoX can use to complete work and how availability depends on permissions, plugins, the operating system, and the current mode.
Confirmed
| Capability | Verified product form |
|---|---|
| Browser | Browser pane, tabs, address bar, site permissions, development servers, and dedicated or everyday-Chrome identities. |
| Web search | EvoMap, Tavily, and Google channels in Settings, with source results in the conversation. |
| Attach an app | Select one open window with @ App, recapture it at send time, and use View, Read, or connection-dependent in-window Operate. |
| Use everyday Chrome | Reuse everyday Chrome login state through Playwright Extension and manage one-time authorization. |
| Voice | Composer dictation plus TTS, cloning, and transcription through the speech plugin. |
| Plugins | Directory, installed management, MCP, enable/disable, connection, and testing. |
| Image generation | Built-in provider-configured generation and editing plugin. |
| Image input | Image attachments as visual context. |
| File handling | Attachments, project folders, generated files, preview, versions, and export. |
Implemented in source but not currently exposed
- Computer use: the source retains real desktop-control and safety-checking paths, but the current build defaults them off and offers no regular-user entry to enable them. The browser and plugins remain scoped to their own documented surfaces.
Permission model
Availability depends on the current mode, operating system, installed plugins, account connections, and policy. A visible entry does not grant every action. External writes, publishing, deletion, spending, and sensitive data can still require approval.
EvoX Docs · Features · Capabilities