Troubleshooting

A remote location shows "Reconnecting" indefinitely

The most likely cause is a server shell that runs each SSH connection in its own temporary Docker container, such as RunCloud's jailed shell /bin/rc-shell. The daemon Jojo starts in one connection ends with that connection's container, so the next connection finds no daemon.

In the RunCloud dashboard, open the server, then System Users, and change the account's shell to /bin/bash.
In Jojo, right-click the location's heading and choose Remove remote location…, then add it again.

A remote location reports that authentication failed

The server refused your SSH key. In a terminal, run ssh -o BatchMode=yes <alias> true; "Permission denied (publickey)" confirms it. Add your public key (the .pub file named by the alias's IdentityFile) to the account's authorized keys, for example in RunCloud under SSH Keys, then choose Reconnect.

The window says the daemon is outdated

The running daemon speaks an older protocol than the window. For your computer, choose Restart daemon in Settings. For a remote location, right-click its heading and choose Upgrade jojod…. Restarting ends that daemon's sessions; Restore sessions brings them back.

Selecting text no longer copies it

Copy on select is off. Turn it on in Settings, or select text and press Ctrl+C.

Copied commands from Claude contain line breaks

Claude Code draws its replies with its own line breaks at the pane's width, so text copied from a reply contains those breaks. Lines that the terminal itself wrapped, such as long shell output, copy as one line. Jojo cannot tell Claude Code's line breaks from intended ones, so copied commands may need their breaks removed by hand.

Hover over it to see the reason. See Right-click menus for the common ones.