Repository navigation
feat: P1 usability findings from the demo evaluation (#232) - #236
Merged
Merged
Conversation
…sks first Three things the dashboard did not do for the person using it. Recent activity rows lit up on hover and did nothing when clicked. They now open the same investigation a service-map node does, reachable by keyboard and labelled for a screen reader, and they only look clickable when an agent is available to answer. The window and namespace lived only in the saved dashboard, so a shared link opened on whatever the recipient had chosen and the two people ended up discussing different numbers. Both are in the address bar now; a link that carries them wins for the visit, and nothing is written back until the recipient changes a control themselves. An unrecognised value is dropped rather than rejected, so a stale link still opens the dashboard. Removing a view took effect on the click, and a dashboard has no undo. It asks first, and says that the card comes off the dashboard for everyone. A URL naming a dashboard that is not there now says so and offers the default, instead of quietly rendering the default while the address bar still pointed somewhere else. Reported in #232 (P1 items 10, 12 and 13). Claude-Session: https://claude.ai/code/session_017ovmTezqzvxVP8P9MGDQNk
…ty cards Searching for "checkout" answered "No matching chats / No matching dashboards" while checkout was live, traced and logged: the search only knew about things the user had already named. Matching services now appear in the rail under their own heading and open an investigation, and the catalogue is fetched only once someone is actually searching. dashboard_create and dashboard_update now probe the filtered cards they were handed and name the ones with nothing to show. The generated demo dashboard shipped "Checkout Error Logs" and "Checkout Warnings", both empty on arrival and permanently so, and nothing in the tool result told the model — which went on to describe them to the user as working views. Probes are capped, and a probe that fails is silent: a dashboard that saved correctly is never reported as an error because a follow-up query failed. Reported in #232 (P1 items 9 and 11). Claude-Session: https://claude.ai/code/session_017ovmTezqzvxVP8P9MGDQNk
…s one Putting the namespace in the address bar made the URL authoritative for what is shown, which also made the input unusable: every keystroke was overwritten by the value in the URL, so a namespace that came in on a link could not be cleared or changed. Typing now edits a draft that blur or Enter commits to both the dashboard and the URL. Found by driving a local build rather than by a test — the field looked right and simply would not take input. The empty-window hint is shortened to fit its tile, which was truncating it to "Nothing reported in this wi…". Reported in #232 (P1 item 12). Claude-Session: https://claude.ai/code/session_017ovmTezqzvxVP8P9MGDQNk
…romptly The check ran up to eight queries with no time limit while the caller waited on a dashboard that had already been written. A log query over a busy window was measured at twelve seconds during the evaluation, which would have made the tool's answer slower than the work it describes. The probes now share a three-second budget and stop once it is spent. Whatever answered is reported; the rest go unmentioned, which is the same trade the per-probe error path already makes. Claude-Session: https://claude.ai/code/session_017ovmTezqzvxVP8P9MGDQNk
This was referenced Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
P1 items 9–13 from #232 — the places where the product knew something and did not act on it. Two commits.
Rows lead somewhere, links carry the view, removal asks first
Search finds services, and a generated dashboard admits its empty cards
dashboard_createanddashboard_updateprobe the filtered cards they were handed and name the ones with nothing to show. The generated demo dashboard shipped "Checkout Error Logs" and "Checkout Warnings", both empty on arrival and permanently so, and nothing in the tool result told the model — which described them to the user as working views. Probes are capped at eight per call, and a failed probe is silent: a dashboard that saved correctly is never reported as an error because a follow-up query failed.Verification
just checkjust test-racewhen auth, API, ingest, query, MCP, or agent paths changedNew tests: activity rows opening an investigation, removal cancelled and confirmed, dashboard search-param parsing, a matching service opening an investigation, the catalogue not being fetched before a search, and the create tool both naming an empty card and staying quiet when the card has data.
MCP behaviour change to note: the
dashboard_createanddashboard_updatesummaries can now carry a sentence about cards that will render empty. The structured output is unchanged.Replaces #234, which GitHub closed when its base branch was deleted on merge of #233. Same four commits, replayed onto main.
Part of #232 (P1 items 9, 10, 11, 12, 13).
Added after review: the empty-widget probe now shares a three-second budget and stops when it is spent, so a dashboard that has already been saved is not held open behind up to eight queries — one of which was measured at twelve seconds during the evaluation.