Add friendly names to zellij worker tab titles #103
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR enhances zellij tab naming in the Claude Orchestrator by adding user-friendly names to tab titles. Previously, tabs were named using only technical identifiers (e.g.,
work-w-3wl). Now they display both the work ID and a descriptive friendly name (e.g.,work-w-3wl (action_jackson)), making it significantly easier to identify and navigate between work sessions.Changes
New Helper Function
FormatTabName()helper ininternal/claude/runner.goto consistently format tab names with optional friendly namesprefix-workID (friendlyName)when friendly name exists, otherwiseprefix-workIDUpdated Functions
All zellij tab creation functions now accept and use friendly names:
Updated Callers
Modified all call sites across the codebase to pass work friendly names:
cmd/run.go: runTasks, runFullAutomatedWorkflow, RunWorkcmd/work.go: runWorkCreate, runWorkConsole, runWorkClaudecmd/work_automated.go: runWorkCreateWithBeads, runAutomatedWorkflowcmd/tui_plan_work.go: executeCreateWorkcmd/tui_work.go: createWork, openConsole, openClaudeIssues Resolved
Closes the following beads:
Testing
work.NameorworkerNamefrom database recordsImplementation Details
The implementation maintains backward compatibility - if no friendly name is provided (empty string), tabs display with just the work ID. This ensures the system continues to work even if friendly names are not set.
The change is purely cosmetic and does not affect the underlying functionality or data model. All existing workflows continue to work unchanged.
🤖 Generated with Claude Code