Skip to content
RightNow

Terminal Support

RightNow depends on the terminal for color, keyboard input, mouse input, clipboard access, and fullscreen display. Start with Doctor when one of these behaves unexpectedly.

Run Doctor

Run /doctor inside the TUI to include live session checks. If the TUI cannot start, run the shell command:

powershell
rightnow doctor

Doctor can report issues or recommendations and still exit successfully. Read the findings and suggested fixes before treating the exit code as a clean report.

For the same report as JSON:

powershell
rightnow doctor --json

Detected terminals

RightNow detects terminal names from environment variables.

Detected names include Windows Terminal, Apple Terminal, Ghostty, iTerm2, foot, VTE, VS Code-family terminals, and JetBrains terminals.

Terminal detection can be incomplete in tmux or over SSH.

The tmux global environment can describe the first attached client instead of the current terminal.

Apply a tmux fix

Doctor writes one named tmux fix at a time to the persistent configuration; it does not reload the live tmux server.

List the fixes available for the detected setup:

powershell
rightnow doctor fix

Apply the clipboard fix only when Doctor lists it:

powershell
rightnow doctor fix tmux-clipboard

After applying a tmux fix, use the reload command Doctor prints, detach and reattach, then run /doctor again.

Clipboard routes

Clipboard writes can use the native clipboard, the tmux buffer, or OSC 52.

Set RIGHTNOW_CLIPBOARD_NO_OSC52=1 before starting RightNow to disable OSC 52 without changing native or tmux clipboard routes.

Apple Terminal cannot receive OSC 52 over SSH; copies still have a backup file.

The default backup is ~/.rightnow/last-copy.txt; RIGHTNOW_COPY_FILE selects another path.

Linux selections and SSH

Ctrl+V reads CLIPBOARD and never falls back to PRIMARY.

On XWayland, PRIMARY paste needs xclip or xsel on PATH.

Over SSH, use terminal-native Shift+Insert or Shift+middle-click for local selected text.

Keyboard fallbacks

  • Windows consoles can lose Ctrl+Enter; use Ctrl+I outside VS Code-family terminals.
  • VS Code-family terminals use Ctrl+L to send now.
  • Use Alt+Enter when Shift+Enter reaches a VS Code-family terminal as Enter.
  • WezTerm needs enable_kitty_keyboard = true for modified Enter keys.

Related