From b3e412a41f03fff785d31bd3610457d733ecc6fa Mon Sep 17 00:00:00 2001 From: Algis Dumbris Date: Tue, 25 Aug 2026 07:17:59 +0300 Subject: [PATCH 1/2] =?UTF-8?q?docs(qa):=20Web=20UI=20UX=20audit=20?= =?UTF-8?q?=E2=80=94=20ranked=20findings=20(ux-audit=20epic)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Heuristic + live-instance audit of every routed Web UI view in light/dark, first-run and populated states, at 1440/820/390px. 36 findings ranked P0-P3 with view, evidence, heuristic violated, suggested fix and effort. Audited against standard heuristics plus the house activity-UI rules (grouping, failure-only status, intent reason, histogram/log parity). --- docs/qa/ux-audit-webui-2026-08.md | 513 ++++++++++++++++++++++++++++++ 1 file changed, 513 insertions(+) create mode 100644 docs/qa/ux-audit-webui-2026-08.md diff --git a/docs/qa/ux-audit-webui-2026-08.md b/docs/qa/ux-audit-webui-2026-08.md new file mode 100644 index 000000000..9d8288c85 --- /dev/null +++ b/docs/qa/ux-audit-webui-2026-08.md @@ -0,0 +1,513 @@ +--- +title: "Web UI UX Audit — August 2026" +sidebar_label: "Web UI UX Audit (2026-08)" +description: "Heuristic + live-instance UX audit of the MCPProxy Vue Web UI, with a ranked P0-P3 backlog." +--- + +# Web UI UX Audit — August 2026 + +**Scope:** every routed view of the personal-edition Web UI (`frontend/src/views/`), in light and dark +themes, in first-run (empty) and populated states, plus reachable error states. +**Build audited:** `v0.60.0`, `main` @ `20a3e50` (`make build`, embedded frontend). +**Method:** two isolated cores (`127.0.0.1:18412` populated, `127.0.0.1:18413` first-run) on scratch +`--data-dir` **and** `--config`; Playwright/Chromium 1440×900 (plus 820px and 390px passes); ~90 +screenshots; programmatic WCAG contrast sampling (canvas-resolved computed colors); MCP traffic +generated over the real `/mcp` endpoint (reads, writes, destructive calls, failures, a sensitive-data +hit, repeated identical calls). +**Screenshots are not committed** — each finding names the state to reproduce. + +## Heuristics used + +Standard: Nielsen's 10, information scent, empty/error/loading-state completeness, WCAG 2.1 AA +contrast and keyboard operation, responsive behaviour, cross-view data consistency. + +House rules (from Algis's standing activity/tray UX preferences — treated as normative here): + +| # | Rule | +|---|------| +| H1 | Group consecutive same-tool calls into runs | +| H2 | Surface `metadata.intent.reason` as the user-facing context line | +| H3 | Mark only failures — no success checkmarks | +| H4 | Activity belongs at the top level | +| H5 | Show recently-seen clients as *idle*, never an empty "no clients" | +| H6 | Native forms over deep links | +| H7 | Never merge ok + error into one run; split runs on status change | +| H8 | Summary/histogram must visibly match the call log | +| H9 | `code_execution` sub-calls are first-class, with parent ↔ child navigation | + +--- + +## Executive summary + +The Web UI is in good shape structurally — the sidebar's Workspace / Observability / System grouping +gives real information scent, the server-detail error card (code + plain-language cause + copyable +remediation + docs link) is best-in-class, and the Agent Tokens empty state is a model for the rest of +the product. Recent work has already landed the hard parts of H2 and H9: the Activity view *does* +render `intent.reason` and *does* carry `parent_id` linkage for `code_execution` sub-calls. + +Three problems dominate, and all three sit directly under the epics this audit gates. + +**1. The numbers disagree with each other.** Within seconds of each other, on the same 24-hour window, +the Activity Log header reported **70 calls · 6 errors** while the Dashboard's Usage tab reported +**42 tool calls · 6 errors · 14.3% error rate**, and the Activity filter panel's own tiles read +**Total 42 / Success 15 / Errors 4** — which do not sum. Per-call latency is 3–5 ms in the Activity +table and a flat 10 ms p50/p95 for every tool in Usage. This is H8 at product scale: it is the fastest +way to lose a user's trust in an observability surface, and `action-log-transparency` cannot be built +on top of it. (F1, F2, F22) + +**2. The default landing page answers no question.** The Dashboard is a static hub diagram with +animated dots. The only real analytics — Calls per tool, Token sinks, Errors & latency, Activity over +time — live in a `v-show` tab that has no route, no sidebar entry, no deep link, and no bookmark. The +hero metric next to it ("32.4% tokens saved / 519 saved") did not move after 16 further tool calls. +This is exactly the gap `analytics-default-landing` exists to close. (F4, F23) + +**3. First run leaks users at the empty state.** Given that ~48% of installs are one-and-done, the +Servers page — the page a new user lands on after closing the wizard — shows *"No servers found / No +servers available"* with **no call to action at all**, while the Tools and Agent Tokens pages +in the same build have exemplary empty states with buttons. The Secrets page goes further: with zero +secrets there is **no way to add one from the Web UI at all**. (F3, F8) + +Alongside those: the Add Server modal's submit button sits 594px below the viewport and Escape does +not close it (F6); the security-critical "Docker isolation disabled" warning is the *least legible* +text on the Dashboard at **1.28:1** (F9); the sensitive-data drawer prints the AWS key it just flagged +in cleartext (F13); and at 390px the telemetry banner renders as a ~10-character-wide column ~440px +tall (F14). + +**Counts:** 4 P0 · 12 P1 · 12 P2 · 8 P3 (36 findings). + +**Suggested first slice (all S/M, unblocks the three downstream epics):** +F1 + F2 (one shared 24h aggregate behind both surfaces) → F4 + F23 (route `/usage`, put it in the +sidebar, consider it the default landing) → F3 + F8 (empty-state CTAs) → F5 + F7 (grouping + failure-only +status) → F9 (contrast tokens). + +--- + +## P0 — trust and conversion + +### F1. Activity Log and Usage report different totals for the same 24h window +- **View:** `Activity.vue` header; `Dashboard.vue` → Usage tab (`Usage.vue`) +- **Evidence:** Populated instance, both screens loaded within ~20s. Activity header: `70 calls · 6 errors`. + Usage 24h tiles: `Tool calls 42`, `Errors 6`, `14.3% overall error rate`. Activity's own paginator + agreed with 70 (`Showing 1-25 of 70`); Usage's "Activity over time" hour buckets summed to ~42. + Root cause is visible in the data: Activity counts every `type` (including `security_scan` and + `system_start`) as a "call"; Usage counts only `tool_call`. +- **Heuristic:** H8; Nielsen #4 consistency; #1 visibility of system status. +- **Fix:** One shared 24h aggregate, computed once server-side, consumed by Activity, Usage, tray and + CLI. Until then, relabel Activity's header to `70 events · 6 errors` and add a `42 tool calls` sub-count. +- **Effort:** M + +### F2. Activity's own filter tiles do not sum +- **View:** `Activity.vue` → Filters +- **Evidence:** Tiles read `Total (24h) 42 · Success 15 · Errors 4 · Blocked 0 · Rejected 0`. + 15 + 4 + 0 + 0 = 19, not 42. Simultaneously the header above said `42 calls`. On a later pass the + header said `70 calls · 6 errors` while the tiles still used a different denominator. +- **Heuristic:** H8; #1 visibility of system status. +- **Fix:** Make the tiles a partition of one denominator and label it (`42 tool calls in the last 24h`); + add an `Other / internal` bucket for whatever is currently unaccounted. Add a unit test asserting the + buckets sum to the total. +- **Effort:** S + +### F3. First-run Servers page has no call to action +- **View:** `Servers.vue`, first-run instance, zero servers +- **Evidence:** Empty state renders an icon plus *"No servers found"* / *"No servers available"* — + a restatement, no button, no link. The same build's `Tools.vue` empty state offers **Manage Servers** + and `AgentTokens.vue` offers **Create Your First Token** with a one-line explanation. Above the empty + state sit four zero-valued stat tiles and four zero-count filter pills (`All (0) Connected (0) + Enabled (0) Quarantined (0)`) plus a "Search servers…" box with nothing to search. +- **Heuristic:** Empty-state completeness; #6 recognition over recall; #10 help. Highest-leverage screen + for the ~48% one-and-done cohort. +- **Fix:** Replace with the AgentTokens pattern: headline, one line of why, and two buttons — + **Add Server** (primary) and **Browse Registry** (secondary) — plus a third quiet link, *Import from + your AI client configs*. Hide the stat row and filter pills at zero. +- **Effort:** S + +### F4. The default landing page carries no analytics, and the analytics that exist are unroutable +- **View:** `Dashboard.vue` (Overview) / `Usage.vue` +- **Evidence:** Overview is a hub diagram with four animated SVG dots on a 20s loop, a clients box, a + servers box and six buttons; the only quantitative content is a floating `32.4% tokens saved` chip. + All real analytics live under the Usage tab, which is `v-show`-toggled inside Dashboard — `Usage.vue` + has **no entry in `router/index.ts`** and no sidebar item, so it cannot be linked, bookmarked, or + returned to after a reload. +- **Heuristic:** #1 visibility of system status; information scent; H4 (observability at the top level). +- **Fix:** Give Usage a real route (`/usage`) and a sidebar entry under Observability; make the + Dashboard's default panel a compact answer to "what happened and what needs me" (24h calls/errors + sparkline, top tools, servers needing attention, recent failures) with the hub diagram demoted. +- **Effort:** M (route + nav is S; landing redesign is M) + +--- + +## P1 — significant friction on a primary path + +### F5. Activity does not group repeated identical calls, and stamps "Success" on every row +- **View:** `Activity.vue` table +- **Evidence:** 12 consecutive `everything:echo` calls with an identical reason produced 12 separate + rows, each repeating the same 3-line absolute timestamp, the same `📖 Polling the echo endpoint while + the user …`, and the word `Success`. On one 900px screen: 11 × "Success", 1 × "Error". Real logs are + far worse — Algis's own export was 1479 calls → 809 runs, with runs up to 100×. +- **Heuristic:** H1, H3, H7; #8 aesthetic and minimalist design. +- **Fix:** Collapse consecutive same-tool + same-status rows into a run (`echo ×12`, expandable), + splitting on status change so a run never mixes ok and error. Show a status chip only for + failed/blocked/rejected rows; leave successes blank. +- **Effort:** M + +### F6. Add Server modal: submit is below the fold, Escape does not close it, focus never enters the dialog +- **View:** `AddServerModal.vue` from `Servers.vue` / header **+ Add Server** +- **Evidence:** At 1440×900 the modal measured `scrollHeight 1494` vs `clientHeight 900` — 594px of the + form, including the submit/cancel row, is below the fold with no sticky footer and no visible close + affordance in the header. After opening, `document.activeElement` was still the triggering + `button.btn.btn-primary`; pressing Escape left `.modal-box` in the DOM. +- **Heuristic:** #3 user control and freedom; WCAG 2.1.1 keyboard; ARIA dialog pattern; H6. +- **Fix:** Sticky footer with the primary action; scroll the body only; move focus to the first field on + open; close on Escape and on backdrop click; add a header ✕; restore focus to the trigger on close. +- **Effort:** S + +### F7. A quarantined server card offers no way to review it +- **View:** `Servers.vue` card for a quarantined server; `ServerCard.vue` +- **Evidence:** The card shows a yellow *"Server is quarantined"* banner and the actions + **Enable · Details · Delete** (with a greyed **Scan**, disabled without explanation). Nothing on the + card leads to the tool-approval review, even though the stat tile above says + `Quarantined 1 — Need security review`. +- **Heuristic:** #7 flexibility and efficiency; the page states a required action and doesn't afford it. +- **Fix:** Make **Review** the primary action on a quarantined card (deep-link to the server's Security + tab / pending-tools list); demote Enable; add a `title` on the disabled Scan explaining why. +- **Effort:** S + +### F8. Secrets page cannot add a secret +- **View:** `Secrets.vue` +- **Evidence:** Empty state is *"No secrets found / No secrets available"* with no CTA. `AddSecretModal` + exists, but `showAddSecretModal()` is only reachable from a per-row **Set** button that renders when a + secret is *referenced in config but not yet set* (`Secrets.vue:138`). With zero rows, the page's stated + purpose ("Manage secrets stored in your system's secure keyring") is unreachable. +- **Heuristic:** #7; empty-state completeness; the page title promises a capability it doesn't expose. +- **Fix:** Page-level **+ Add Secret** button in the header, and the same CTA inside the empty state. +- **Effort:** S + +### F9. Security-critical text fails WCAG AA, worst on the security warnings themselves +- **View:** Dashboard hub chips; `ServerDetail.vue` error card; global primary buttons +- **Evidence** (canvas-resolved computed colors, effective ratio incl. opacity; AA needs 4.5:1 for normal text): + + | Text | Theme | Ratio | + |---|---|---| + | `Docker isolation disabled — enable Docker to protect your system` | corporate | **1.28** | + | `dig ` remediation box | dark | **1.07** | + | `https://docs.mcpproxy.app/errors/MCPX_HTTP_DNS_FAILED` | corporate / dark | **1.41 / 1.63** | + | `Manage in Settings` (telemetry banner) | dark | **2.07** | + | `Quarantine protection active` | corporate | **2.69** | + | `4 errors` (Activity header) | corporate | **2.92** | + | `32.4% tokens saved` | corporate / dark | **3.37 / 3.60** | + | `Host not found` badge | dark | **3.67** | + | `Add Server`, `Connect Clients`, `Restart` (white on primary) | both | **4.13** | + + The 4.13 figure is systemic: every filled primary button in the app fails AA by the same margin. +- **Heuristic:** WCAG 2.1 AA (1.4.3). +- **Fix:** Darken the primary token one step (4.13 → ≥4.5 buys AA on every button at once); give warning + and error surfaces AA-checked on-color foregrounds instead of tinted text on tinted fill; add a + contrast assertion to the Playwright sweep so this cannot regress. +- **Effort:** M + +### F10. Dashboard says no client is connected while Sessions shows a live session +- **View:** `Dashboard.vue` AI Agents box vs `Sessions.vue` +- **Evidence:** With an MCP client mid-session, the Dashboard box showed only + `Available: Claude Code, Claude Desktop, Cursor, VS Code, Codex CLI, Gemini CLI, OpenCode` and no + Connected group, while `/sessions` listed `ux-audit-client v1.0 — Active — 13 tool calls — Last active 11m ago`. +- **Heuristic:** H5; #1 visibility of system status; cross-view consistency. +- **Fix:** Drive the box from the same session store as `/sessions`; show recently-seen clients as + **idle** with a last-seen time rather than omitting them, and make each name link to its session. +- **Effort:** S + +### F11. Wrong remediation offered for a DNS failure, and three status vocabularies on one row +- **View:** `Dashboard.vue` attention banner; `Servers.vue` card; `ServerDetail.vue` header +- **Evidence:** For `broken-remote` (`dial tcp: lookup example.invalid: no such host`) the offered + action is **Restart** on both the Dashboard banner and the card. On the detail page one row of tiles + reads `Status: Enabled / Active` with a **green check**, `Connection: Offline`, and the page badge + reads `Disconnected` — three vocabularies, one of them green, for a server that is down. +- **Heuristic:** #1, #4 consistency, #9 help users recover. +- **Fix:** Map `health.action` for DNS/URL failures to **Edit URL** (opens the config tab focused on the + URL field). Collapse `Enabled/Active`, `Online/Offline` and `Connected/Disconnected` into one + admin-state + one health-level vocabulary, and never render a success glyph on an unhealthy server. +- **Effort:** M + +### F12. Servers card shows a raw Go error dump next to a perfectly good summary +- **View:** `Servers.vue` card +- **Evidence:** The card renders both the badge `Host not found` (good) and a full-width red block: + `failed to connect: MCP initialize failed during no-auth strategy: transport error: failed to send + request: failed to send request: Post "https://example.invalid/mcp": dial tcp: lookup example.invalid: + no such host` — note the duplicated `failed to send request:`. The detail page already renders this + correctly as *code + summary + Cause + remediation*. +- **Heuristic:** #9 errors in plain language. +- **Fix:** Show the structured summary + code on the card with a **Details** link; keep the raw cause on + the detail page only. Fix the duplicated wrapper text in the upstream error chain. +- **Effort:** S + +### F13. Sensitive-data drawer prints the secret it just flagged +- **View:** `Activity.vue` detail drawer +- **Evidence:** A call flagged `critical · aws_access_key · in arguments · in response` renders, a few + hundred pixels below the red detection panel, `"message": "AKIAIOSFODNN7EXAMPLE aws key here"` in + Request Arguments and `"Echo: AKIAIOSFODNN7EXAMPLE aws key here"` in Response Body, both in cleartext + with a **Copy** button. The same panel also exposes the internal field `_auth_auth_type: "admin"`. +- **Heuristic:** Security-UX: a screen-share, screenshot or exported drawer leaks the credential the + product exists to protect. #4 consistency (detect then display). +- **Fix:** Mask detected spans by default (`AKIA…MPLE`) with an explicit **Reveal** that is logged; + strip `_auth_*` internals from the user-facing argument view. +- **Effort:** S + +### F14. Mobile (390px) layout collapses +- **View:** all, at 390×844 +- **Evidence:** The telemetry banner text renders as a ~10-character-wide column consuming ~440px of + vertical space — over half the viewport — before any content. The attention banner wraps + `Host not found` onto 3 lines and the `View All Servers` label onto 3 lines. The Activity table shows + only **Time** and **Type**; Server, Details, Sensitive, Intent, **Status** and Duration are clipped off + the right with no horizontal-scroll affordance, so failures are invisible on a phone. The footer + overlaps the last table row. +- **Heuristic:** Responsive; #1 visibility (status is the clipped column). +- **Fix:** `min-w-0` / `flex-1` on the banner's text child; below `md`, render Activity as stacked cards + (time + tool + status + reason) instead of a table; make the footer static, not overlaying. +- **Effort:** M + +### F15. Security page renders four zero-valued tiles while it is still loading +- **View:** `Security.vue` +- **Evidence:** On the first visit after a cold start, the page showed + `Scanners Installed 0 · Total Scans 0 · Active Scans 0 · Findings 0` above a + *"Loading security data…"* spinner, with **Scan All Servers** greyed and **Refreshing…** spinning; the + Deep-scan card read *"Checking configuration…"*. The same page, once loaded, reads + `1 · 2 · 0 · 0 · Signatures 7`. The stat row sits outside the `v-if="loading && !initialized"` guard + (`Security.vue:222`), so `overview = {}` renders as real zeros. Warm reloads settle in ~130 ms; the + cold first paint is the one users see. +- **Heuristic:** #1 visibility of system status — showing false data is worse than showing none. +- **Fix:** Skeleton the tiles (and the Deep-scan state) until `initialized`; never render a numeral for + an unknown value. +- **Effort:** S + +### F16. Settings promises instant apply; `enable_code_execution` does not take effect +- **View:** `Settings.vue` → Advanced → *Enable code execution tool* +- **Evidence:** The page header states *"Changes save instantly; a badge marks fields that need a + restart"*, and `settings/fields.ts:191` declares the field with no restart flag. + `PATCH /api/v1/config {"enable_code_execution": true}` (the same call `api.patchConfig` makes) returned + `applied_immediately: true, requires_restart: false`, and `GET /api/v1/config` then reported `true` — + yet the `code_execution` tool still answered *"Code execution is disabled"*, including from a + brand-new MCP session. (The PATCH response also mislabelled `changed_fields` as `["mcpServers"]`.) +- **Heuristic:** #1 visibility of system status; the UI states an outcome that did not happen. +- **Fix:** Either wire the hot-reload path for this key or mark the field `restart: true` so the badge + appears; make `changed_fields` report the field actually changed. +- **Effort:** M + +### F17. Repositories: the registry cards look like the selector but aren't +- **View:** `Repositories.vue` +- **Evidence:** Three prominent cards (Official MCP Registry / Reference Servers / Docker MCP Catalog) + sit above a *"Choose registries…"* dropdown, a disabled search box and a disabled **Search** button; + the body reads *"Select a Registry — Choose a registry from the dropdown to start browsing"*. The cards + are not clickable and carry no hint that they are display-only. +- **Heuristic:** #6 recognition over recall; affordance/false affordance. +- **Fix:** Make the cards the selector (click to select, selected state visible); drop the dropdown, or + keep it only for multi-select. Enable the search box once a registry is selected and say so inline. +- **Effort:** S + +### F18. Connect modal: three interaction patterns, and "connected" means "config mentions mcpproxy" +- **View:** `ConnectModal.vue` +- **Evidence:** In one list: six rows offering a bare red **Disconnect** text link (no confirm), one row + reading `Config not found` with no action, and one offering **Review & connect** + **Check access**. + The footer's primary action is **Connect All** while every actionable row already says Disconnect. More + seriously, an instance on `:18412` reported those clients as connected because their configs contain a + `mcpproxy` entry — pointing at a *different* endpoint (`:8080`). The modal never shows which endpoint a + client is registered to. +- **Heuristic:** #1 visibility; #4 consistency; #5 error prevention (unconfirmed destructive link). + Also a hard blocker for `remote-access-tunnel`, where "which endpoint am I connected to" is the question. +- **Fix:** Show the registered endpoint per row and mark rows pointing elsewhere as *Connected to another + instance*. One action pattern for all rows (a button with three states). Confirm before Disconnect. + Make **Connect All** reflect how many rows it would actually change, and disable it at zero. +- **Effort:** M + +--- + +## P2 — consistency, comprehension, accessibility + +### F19. Onboarding wizard has no path for a user with no existing MCP setup, and hides the security choice +- **View:** `OnboardingWizard.vue`, first-run +- **Evidence:** Step 2 ("Servers") is entirely *"pick which servers from your existing AI clients to + import"*. A user with no prior MCP config sees an empty list and no alternative (no registry browse, no + manual add) inside the wizard. The footer offers two similar primaries — **Import as active** and + **Import & quarantine** — with no guidance on which is safer, and the safer one is the visually weaker + of the two. The security controls sit behind a collapsed `▸ Runtime isolation and MCP server quarantine` + disclosure. The server list is clipped mid-row with no scrollbar affordance, and there is no **Back**. +- **Heuristic:** #6, #7, #10; safe-by-default. +- **Fix:** Add a *"Nothing to import — browse the registry"* branch. Make **Import & quarantine** the + single primary and demote the other to a link labelled *Import without review*. Expand the isolation + panel by default. Add Back, and cap the list height with a visible scrollbar. +- **Effort:** M + +### F20. `/search` is an orphan and duplicates two other search surfaces +- **View:** `Search.vue` +- **Evidence:** Routed at `/search` but absent from the sidebar. `?q=echo` does not prefill — the page + renders its empty state regardless. Its layout is marketing-style (centered *"Powerful Tool Search"* + with three feature cards: Natural Language / Relevance Scoring / Cross-Server) unlike every other view. + Meanwhile the header has a *Search tools* box **and** a second greyed **Search** button, and `Tools.vue` + has its own search + four filter dropdowns. +- **Heuristic:** #4 consistency; #8 minimalist design. +- **Fix:** Pick one: fold the BM25 search into `Tools.vue` (or make `/search` the canonical page, add it + to the sidebar, honour `?q=`, and drop the marketing panel). Remove the duplicate header button or make + its enabled state obvious. +- **Effort:** M + +### F21. Server Logs tab is unreadable +- **View:** `ServerDetail.vue` → Logs +- **Evidence:** Each entry is a 5-line pretty-printed JSON object whose `message` field contains a second, + already-formatted log line with escaped quotes: + `"message": "2026-08-25T06:49:51.879+03:00 | INFO | core/connection_lifecycle.go:235 | Disconnecting from server | {\"server\": \"everything\", \"was_connec…` — clipped at the right edge, no wrap, no + horizontal scrollbar. Two different timestamps per entry (read time and event time). Controls are only + *Last 100 lines* and **Refresh** — no level filter, no text filter, no follow/tail. +- **Heuristic:** #8; #10 help with diagnosis. This is the primary debugging surface. +- **Fix:** Render one line per entry (`time · level · message`) with the structured fields behind a + disclosure; unescape the inner payload; add level + text filters and a follow toggle. +- **Effort:** M + +### F22. Usage charts invent tools and quantize latency +- **View:** `Usage.vue` +- **Evidence:** *Calls per tool*, *Token sinks* and *Errors & latency* all list `everything:doesnotexist` + and `broken-remote:whatever` — names from failed calls to tools that never existed — as first-class + tools with 100.0% error rates. Every row of the p50/p95 table reads exactly `10 ms`, while the Activity + table shows 3 ms / 4 ms / 5 ms for those same calls. The *Errors & latency* bar chart has no axis title + distinguishing error-rate bars from latency. +- **Heuristic:** #4 consistency; data honesty. +- **Fix:** Exclude unresolved tool names from the tool charts (or bucket them as *Unknown tool*); + fix or hide the latency quantization; label the chart axes. +- **Effort:** M + +### F23. The token-savings headline does not move +- **View:** `Dashboard.vue` chip; `Usage.vue` tile +- **Evidence:** `32.4% tokens saved · 519 saved` read identically before and after 16 additional tool + calls, with the panel stamped *Updated 21s ago*. The chip has no tooltip and no drill-down. +- **Heuristic:** #1 visibility; #2 match with the real world. This is the product's headline claim. +- **Fix:** Verify the aggregation window and refresh path; make the chip link to the Usage breakdown and + carry a tooltip explaining how the figure is derived. +- **Effort:** S + +### F24. Activity counts non-calls as "calls" +- **View:** `Activity.vue` header +- **Evidence:** First-run instance: the header reads `1 call` and the single row is + `🚀 System Start`. Populated: `70 calls` includes two `security_scan` rows and a `system_start` row. +- **Heuristic:** #2 match with the real world. +- **Fix:** Count `tool_call` for "calls" and label the rest as events (see F1). +- **Effort:** S + +### F25. The drawer for internal events is a dead end +- **View:** `Activity.vue` drawer for a `security_scan` row +- **Evidence:** Four fields (Status, ID, Server, Tool, Source) and ~80% whitespace — no scan verdict, no + findings count, no link to the scan report, though `/security/scans/:jobId` exists. On tool-call rows + the drawer shows a Session ID as plain text with no link to `/sessions`, even though Sessions links the + other way with **View Activity**. +- **Heuristic:** #7 flexibility; navigation should be bidirectional. +- **Fix:** Type-specific drawer bodies; link `security_scan` → its report and Session ID → `/sessions`. +- **Effort:** S + +### F26. Intent and Sensitive columns are unlabeled emoji +- **View:** `Activity.vue` table +- **Evidence:** The Intent column renders 📖 / ✏️ / ⚠️ for read/write/destructive; the Sensitive column + renders a red `☢ 1` badge. No legend, no visible key, and colour+emoji is the only encoding. +- **Heuristic:** #6 recognition over recall; WCAG 1.4.1 (colour/glyph as sole indicator). +- **Fix:** Emoji + short word (`read` / `write` / `destructive`), or a legend in the filter panel. + (The `sr-only` label is already present — surface it visually.) +- **Effort:** S + +### F27. Server stat tiles use an ambiguous denominator and double-count +- **View:** `Servers.vue` stat row +- **Evidence:** `Total Servers 4 (3 enabled) · Connected 2 (50% online) · Quarantined 1 (Need security + review)`. 50% is 2-of-4 (all servers) rather than 2-of-3 (enabled). The one server that is both disabled + and quarantined is counted in the Dashboard's right rail as **both** `1 disabled` and `1 in quarantine`, + reading as two problems. +- **Heuristic:** #2; #4. +- **Fix:** State the denominator (`2 of 3 enabled online`); make quarantine and disabled mutually + exclusive in the summary, or label the overlap. +- **Effort:** S + +### F28. Auth-required state shows three error surfaces at once and calls the key optional +- **View:** `AuthErrorModal.vue` +- **Evidence:** With no key: a modal *"Authentication Required"*, a red inline alert behind it, and a + yellow *"Connection Lost — Reconnecting to server…"* toast bottom-left — three messages for one cause. + The field is labelled **Enter API Key (optional)** though it is the only way in, and + **Continue Without Auth** is offered at equal weight (it leads to a shell of zero-valued tiles). + Instructions assume a tray icon, which headless/server installs do not have. +- **Heuristic:** #9 error messages; #5 error prevention. +- **Fix:** Suppress the inline alert and the reconnect toast while the auth modal is open. Relabel to + **API key** (required). Remove or heavily demote *Continue Without Auth*. Add the + `mcpproxy status`/config-file path alongside the tray instruction. +- **Effort:** S + +### F29. No "match system" theme; the default is light +- **View:** `SidebarNav.vue` footer → Theme; `stores/system.ts:28-44, 350` +- **Evidence:** 15 daisyUI themes are offered with no grouping and no *System* option; + `loadTheme()` falls back to `corporate` (light), so a user on a dark OS gets a light UI on first run + and must find the footer dropdown. +- **Heuristic:** #4 consistency with platform conventions; #7. +- **Fix:** Add **System** and make it the default (`prefers-color-scheme`); group the rest under a + "More themes" section. +- **Effort:** S + +### F30. Accessibility gaps on the main screens +- **View:** `Servers.vue`, `Activity.vue` +- **Evidence:** 5 form controls on `/servers` have no accessible name (no `aria-label`, no `placeholder`, + no associated `