DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to tell Claude Code panes apart in Herdr's goto panel with Herdr Auto Title

Give each Claude Code pane its own name so the goto panel stops listing every one as claude.

Who it is forA developer running several Claude Code sessions across Herdr tabs who needs to switch to the right session quickly.

The problemHerdr's goto panel lists every Claude Code pane as claude, so the sessions cannot be told apart.

The outcomeEach Claude Code pane gets its own label based on what the session is doing, and the goto panel shows distinct names.

What you need first

  • Herdr 0.8.2 or newer installed
  • Go 1.24 or newer, since Herdr builds the plugin from source during install
  • macOS, Linux, or Windows
  • Familiarity with a terminal and editing a TOML config file

Steps

  1. Install the plugin with herdr plugin install kryptamine/herdr-auto-title --ref v0.14.0.
  2. Install Herdr's integration for Claude Code with herdr integration install claude.
  3. Run herdr plugin action invoke herdr.auto-title.restart so the setting takes effect.
  4. Start two Claude Code sessions in separate panes and open the goto panel with prefix plus g to check that each pane has its own name.

Prompt for your agent

Using the repo kryptamine/herdr-auto-title, set up Claude Code pane naming on <target machine> by running the Herdr integration install for claude and restarting the plugin. Report the goto panel entries for two open Claude Code panes and confirm they show different names instead of claude.

Caveat. Pane names depend on Herdr's integration being installed for Claude Code, and on Windows Herdr reports only the shell or a recognised agent per pane, so detection may be limited there.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page