Introduce global requests history window

[julienbourdeau]

Summary

This is getting close but it's still a work in progress.

I'm adding a global history window to see all previous requests, with their body, method and so on. It's mostly frontend work but there is some database schema change needed. I believe this should live together with the existing history per request, not replace it.

• Small DB change
  Because of the way history works now, some attributes are not saved and rely on the current request. Like method, name and body_type. I have added those to the response table.

• UI and features
  I went for a separate window because I like it more. It's accessible via the cmd + K palette.
  I added a button to collapse all requests, to delete all requests, to delete one request. I'm missing one button to replay/restore a request specifically.

• HTTP + Graphql
  For now, only http and graphql requests are supported. gRPC and websocket could be handled in a future release. Ideally, I'd add filters at the very top and you can see only one type at the time. They are in different tables so it's annoying to handle pagination and such. And I think you only really need to see one at a time.

Any feedback is very welcome!

Submission

• This PR is a bug fix or small-scope improvement.
• If this PR is not a bug fix or small-scope improvement, I linked an approved feedback item below.
• I have read and followed CONTRIBUTING.md.
• I tested this change locally.
• I added or updated tests when reasonable.

Approved feedback item (required if not a bug fix or small-scope improvement):

https://yaak.app/feedback/posts/show-global-history

Related

• https://yaak.app/feedback/posts/save-request-data-for-response-history
• https://yaak.app/feedback/posts/request-body-on-history

Screenshots

Short video

CleanShot.2026-04-25.at.14.04.44.mp4

[julienbourdeau]

😢 😢 😢

[gschier]

Why did you close this @julienbourdeau?

My apologies for the delay. It's hard to get around to reviewing large feature implementations like this without having discussed design/implementation details in the ticket, as I usually have to go in and change a ton of stuff in order for it to fit with Yaak's architecture and UI/UX.

I think this is likely a feature I will implement myself because of the larger scope, but I will be sure to give you contribution credit in the repo if I do. Thanks for taking the time on it!

[julienbourdeau]

I mainly closed it because there was many conflicts.

It's surprisingly not that much code for the feature because I reused many components.
Also, I couldn't figure out why I had formatting changes on the gen_* files, which was very frustrating.

reviewing large feature implementations like this without having discussed design/implementation details in the ticket
I absolutely understand. It would have saved me times probably too but I was happy to discover the codebase. I like having a first version to discuss the details, especially for the UI.

I'm happy to get your take and modify it if you want, but I totally get that you'd rather do it yourself.