JetBrains integrated terminal support

[ddmaster]

Hi!

Since AI integration in JetBrains (any of them) sucks, could we consider supporting revdiff in the JetBrains terminal?

Right now it’s actually pretty convenient to use Claude in the JetBrains terminal: I can quickly expand terminal to full screen with a hotkey and then hide it again. And quickly switch to code to continue or double check something by yourself.

But revdiff doesn’t work in JetBrains terminal:

Bash("$("~/.claude/plugins/cache/revdiff/revdiff/0.8.9/.claude-plugin/skills/revdiff/scripts/resolve-launcher.sh" launch-revdiff.sh)
  ⎿  Error: Exit code 1
     error: no overlay terminal available (requires tmux, zellij, kitty, wezterm, cmux, ghostty, iTerm2, or emacs vterm)

What do you think, would support be possible? Maybe there have already been attempts to do this or have possible workarounds? I couldn’t find anything in the repository history.

[umputun]

the launcher script needs a way to spawn revdiff in a separate pane/popup so it doesn't take over the parent Claude Code session. That's why it requires one of those backends - each one exposes a scripting API the script can call (tmux display-popup, kitty kitty @ launch, wezterm cli split-pane, ghostty/iTerm2 via AppleScript, etc.).

JetBrains' built-in terminal, as far as I know, doesn't expose anything like that. No CLI hook or IPC the launcher could use to open a split or new pane from inside the shell. A custom JetBrains plugin could probably bridge this (expose some spawn/split API the launcher could call), but that's a separate project and out of scope for this repo.

practical workaround: start tmux or zellij inside the JetBrains terminal, then run Claude from there. Once $TMUX (or $ZELLIJ) is set, the existing code paths kick in and revdiff opens in a popup over the JetBrains terminal pane. Works the same as any other plain terminal emulator without a popup API.

if you try the tmux route and hit something specific, drop a follow-up here.

[ddmaster]

I chose zellij, and it works fine as a workaround. No issues so far. Thanks!