Third-party CLI agent toolbar shows stale and misleading state

[GodOnlyKn0w]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

Summary:
Three independent bugs in the third-party CLI agent toolbar, all affecting coding agent workflows:

Bug 1 — Multi-agent Git branch display stale (high severity):

• Open two CLI agents in the same project directory (D:\bootstrap-tools)
• In agent1: git switch audit/robustness-v1; git branch --show-current
• Terminal confirms audit/robustness-v1
• Sidebar still shows both agents as main. Status bar also shows main.

Bug 2 — Voice Input in toolbar layout but not in actual toolbar (medium):

• Settings → Third party CLI agents → Toolbar layout includes "Voice Input"
• Actual toolbar: no Voice Input button visible

Bug 3 — cwd/branch badges non-interactive (low):

• Bottom-right toolbar badges for directory and branch look clickable
• Clicking either has no effect — no navigation, no tooltip

Environment:

• Warp v0.2026.04.27.15.32.stable_03
• Windows 10 x86_64
• Git Bash (MINGW64)

To reproduce

1. Open Warp with two CLI agent sessions in the same project directory (e.g., D:\bootstrap-tools)
2. In the first agent session, run:

  git switch audit/robustness-v1                                                                                                                     
  git branch --show-current                                                                                                                          

Terminal output confirms: audit/robustness-v1
3. Observe the left sidebar — both agents show branch main
4. Observe the bottom-right status bar — shows D:\bootstrap-tools (main)

Expected behavior:

• Sidebar shows agent1 as audit/robustness-v1
• Status bar reflects the active terminal's actual cwd and branch

Actual behavior:

• Sidebar and status bar display stale main for all agents
• Git branch appears cached by directory path rather than per-session

Screenshots attached:

• bug1-sidebar-initial.png — sidebar showing both agents on main
• bug1-terminal-actual-branch.png — terminal showing audit/robustness-v1 while status bar shows main
• bug2-voice-input-settings.png — Settings panel with Voice Input enabled in toolbar layout
• bug2-voice-input-toolbar.png — Actual toolbar missing Voice Input button

Expected behavior

No response

Screenshots, videos, and logs

Operating system (OS)

Windows

Operating system and version

Windows 10 x86_64

Shell Version

GNU bash 5.2.37(1)-release (x86_64-pc-msys)

Current Warp version

Warp v0.2026.04.27.15.32.stable_03

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

2026/5/2

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[oz-for-oss]

This issue has been labeled ready-to-implement and is open for contributions involving code changes. If you'd like to tackle it, feel free to open a pull request against this issue. You can also comment @oz-agent on this issue to have the bot draft an implementation PR automatically.

[oz-for-oss]

@GodOnlyKn0w

Here's what I found while triaging this issue:

The report has enough detail to triage as reproducible on Windows Git Bash. The branch/CWD symptom is related to #9125 but this issue is specific to third-party CLI agent toolbar/sidebar state and includes separate Voice Input and badge-affordance problems.

I have a few follow-up questions before I can narrow this down:

1. Can you confirm whether the global Voice Input toggle under Settings → AI → Voice is enabled on this Windows install, and whether the Voice Input button appears in the regular Warp agent toolbar outside a third-party CLI agent session?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that third-party CLI agent toolbar/sidebar state appears to reuse generic prompt/context-chip metadata in ways that can leave branch/CWD stale, expose unavailable Voice Input layout items, and render disabled chips with clickable affordances..

Triage summary

This is a Windows bug report for third-party CLI agent toolbar/sidebar metadata. It bundles three related toolbar problems: branch/CWD state stays stale after a branch switch in one of multiple agent sessions; Voice Input can appear in the CLI toolbar layout editor but not render in the actual toolbar; and CWD/branch badges look interactive but do nothing.

Reproducibility

High for initial triage: the report includes exact version, OS/shell, concrete steps, terminal-confirmed branch output, and screenshots. The combined issue spans multiple UI surfaces, so implementation should verify each subcase independently on Windows Git Bash.

Likely root cause

The code paths reuse generic context-chip and tab metadata for CLI-agent UI. Vertical tabs and toolbar metadata call display_working_directory/current_git_branch, which prefer prompt-chip values; git branch chips initialize from PrecmdValue::git_branch and refresh by periodic shell command. In a long-running third-party CLI agent session, prompt/precmd and per-session state can lag behind a branch switch, especially when multiple sessions share the same repo path.

The CLI toolbar layout editor exposes VoiceInput in available/default CLI items, while actual rendering only returns the mic button when the voice_input feature is compiled and AISettings::is_voice_input_enabled is true. This can make the layout editor advertise an item the current runtime will suppress.

The branch and working-directory display chips still render with chip affordances, but DisplayChipAction::ToggleMenu returns early while a CLI-agent session is active, so the UI can look clickable while intentionally doing nothing.

Duplicate check

