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

How to show each workspace's active task in the Herdr sidebar with Herdr Auto Title

Display the active tab's topic under each workspace name in the Herdr sidebar.

Who it is forA developer with several workspaces in Herdr who wants to see what each one is working on without opening it.

The problemThe Herdr sidebar shows workspace names and branches only, so the current task in each workspace is hidden.

The outcomeEach workspace row shows its name and branch, with the active tab's topic in bold underneath.

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. Open Herdr's config.toml and add the sidebar rows that include the $topic token, as shown in the README's recommended setup.
  3. Make sure the setting HERDR_AUTO_TITLE_WORKSPACES is left at its default of true, or set it to true in config.env.
  4. Run herdr plugin action invoke herdr.auto-title.restart and check that the sidebar shows the topic under each workspace.

Prompt for your agent

For the repo kryptamine/herdr-auto-title, add the README's [ui.sidebar.spaces] rows containing the $topic token to the Herdr config.toml on <target machine>, then restart the plugin. Report the sidebar rows for two workspaces and confirm each shows a topic line under its name and branch.

Caveat. Each client reads its own config.toml, so the sidebar rows must be set on every machine you attach from.

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