Commands
EvoX actions can be reached through buttons, the app menu, command surfaces, keyboard shortcuts, and slash commands. This page covers command access and scope; see Slash commands for the / inventory.
View and change key bindings
Open Settings > Keyboard shortcuts or use /keybindings in Code. Bindings can differ by operating system and user configuration, so one shortcut should not be documented as universal.
Search by action name. Resolve conflicts by preserving global navigation and stop actions before lower-frequency commands.
Command areas
| Area | Available actions | Notes |
|---|---|---|
| Global navigation | New conversation, open project, search chats, open settings | Switches the main work surface. |
| Conversation | Send, stop, retry, copy, compact context, feedback | Some actions require existing context. |
| Code | Files, terminal, browser, preview, diff, and GitHub views | Depends on workspace and repository state. |
| Permissions | Ask, smart approval, accept edits, automatic, full access | Changes how later tools request approval. |
| Projects | Create, rename, pin, archive, move chats, attach folders | Organization does not grant new access. |
| Scheduled tasks | Create, run now, pause, edit, open last run, delete | Local runs depend on the app and project directory. |
| Artifacts | Open preview, source view, export, download, and versions | Available actions depend on artifact type and provenance. |
Availability
EvoX hides, disables, or annotates commands based on context. Workspace commands need a workspace; conversation recovery needs existing history; browser controls depend on the host; plugin commands depend on connection state. Some commands are immediate desktop actions while others hand a structured request to EvoX.
Safety commands
Stop, cancel, and reject should stay easy to reach. When a window is wrong, publication state is unknown, or a retry may duplicate spending, stop and read the actual state before issuing the command again.
EvoX Docs · Features · Reference