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

How to shorten or hide tab titles with a config.env file with Herdr Auto Title

Set title length, branch display, and position using a config.env file.

Who it is forA developer whose Herdr tab titles are too long or cluttered with branch names and needs them trimmed.

The problemDefault titles may be wider than the tab bar or include branch text the user does not want.

The outcomeTab titles stay within a chosen width, long branch names are shortened or hidden, and the settings persist across updates.

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. Copy the file config.env.example from the repo to ~/.config/herdr-auto-title/config.env.
  2. Uncomment and set HERDR_AUTO_TITLE_MAX_LENGTH for the longest title width, or HERDR_AUTO_TITLE_BRANCH_MAX set to 0 to hide branches.
  3. Run herdr plugin action invoke herdr.auto-title.restart, since the file is read once at startup.
  4. Check that a tab on a feature branch shows the expected title width or no branch.

Prompt for your agent

In the repo kryptamine/herdr-auto-title, create ~/.config/herdr-auto-title/config.env on <target machine> from config.env.example with HERDR_AUTO_TITLE_BRANCH_MAX set to 0, then restart the plugin. Report the tab titles before and after the change and confirm no branch name appears in them.

Caveat. The config file is read only at startup, so every change needs a restart before it takes effect.

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