I enumerated open issues and checked recent closed issues from the last 7 days. Related but not duplicate: #9125 covers stale branch/CWD in vertical tabs after external CWD changes; #9573/#9870 cover other CLI-agent toolbar activation issues. I did not find two or more existing issues matching this issue's combined toolbar/sidebar stale state + voice layout + non-interactive badge symptoms, so this should not be marked duplicate.

Suggested next steps

• Treat this as a CLI-agent toolbar metadata/state bug and verify on Windows Git Bash with two same-directory CLI-agent sessions.
• Consider splitting implementation into: per-session branch/CWD refresh, toolbar layout availability vs render gating for Voice Input, and disabled/tooltip styling for CLI-mode context chips.

Question reasoning

1. Can you confirm whether the global Voice Input toggle under Settings → AI → Voice is enabled on this Windows install, and whether the Voice Input button appears in the regular Warp agent toolbar outside a third-party CLI agent session? — The layout editor can list Voice Input while actual CLI toolbar rendering is gated by voice feature/runtime settings, so this distinguishes a CLI-toolbar-specific rendering bug from a disabled or unavailable Voice Input runtime.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[GodOnlyKn0w]

这三个 bug 共享同一个根模块 app/src/workspace/view/vertical_tabs.rs（~6000 行），都围绕垂直标签栏的行渲染、状态同步和异步数据更新。
Bug 1 — Git 分支名显示异常
现象：git checkout 后垂直标签栏里的分支名不更新，或初始加载时为空。
根因定位：current_git_branch()（tab_metadata.rs:47）先读 prompt chip 里的 ShellGitBranch，chip 为空则回退到 git_status_metadata()。两者都依赖文件系统事件触发更新——如果事件比渲染先到，chip 仍是旧值；如果事件还没到，fallback 也是旧的。branch_label_display() 在 Branch 模式下还控制是否显示 git 图标，条件判断有可能在分支切换时返回错误状态。
关键链路：GitRepoStatusModel → current_prompt.rs:1426 set_git_repo_status() → chip 值更新 → render_terminal_row_content() 读取并渲染。
Bug 2 — 工具栏 Badge 不显示/不更新
现象：终端标签行上应有 badge 提示的地方没有显示（如 diff 统计 +3 -1、未保存标记等）。
根因定位：TypedPane::badge()（vertical_tabs.rs:2576）只对 CodePane 返回 "Unsaved"，所有 Terminal 类型直接返回 None。Terminal 的 diff stats 走的是另一条路径 render_passive_terminal_diff_stats_badge()，需要 GitLineChanges 数据。这个数据同样来自异步文件系统事件，可能在渲染时尚未就绪。另外 PaneRowBadgeMouseStates 的清理逻辑（line 1676）只删不存在的 pane，不处理重排的情况，可能导致 badge hover 状态残留。
Bug 3 — 侧边栏 Tab 渲染异常
现象：tab 行颜色错乱、图标显示错误、detail sidecar 信息不对、快速切换 tab 时闪烁。
根因定位：核心是 RefCell<HashMap<PaneId, ...>> 模式管理所有 hover/drag/badge 状态。增删 pane 时清理不完全（line 1676 只删不存在的 key，不处理顺序变化）；compute_tab_group_color_mode() 在快速切换 active tab 时可能计算出错误的 per-pane 颜色；resolve_summary_pane_kind_icons() 对 agent/terminal 模式的图标解析有边界情况；跨窗口 tab 拖拽（CrossWindowTabDrag）的状态可能泄漏到渲染中。
共同病灶
三个 bug 的共性问题是观察者模式的时序竞争：git 分支、diff stats、tab 状态都是异步事件驱动更新，但渲染管线假设数据已就绪。RefCell 在 borrow_mut() 期间如果触发 re-render，状态不一致会直接反映到 UI。
建议排查顺序
在 current_git_branch() 三条路径加 log，确认切换分支后各路径返回值
检查 render_passive_terminal_diff_stats_badge() 调用时 GitLineChanges 是否为旧值
验证 PaneRowBadgeMouseStates 清理在 pane 重排场景的覆盖
追踪 ShellGitBranch chip 填充时机 vs vertical tabs 渲染周期
快速切换 tab 时检查 compute_tab_group_color_mode 的边界

[oz-for-oss]

@GodOnlyKn0w

Here's what I found while triaging this issue:

Thanks for the detailed report and screenshots. This looks actionable as a Windows/Git Bash third-party CLI-agent toolbar/sidebar state issue; #9792 is related to branch mismatch, but it does not cover this same CLI-agent toolbar/sidebar workflow, so I’m not marking this as a duplicate.

I have a few follow-up questions before I can narrow this down:

1. After running git switch, does the sidebar/status toolbar remain stale after waiting about 10 seconds or running another prompt command, or does it eventually update?
2. Is the separate Voice Input setting under Settings > Agents/Warp Agent > Voice enabled on this Windows install?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that third-party CLI agent toolbar/sidebar state appears stale or misleading on Windows/Git Bash across branch metadata, Voice Input visibility, and CLI toolbar chip affordances..

