Plugin · Claude Code · Productivity

Cosgroveb Claude Tmux Namer

cosgroveb-claude-tmux-namer is a Claude Code plugin for the Build phase that automatically renames your tmux window from conversation context after each response.

by cosgroveb · github.com/cosgroveb/claude-tmux-namer

Install this when you keep many Claude Code tmux windows open and need window titles that reflect the current task instead of generic defaults.

0
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install cosgroveb-claude-tmux-namer@cosgroveb/claude-tmux-namer
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:cosgroveb/claude-tmux-namer") and the paste-ready config with skillselion.get_install_config("plugin:cosgroveb/claude-tmux-namer").

About

What it does

cosgroveb-claude-tmux-namer is a Claude Code plugin that listens to your session and updates the current tmux window name to a concise phrase that reflects what you are working on. If you run several agent conversations at once—frontend in one window, API debug in another—default titles like bash or pane numbers force constant context switching. This plugin trades that friction for semantic labels derived from the latest exchange, so your window list reads like a lightweight task board. It complements session-summary style plugins but focuses on wayfinding during active work rather than end-of-session narrative. Requirements are Claude Code plus tmux; it is not a project management integration and does not sync titles to GitHub or Linear. Complexity stays low: install the plugin, keep coding, and let renames happen after agent turns. Best when you multiplex aggressively; skip if you use a single full-screen IDE session without tmux.

Highlights

  • Renames the active tmux window from Claude conversation context after responses
  • Uses a short descriptive phrase instead of leaving windows untitled or generic
  • Community Claude Code plugin (pluginCount: 1) from cosgroveb/claude-tmux-namer
  • Runs in the background during normal Claude Code chat—no manual rename step
  • Helps solo builders scanning many tmux windows find the right agent task quickly

Why builders use it

Multiple Claude Code tmux windows all look the same, so you waste time clicking the wrong pane or re-reading prompts to find the task you meant to continue.

After install, tmux window titles stay aligned with what each Claude session is doing, so parallel agent work stays scannable from the window list.

At a glance

  • Type - Plugin in Productivity.
  • Adoption - 0 installs, 0 stars, 0 votes.

FAQ

Who is cosgroveb-claude-tmux-namer for?

It is for terminal-first builders who multiplex Claude Code in tmux and want readable window names tied to the current conversation topic.

When should I use cosgroveb-claude-tmux-namer?

Use it when you routinely have more than one Claude window open and lose track of which pane matches which feature or bug.

How do I add cosgroveb-claude-tmux-namer to my agent?

Add the plugin from cosgroveb/claude-tmux-namer to Claude Code following the repository’s plugin setup, with tmux as your session manager.

Discussion

Comments

Share how you use cosgroveb-claude-tmux-namer, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.