Troubleshooting

Reference

Troubleshooting

Use Red's focused checks to separate installation, configuration, runtime asset, language-server, Agent, keyboard, and recovery problems.

Start with the narrow check

ProblemFirst check
Red doesn't start or bundled tools are missingred --self-check
Configuration fails to loadred --check-config
A plugin or theme looks stale or missingred --runtime-files
Codex can't start from Redred --agent-check --strict
A modified Enter shortcut doesn't arrivered keys
A language server doesn't respondConfirm its executable is on PATH, then reopen a matching file
A previous editor stopped with unsaved workred --resume

Read messages and logs

Press Space m or run :messages to browse editor notifications, command output, and recent errors. Red writes red.log in its configuration directory by default. Relative log_file paths are resolved from that directory.

Fix common problems

  • Command not found after installation: open a new terminal or add the install directory printed by the installer to PATH.
  • Language tools are empty: install the configured server executable. Buffer-word completion still works without a server.
  • A bundled theme or plugin behaves like an older copy: a file in your configuration directory may be shadowing the embedded asset. Check red --runtime-files, then remove or replace the ejected copy.
  • An Agent prompt failed to start: update Codex, run codex login, then retry the preserved prompt.
  • Shift+Enter behaves like Enter: use Ctrl+J for a newline and run red keys to see what the terminal sends.
  • A dirty file changed on disk: run :diffdisk; use :e!, :w file, or :w! only after choosing which version to keep.
  • Detach isn't available on Windows: use red --resume for crash recovery. Live detach and attach currently require macOS or Linux.

Report a reproducible problem

Include your Red version, operating system, terminal, the smallest reproduction, and the relevant focused-check output. Remove private paths, source, prompts, and credentials before sharing logs.

Open a GitHub issue