diff --git a/frontend/src/components/modal/TagChip.vue b/frontend/src/components/modal/TagChip.vue
index 7e11b31..ccd698d 100644
--- a/frontend/src/components/modal/TagChip.vue
+++ b/frontend/src/components/modal/TagChip.vue
@@ -10,7 +10,7 @@
       @click:close="$emit('remove', tag.id)"
     >
       <v-icon start size="x-small">{{ iconFor(tag.kind) }}</v-icon>
-      {{ tag.name }}<v-icon
+      <span class="fc-tag-chip__name">{{ tag.name }}</span><v-icon
         v-if="tag.is_system" end size="x-small" class="fc-tag-chip__system"
         title="System tag — tagged items are excluded from training other concepts"
       >mdi-shield-outline</v-icon><span
@@ -130,7 +130,17 @@ function iconFor (k) { return KIND_ICONS[k] || 'mdi-tag' }
 </script>
 
 <style scoped>
-.fc-tag-chip { display: inline-flex; align-items: center; gap: 1px; }
+/* A chip must never exceed the rail — a long character+fandom(+AUTO) chip used
+   to overflow the right edge and clip its close ✕ (operator-flagged 2026-07-06).
+   The name is the elastic part: it ellipsis-truncates so the ✕, fandom, and AUTO
+   badge stay reachable. Full name is still available via the chip's hover title. */
+.fc-tag-chip { display: inline-flex; align-items: center; gap: 1px; max-width: 100%; min-width: 0; }
+.fc-tag-chip__nav { max-width: 100%; min-width: 0; }
+.fc-tag-chip__nav :deep(.v-chip__content) { min-width: 0; overflow: hidden; }
+.fc-tag-chip__name {
+  overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
+  min-width: 0; flex: 0 1 auto;
+}
 /* The chip body navigates to the filtered gallery (#5); signal it's clickable.
    The close ✕ (remove) and the sibling kebab stay as the explicit controls. */
 .fc-tag-chip__nav { cursor: pointer; }