Troubleshooting
First identify the affected surface: startup, Chat, Cowork, Code, browser, plugin, scheduled task, Sites, or file preview. Preserve the original error, time, and version. Do not repeatedly retry a high-impact action while state is unknown.
A page or local link does not open
- Confirm the development server is still running and use the port from its current output.
localhost:3000and127.0.0.1:3105are different services; do not turn a temporary preview port into a permanent product link.- For a blank page, inspect build errors and the browser console, then reload once.
- If the port is occupied, stop the stale process or use a new port and update the link.
Work appears stuck
Check for an approval, file picker, or login prompt; inspect the latest tool state and persistent notice; run one low-risk terminal command in Code; stop before narrowing the request; and record unfinished steps before restarting so external effects are not repeated.
Browser problems
- Check whether the current version and operating system provide the browser pane, then read the unavailable reason shown in the UI.
- Check allowed-site scope when an external address is rejected.
- Verify whether the browser uses shared, session, or temporary storage.
- If the page is visible but input fails, inspect site permissions and the input actions available in the current conversation instead of bypassing the permission boundary.
- Missing console or network detail can mean that the current version does not expose those tools; it is not proof that no error exists.
Everyday Chrome will not connect
- Open Settings > Cowork > Browser and confirm that Take over my everyday Chrome is selected.
- Check that Playwright Extension is installed, then choose Re-check in Settings.
- The first browser task requires one Allow click on Chrome's connection page; without it, the task continues waiting.
- If silent connection was turned off but old access is still a concern, regenerate the token in the extension and restart the related task.
Web search is unavailable
- Open Settings > AI services > Web search and confirm that the active channel is not labelled Not ready.
- EvoMap search reuses the account key; Tavily needs an API key; Google needs an API key and search engine ID.
- For a rejected key, rate limit, exhausted quota, timeout, or unavailable service, verify provider status and switch to another configured channel.
- Run the search again after switching and confirm that the tool result contains new clickable sources.
Attach an app fails
- Confirm that the target window is still open, then choose it again from
@ Appin the composer. - macOS requires version 14 or later and Screen Recording permission; EvoX may need a restart after permission is granted.
- Read can also require Accessibility permission. Some applications expose no readable text, so fall back to View.
- A protected window will keep rejecting capture. Use a screenshot or choose another window instead of retrying indefinitely.
- Operate appears only when the current connection supports it. A missing Operate button does not disable View or Read.
Plugin or MCP problems
Use /mcp to check installation, enabled state, and connection. Test the plugin connection and credentials. Built-in image and speech plugins require provider configuration. If an external write has unknown status, verify it in the target service before retrying.
A scheduled task did not run
Confirm it is enabled and its next run and time zone are correct. Local runs need the computer on, EvoX running, and the directory present. Review model, plugin, file, and network access in the latest run. Scheduled tasks do not create worktrees automatically; if a Code schedule uses an EvoX-managed isolated task worktree, disable the schedule and preserve its changes before cleaning that worktree up in Code mode.
A file is missing or will not preview
Artifacts require a real file or explicit preview-tool result; prose alone does not create one. Check the output path, extension, and active version. Re-render office and PDF output to inspect fonts and pagination. For blank HTML, inspect relative assets, script errors, and machine-only absolute paths.
Diagnostics and logs
Advanced settings include daemon status, diagnostics, and maintenance. A useful report contains the EvoX version and operating system, timestamp and mode, redacted error and logs, expected and actual behavior, reproduction reliability, and attempted recovery.
Remove secrets, tokens, customer data, and sensitive local paths before sharing logs. /feedback can optionally include the current conversation.
EvoX Docs · Features · Reference