Show what an agent sent in History, as it happens - #99
Merged
Merged
Conversation
The MCP server has always recorded its sends — it writes to the same database as the window, so `query_response` can read a body back — but the window only read that database at launch. A request an agent made appeared in History after the next relaunch, and then as a bare URL: the server files its sends under one synthetic request per collection rather than an endpoint's id, so the name lookup came up empty. History now catches up on focus, when the tab is opened, and every few seconds while it stays open. The list is merged rather than replaced, so a loaded body or a send still streaming is untouched. Entries from the server wear an `MCP` badge, and `mcp` matches in the search box. Every entry now has a name. One with no request to be named after — sent by an agent, from scratch, or by a request since deleted — takes the name of the endpoint its URL hits in that collection, the loader's or a saved request's, and failing that its path, the way endpoint rows read in Collections. A row without a name looked like a rendering fault.
Merged
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
1 participant
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.
Requests an agent sends through the MCP server now appear in the History tab as they happen, with an
MCPbadge, instead of only after a relaunch. The server always recorded them to the shared database, but the window only read it at startup; History now refreshes on focus, when the tab is opened, and every few seconds while it stays open, merging new rows so loaded bodies and in-flight sends are untouched. Every entry also gets a name: the request it came from, else the endpoint its URL hits in that collection's loader manifest or saved requests, else its path, which fixes the untitled rows for MCP, scratch and deleted-request sends. Typingmcpin the history search filters to agent sends. Includes a changeset.