From 235b369d1549c97996a36479279e9866e5519c51 Mon Sep 17 00:00:00 2001 From: Ed_ Date: Sun, 8 Mar 2026 13:55:32 -0400 Subject: [PATCH] chore(conductor): Add per-response metrics requirement to caching optimization track --- conductor/tracks/caching_optimization_20260308/plan.md | 2 ++ conductor/tracks/caching_optimization_20260308/spec.md | 1 + 2 files changed, 3 insertions(+) diff --git a/conductor/tracks/caching_optimization_20260308/plan.md b/conductor/tracks/caching_optimization_20260308/plan.md index 985343e..b8632c4 100644 --- a/conductor/tracks/caching_optimization_20260308/plan.md +++ b/conductor/tracks/caching_optimization_20260308/plan.md @@ -35,5 +35,7 @@ - [ ] Implement visual indicators (badges) for cached files in the Context Hub. - [ ] Task: Add manual cache management buttons to the AI Settings panel. - [ ] "Force Cache Rebuild" and "Clear All Server Caches". +- [ ] Task: Update Comms Log UI to show per-response metrics. + - [ ] Modify `_render_comms_history_panel` in `src/gui_2.py` to display token usage (including cache hits) for each response entry. - [ ] Task: Final end-to-end efficiency audit across all providers. - [ ] Task: Conductor - User Manual Verification 'Phase 4: GUI Integration & Visualization' (Protocol in workflow.md) diff --git a/conductor/tracks/caching_optimization_20260308/spec.md b/conductor/tracks/caching_optimization_20260308/spec.md index 1b71a60..27f87ac 100644 --- a/conductor/tracks/caching_optimization_20260308/spec.md +++ b/conductor/tracks/caching_optimization_20260308/spec.md @@ -35,6 +35,7 @@ This track aims to verify and optimize the caching strategies across all support - Add a "Force Cache Rebuild" button to invalidate existing caches and start fresh. - Add a "Clear Provider Caches" button to explicitly delete server-side caches (primarily for Gemini). - **Cache Awareness:** Display a visual indicator (e.g., a "Cached" badge) next to files in the Context Hub that are currently part of a cached prefix. +- **Per-Response Comms Metrics:** Ensure each response entry in the Comms Log displays its specific token usage (input, output, cached) directly in the list or detail view for immediate verification of caching efficacy. ## Non-Functional Requirements - **Efficiency:** The caching logic itself must not introduce significant overhead or latency.