Skip to content

fix: respect tmux base-index and pane-base-index settings#140

Open
noqcks wants to merge 1 commit intoTinyAGI:mainfrom
noqcks:fix/tmux-base-index
Open

fix: respect tmux base-index and pane-base-index settings#140
noqcks wants to merge 1 commit intoTinyAGI:mainfrom
noqcks:fix/tmux-base-index

Conversation

@noqcks
Copy link

@noqcks noqcks commented Feb 24, 2026

Summary

  • Daemon hardcoded window 0 and pane indices starting at 0 when targeting tmux panes
  • Users with set -g base-index 1 or set -g pane-base-index 1 in tmux.conf see silent failures: all channel processes, queue processor, and heartbeat fail to start
  • The tmux session is created successfully but send-keys commands produce "can't find window: 0" errors, making it look like everything started when nothing did

Fix

Detect base-index and pane-base-index at runtime via tmux show-option -gv and use them when targeting panes, instead of hardcoding 0.

Test plan

  • Tested with base-index 1 and pane-base-index 1 — all panes start correctly
  • Verify with default tmux config (base-index 0) still works

The daemon hardcoded window index 0 and pane indices starting at 0 when
targeting tmux panes. Users with `set -g base-index 1` or
`set -g pane-base-index 1` in their tmux.conf would see "can't find
window: 0" errors, causing all channel processes, queue processor, and
heartbeat to silently fail to start despite the session being created.

Detect the actual base indices at runtime so pane targeting works
regardless of the user's tmux configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant