Conversation
Add ui.tab_bar_position, ui.show_clock, and ui.prefix_hint to the versioned config reference so it stays in sync with the config model.
…ts (tvaintrob#1) Adds a new configurable keybinding `next_blocked_agent` that focuses the next agent in blocked state, wrapping around when reaching the end. This allows quickly jumping to agents that need human input without cycling through idle/working agents. Configuration (in config.toml): [keys] next_blocked_agent = "prefix+shift+n" Co-authored-by: tamir altshuler <tamir@tamirs-MacBook-Pro.local> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds two optional keybindings that move the active tab one position left
or right, so tabs can be reordered from the keyboard. Reordering was
previously mouse-drag only — Workspace::move_tab and the tab.move socket
API already existed, but nothing was bound to them.
Both are unset by default, so no existing binding changes. Example:
[keys]
move_tab_left = "ctrl+shift+left"
move_tab_right = "ctrl+shift+right"
Movement is clamped at the ends rather than wrapping, and routes through
move_tab_via_api so the change is broadcast like a mouse-driven move.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two optional keybindings to move the active tab one position left or right, so tabs can be reordered from the keyboard.
Why
Tab reordering already works — but only by mouse drag.
Workspace::move_taband thetab.movesocket API both exist; there was simply no keybinding wired to them. This closes that gap for keyboard-driven users (tmux'sswap-windowhabit).Notes
move_tab_via_apiso the move is broadcast identically to a mouse-driven one, rather than mutating workspace state directly.NavigateActionvariants, both dispatch paths,keysconfig, keybind help overlay, the default-config template, and the config reference.Tests
cargo test --release --bin herdr -- --test-threads=1→ 2638 passed.Depends on #2
mastercurrently fails to compile undercfg(test)(NextBlockedAgentmissing from a test-only match), so no tests run until #2 lands. The count above was measured with that fix applied locally, and CI here will stay red until #2 merges.Note that #2 also needs to add
keys.next_blocked_agentto the config reference —scripts/config_reference_check.pycurrently fails onmasterfor that key independently of this PR.🤖 Generated with Claude Code