# Specification: Discussion Metrics and Compression

## 1. Overview
The user requested better visibility into token usage on a per-response and per-discussion basis, rather than just session-wide totals. Additionally, the current history truncation is deemed too naive. The user wants a smarter compression strategy utilizing a helper agent to summarize, categorize, and compact discussion entries (especially tool/vendor logs) when the token limit is approached.

## 2. Functional Requirements
*   **Per-Response Metrics:** Update the Comms History and Discussion Hub panels to display token usage (input/output/cache) and remaining quota for each specific response.
*   **Discussion-Level Metrics:** Add a summary of total token usage for the active discussion.
*   **Helper Agent Compression:**
    *   Implement an asynchronous helper agent capable of analyzing a `discussion`'s history.
    *   The agent should categorize entries (e.g., tool calls, user prompts, AI thinking) and generate a compacted summary.
    *   Provide UI options to trigger this compression manually or set thresholds for automatic suggestions.
*   **New Session Prompt:** Allow the AI to generate a "summary prompt" and "target prompt" to effortlessly transition a heavy, exhausted discussion into a fresh session with adjusted context.

## 3. Non-Functional Requirements
*   **Performance:** The helper agent must run asynchronously to avoid blocking the main GUI thread.

## 4. Acceptance Criteria
*   Token metrics are clearly visible per entry in the Comms History.
*   A new "Compress Discussion" button triggers the helper agent, which successfully produces a compacted history.
*   The system can transition an exhausted discussion into a new one using an AI-generated summary.