Triage summary

This appears to be a bug in the third-party CLI agent toolbar and vertical-tab/sidebar metadata surfaces on Windows/Git Bash. The report has concrete reproduction steps, screenshots, Warp version, OS, and shell details, so reproducibility is high, although two small reporter details would help distinguish a persistent stale-state bug from expected async delay or a disabled voice-input setting.

Maintainer notes

• Branch and cwd display for terminal/CLI-agent rows flows through prompt/context chip state and TerminalView metadata helpers. current_git_branch() prefers the current prompt's ShellGitBranch chip and falls back to git_status_metadata().
• Git metadata is loaded by the repo-scoped GitRepoStatusModel, refreshed asynchronously from repository watcher events and after prompt refreshes. That makes stale display plausible when a CLI-agent session switches branches and the vertical tabs/status toolbar render before the prompt chip or repo metadata refresh propagates.
• The CLI agent toolbar editor can list VoiceInput as an available/configured item, but actual footer rendering hides it when the voice-input feature is unavailable or AISettings::is_voice_input_enabled() is false. That can make the toolbar layout look enabled while the actual toolbar omits the button.
• Working-directory and git-branch display chips explicitly suppress click/menu behavior during active CLI-agent sessions, while still rendering chip-like UI. That matches the report that cwd/branch badges look clickable but clicking them has no visible effect.

Relevant code areas

• app/src/terminal/view/tab_metadata.rs — terminal display cwd, current git branch, and diff line changes helpers.
• app/src/context_chips/current_prompt.rs — external git status updates into ShellGitBranch and GitDiffStats chips.
• app/src/code_review/git_status_update.rs — repo-scoped async git metadata cache/watcher.
• app/src/workspace/view/vertical_tabs.rs — vertical tab/sidebar terminal row and summary metadata rendering.
• app/src/ai/blocklist/agent_view/agent_input_footer/mod.rs and chips.rs — CLI agent toolbar item rendering and display-chip refresh.
• app/src/ai/blocklist/agent_view/agent_input_footer/toolbar_item.rs — CLI toolbar defaults/available items, including VoiceInput.
• app/src/context_chips/display_chip.rs — cwd/branch chip interactivity suppression in CLI-agent sessions.

Duplicate check

I enumerated open non-PR issues and found related reports such as #9792 for branch mismatch, plus broader CLI-agent toolbar requests, but fewer than two existing issues match the same combined Windows/Git Bash third-party CLI-agent toolbar/sidebar stale-state symptoms. Not marking as duplicate.

Question reasoning

1. After running git switch, does the sidebar/status toolbar remain stale after waiting about 10 seconds or running another prompt command, or does it eventually update? — Git metadata refresh is asynchronous and throttled, so this distinguishes a transient refresh delay from a persistent missed update.
2. Is the separate Voice Input setting under Settings > Agents/Warp Agent > Voice enabled on this Windows install? — The CLI toolbar renders VoiceInput only when the global voice-input setting/feature is enabled, even if the toolbar layout contains that item.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[GodOnlyKn0w]

Q1: git switch 后侧边栏分支名会刷新吗？

会，但有延迟。 关键链路：

  git switch → 文件系统变更 → watcher 触发 → 油门 5 秒 →                                                                                               
  async 计算 metadata → MetadataChanged 事件 → chip 更新 → 重新渲染                                                                                    

具体细节（代码都在 git_status_update.rs）：

• 5 秒油门：throttle(Duration::from_secs(5), throttled_rx) — metadata 刷新最快每 5 秒一次
• index.lock 抑制：git 操作期间 .git/index.lock 存在时，commit_updated 事件被丢弃
• 无 timer 兜底：watcher 激活后，ShellGitBranch 标记为"外部更新"，跳过 30 秒定时器。只靠文件系统事件
• 跑 ls 没用：不会触发刷新，纯事件驱动

→ 等 10 秒足够看到更新，正常情况 5-7 秒。最坏情况：index lock 持续 + 油门窗口重叠，可能接近 10 秒。

────────────────────────────────────────────────────────────────────────────────

Q2: Voice Input 设置开关

存在，但受多层门控：

is_voice_input_enabled() (ai.rs:1592) 三道关卡：

1. cfg!(feature = "voice_input") — 编译期 feature flag
2. is_any_ai_enabled(app) — AI 必须开启
3. voice_input_enabled_internal — 用户开关（默认 true，toml 路径 agents.voice.voice_input_enabled）

额外工作区级检查：UserWorkspaces::is_voice_enabled()

Settings 路径：Settings > AI > Voice Input（ai_page.rs，ToggleVoiceInput action）
Windows 上默认快捷键：AltRight（Fn 键在 Windows 被排除）

→ 如果用户说"找不到"，大概率是 voice_input feature 没编译进去，或者 workspace 级别禁用了。