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

How to auto-name Herdr tabs from their Git branch and folder with Herdr Auto Title

Install the plugin so each Herdr tab shows its folder and branch without manual renaming.

Who it is forA developer working on several branches across several repos in Herdr at once, who loses track of which tab is which.

The problemHerdr tabs keep generic or stale names, so finding the tab for a specific feature branch means clicking through each one.

The outcomeEach tab is named after its folder and non-default branch, with its position number in front, and the plugin keeps running after restart.

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. Confirm Herdr is version 0.8.2 or newer and Go 1.24 or newer is installed.
  2. Run herdr plugin install kryptamine/herdr-auto-title --ref v0.14.0.
  3. Run herdr plugin action invoke herdr.auto-title.restart to start the plugin now.
  4. Open a directory on a feature branch in a new tab and check that the tab name shows the folder and the branch.

Prompt for your agent

In the repo kryptamine/herdr-auto-title, install the plugin into the Herdr setup on <target machine> with `herdr plugin install kryptamine/herdr-auto-title --ref v0.14.0` and then start it with `herdr plugin action invoke herdr.auto-title.restart`. Report the Herdr tab names for two tabs, one on the default branch and one on a feature branch, and confirm the feature branch name appears in its tab title.

Caveat. The first start renames every pane, including panes already named by hand, so rename important panes after the first start or accept that they will be renamed.

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