claude-code - 💡(How to fix) Fix [FEATURE] Persistent project name banner in Claude Code UI [1 participants]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

When running multiple Claude Code sessions simultaneously across different terminal windows or tabs (a common workflow for developers juggling multiple projects), there is no persistent visual indicator of which project the current session belongs to. This creates a real cognitive overhead, especially mid-conversation, where scrolling up to find context clues is impractical. The user is forced to either ask Claude which project it's working in, or risk giving instructions intended for one codebase to another.

Proposed Solution

A small, persistent project name banner displayed somewhere in the Claude Code UI ideally at the top or bottom of the terminal interface that shows the current working directory or project name at all times, regardless of chat/scroll position. For example: 📁 my-sitecore-jss-project | Claude Code

This banner should: Always remain visible (sticky), not scroll away with chat history Derive its value from the working directory or project root (already available to Claude Code at session start) Be minimal and non-intrusive just enough to orient the developer at a glance

Alternative Solutions

Manually renaming terminal tab works at the shell level but doesn't help inside the Claude Code chat UI Using CLAUDE.md with the project name at the top Claude references it, but it doesn't create a persistent visual anchor Asking Claude at the start of each session repetitive and adds friction to every new conversation

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

A developer is working on two projects simultaneously: a Sitecore JSS backend and a Next.js frontend. Both are open in separate terminal windows, each running their own Claude Code session. After switching back and forth a few times, they return to one window mid-conversation and without scrolling all the way up have no reliable way to confirm which project Claude is currently operating in. They either pause to ask Claude, or worse, issue a refactoring command to the wrong codebase entirely. A persistent project banner would have immediately grounded them without any interruption to the workflow.

A developer had Claude Code running in both a VS Code extension and a terminal session simultaneously. After switching from the terminal to VS Code, they issued an instruction without realising the VS Code session was rooted in a different directory. Claude began creating folders and files in the wrong project before the developer noticed. A persistent project path banner would have immediately flagged the mismatch.

Additional Context

Claude Code already has access to the working directory and project root at session startup (e.g. via CLAUDE.md discovery and git root detection), so the data needed to populate this banner requires no new infrastructure it's purely a UI rendering concern. A similar pattern exists in tools like VS Code (which always shows the workspace name in the title bar) and tmux (which shows session/window names in a status bar). Claude Code could follow the same convention natively. Even a simple terminal title update via escape codes (e.g. \033]0;ProjectName - Claude Code\007) would be a meaningful step in the right direction for terminal-based users.