Skip to content

Conversation

@KyleKincer
Copy link

@KyleKincer KyleKincer commented Feb 3, 2026

Summary

  • Add request-to-response duration display (e.g., "245ms", "2.4s", "1m 30s") as blue badge next to method names
  • Show timestamps for requests and server notifications in collapsed view
  • Display full timing details (requested/responded timestamps with duration) in expanded view
  • Add TimestampedNotification wrapper for server notifications with receive timestamps
  • Add RequestHistoryEntry type with timing fields for request history

Note on V2

This feature aligns with V2's existing design - the HistoryEntry type in v2/core already includes a duration field, and the V2 UX spec shows timing display. However, V2's timing capture isn't wired up yet. This PR provides the functionality for V1 users in the interim.

Test plan

  • npm run build passes
  • npm run lint passes
  • All 459 unit tests pass
  • E2E tests pass (Chromium)
  • Manual testing: connect to MCP server, make requests, verify duration badges appear
  • Manual testing: expand history items and verify full timing details show
  • Manual testing: verify notification timestamps appear correctly

🤖 Generated with Claude Code

…ions

Add temporal context to help debug MCP server behavior:
- Display request-to-response duration (e.g., "245ms", "2.4s")
- Show timestamps for requests and notifications
- Add expanded view with full timing details

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant