Troubleshooting and limits

What to do when something doesn't work, and the limits Corral has today.

Check your setup

$ corral doctor
$ corral install --check

corral doctor checks the dependencies, the herdr plugin, the theme, Mirador and its browser, and which terminal it detects, one line each, with what to do about each problem. corral install --check prints the installer's checklist, and corral install repairs the installation.

Common problems

SymptomWhat to do
The ctrl+b shortcuts do nothingThe herdr plugin runs the compiled corral in Corral's folder, and there is no other version to fall back on. corral doctor shows whether the plugin is linked; corral install repairs the installation. In a clone, build the binary with cargo build --release in rs/.
Fresh shows a warning (⚠) about the Wayland clipboardWSLg doesn't have the clipboard protocol Fresh looks for, so Fresh uses X11, and copy and paste work anyway. Corral starts Fresh without WAYLAND_DISPLAY so it doesn't try; if you open it by hand, use env -u WAYLAND_DISPLAY fresh.
The variables pane says "Waiting for the console's session (R or Python)…" or stays emptyThat R doesn't have Corral active. In the console's pane, press ctrl+b m, or run corral_activate() in R.
The script's shortcuts do nothing, or the editor doesn't take the new themeThat editor was opened with an earlier version. Close it with Ctrl+Q and open the layout again with ctrl+b a.
corral script --write says the editor didn't answerThe draft has to be open in the editor. An editor opened before you updated Corral needs to be closed (Ctrl+Q) and opened again.
No completionThe file has to be saved as .R, and Fresh's status bar has to say LSP (on). If the folder isn't trusted, mark it as trusted from the status bar.
Mirador doesn't opencorral doctor shows whether it is running and which browser it uses. corral mirador --url gives the address to open it by hand. If the server doesn't start, its log is in ~/.local/state/corral/mirador.log.
ctrl+b enter says "Nothing to send"Select the code with the mouse (herdr copies it) or copy it with Ctrl+C first.
Claude opens its own R instead of using your consolecorral eval --check should answer with the console. If it fails, switch Corral on in that R with ctrl+b m.
The R console says Ark didn't respondArk's log is in ~/.local/state/corral/ark.log. corral config r_console r goes back to plain R while you look into it.

Known limits