Connect to iTerm2

[adlnk]

Describe the bug

Seems like this only works for the native terminal right now. iTerm2 is a very common alternative, and would be nice to have it available since I do all my coding there.

Steps to reproduce

1. Open Buddi
2. Open Claude Code on iTerm2
3. Nothing happens

Expected behavior

For Buddi to see my claude code sessions

macOS version

15.7.3 (24G419)

Device

MacBook with notch

Buddi version

0.1.2

Logs / stack trace

Additional context

No response

[grayashh]

Hey @adlnk, thanks for filing this.

Buddi hooks into Claude Code via ~/.claude/settings.json, which is terminal-agnostic — iTerm2 isn't filtered anywhere on our side, so this is unexpected. A couple of quick checks would help narrow it down:

1. Did you start the Claude session after launching Buddi? The hook installer runs on Buddi launch, so a Claude session that was already running won't have picked it up. Try quitting that claude process and starting a fresh one.

2. Is the hook actually in your settings? Open ~/.claude/settings.json and confirm there are entries referencing buddi-hook.py. If they're missing, relaunching Buddi should re-install them.

3. Does the session show up in Buddi's chat panel at all, or is it only click-to-focus that's broken? That distinction matters:

   • If sessions don't appear at all → hook isn't reaching Buddi (likely a Python resolution issue — happy to dig in).
   • If sessions appear but clicking them doesn't bring iTerm2 forward → known weakness. iTerm2 3.5+ runs shells under an iTermServer daemon, which breaks the process-tree walk we use to find the owning terminal window.

If you can share which of those you're hitting (and a sample line from your settings.json hook entry), I can take it from there.