Fix unreadable agent toolbelt chip text after theme change

The agent toolbelt editor (and agent input footer) snapshotted each
context chip's text color when the chip renderer was constructed
(`ContextChipKind::default_styles` -> `agent_view_chip_color`). That color
is theme-derived, so after switching themes the cached value went stale —
e.g. a color computed under a light theme (near-black) stayed on the chip
when the user switched to a dark theme like Cyber Wave, rendering the
value chips dark-on-dark and unreadable. The neighboring action chips were
unaffected because they recompute `sub_text_color(background)` on every
render.

Recompute the agent-view chip color from the live theme at render time
(mirroring the action chips), so the text always matches the current
theme. Non-agent-view chips keep their snapshotted prompt colors.

Co-Authored-By: Warp <agent@warp.dev>

Author: oz-agent

app/src/context_chips/renderer.rs

@@ -14,7 +14,7 @@ use warpui::{Action, Element};
 
 use super::context_chip::ContextChip;
 use super::display_chip::{chip_container, udi_font_size};
-use super::{spacing, ChipAvailability, ChipValue, ContextChipKind};
+use super::{agent_view_chip_color, spacing, ChipAvailability, ChipValue, ContextChipKind};
 use crate::appearance::Appearance;
 use crate::ui_components::icons;
 
@@ -56,6 +56,12 @@ pub struct Renderer {
     remove_button_state_handle: MouseStateHandle,
     is_disabled: bool,
     tooltip_override_text: Option<String>,
+    /// When true, the chip's text/icon color is recomputed from the live theme
+    /// at render time (via [`agent_view_chip_color`]) instead of using the
+    /// color snapshotted in `styles`. This keeps agent-view chips readable
+    /// after a theme change, since `styles.value_color` is captured once at
+    /// construction and would otherwise go stale.
+    is_in_agent_view: bool,
 }
 
 impl Renderer {
@@ -65,6 +71,7 @@ impl Renderer {
         value: ChipValue,
         styles: RendererStyles,
         availability: ChipAvailability,
+        is_in_agent_view: bool,
     ) -> Self {
         let is_disabled = !availability.is_enabled();
         let tooltip_override_text = availability.tooltip_override_text();
@@ -78,6 +85,7 @@ impl Renderer {
             remove_button_state_handle: Default::default(),
             is_disabled,
             tooltip_override_text,
+            is_in_agent_view,
         }
     }
 
@@ -104,6 +112,7 @@ impl Renderer {
             placeholder_value,
             styles,
             availability,
+            is_in_agent_view,
         ))
     }
 
@@ -147,7 +156,14 @@ impl Renderer {
         remove_button: Option<Box<dyn Element>>,
         appearance: &Appearance,
     ) -> Box<dyn Element> {
-        let mut color = self.styles.value_color;
+        // Agent-view chips recompute their color from the live theme so they
+        // stay readable across theme changes; other chips keep the prompt color
+        // snapshotted in `styles`.
+        let mut color = if self.is_in_agent_view {
+            agent_view_chip_color(appearance)
+        } else {
+            self.styles.value_color
+        };
         if self.is_disabled {
             color.a = (color.a / 2).max(48);
         }

app/src/context_chips/renderer_tests.rs

@@ -24,6 +24,7 @@ fn test_constructor_availability_updates_disabled_state_and_tooltip_override() {
         ChipAvailability::Disabled(ChipDisabledReason::RequiresExecutable {
             command: "gh".to_string(),
         }),
+        false,
     );
 
     assert!(renderer.is_disabled);
@@ -51,6 +52,7 @@ fn test_constructor_availability_enabled_has_no_disabled_state_or_tooltip_overri
             Properties::default(),
         ),
         ChipAvailability::Enabled,
+        false,
     );
 
     assert!(!renderer.is_disabled);