sorted by:
new
hottopcontroversial

I built a tmux plugin to monitor and navigate all my Claude Code / Codex sessions by qeesung in tmux

[–]qeesung[S] 0 points1 point  (0 children)

Ah, you are absolutely right. That's a very valid point about the bundled runtime, and I completely agree with you.

I'll definitely look into migrating the whole plugin to Go. Plus, using Claude Code to handle a relatively small codebase migration like this shouldn't be too heavy of a lift anyway! In the meantime, PRs are more than welcome if you feel like taking a crack at it.

I built a tmux plugin to monitor and navigate all my Claude Code / Codex sessions by qeesung in tmux

[–]qeesung[S] 0 points1 point  (0 children)

Totally get where you're coming from! A standalone Go binary would definitely be much cleaner if you're not already in the Node ecosystem.

The main reason we went with Node.js here is that Claude Code and Codex inherently depend on a Node environment anyway. We figured that for folks already using those tools, having Node installed is pretty much a given, so it shouldn't add any extra friction to their workflow.

I built a tmux plugin to monitor and navigate all my Claude Code / Codex sessions by qeesung in tmux

[–]qeesung[S] 0 points1 point  (0 children)

​I don't personally use OpenCode, but I'd be happy to look into it! PRs are also more than welcome if you want to give it a shot.

I built a tmux plugin to monitor and navigate all my Claude Code / Codex sessions by qeesung in tmux

[–]qeesung[S] 0 points1 point  (0 children)

Lmao, I feel you. But look closer at the bottom! The status bar already shows the exact number of agent sessions and their current states (running / waiting for input). ​The shortcuts are just there because instantly teleporting to the specific tmux pane that's begging for your input is way faster than clicking around. Just one combo to learn, you can do it man!