[GH-ISSUE #5976] [feature]: Save response body and metadata in request history #2347

New issue

Open

opened 2026-03-17 00:02:07 +03:00 by kerem · 3 comments

kerem commented

2026-03-17 00:02:07 +03:00

Owner

Originally created by @AbishekRaj2007 on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5976

Is there an existing issue for this?

I have searched the existing issues

Summary

Currently, the History panel saves request details (URL, method, headers, body) but discards the response entirely. When revisiting a history entry, there's no way to see what the server returned. It would be helpful to store the response body (up to a configurable size limit), status code, response time, and headers alongside each history entry, with a preview panel when clicking a history item. A toggle to disable response saving and a max history size cap would handle privacy and storage concerns. Tools like Postman, Insomnia, and Bruno all retain response history per request, and this would bring Hoppscotch closer to feature parity while making it significantly more useful for debugging.

Why should this be worked on?

This feature would significantly improve the debugging workflow for developers who repeatedly test the same endpoints. Without saved responses, there's no way to compare what an endpoint returned across different runs, which forces developers to re-send requests just to verify past behavior. This is especially painful when debugging intermittent issues or tracking down when a regression was introduced. Since tools like Postman, Insomnia, and Bruno already support this, its absence is a common reason developers switch away from Hoppscotch. Implementing this would directly improve day-to-day usability and bring Hoppscotch closer to feature parity with other leading API clients.

Originally created by @AbishekRaj2007 on GitHub (Mar 12, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5976 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Currently, the History panel saves request details (URL, method, headers, body) but discards the response entirely. When revisiting a history entry, there's no way to see what the server returned. It would be helpful to store the response body (up to a configurable size limit), status code, response time, and headers alongside each history entry, with a preview panel when clicking a history item. A toggle to disable response saving and a max history size cap would handle privacy and storage concerns. Tools like Postman, Insomnia, and Bruno all retain response history per request, and this would bring Hoppscotch closer to feature parity while making it significantly more useful for debugging. ### Why should this be worked on? This feature would significantly improve the debugging workflow for developers who repeatedly test the same endpoints. Without saved responses, there's no way to compare what an endpoint returned across different runs, which forces developers to re-send requests just to verify past behavior. This is especially painful when debugging intermittent issues or tracking down when a regression was introduced. Since tools like Postman, Insomnia, and Bruno already support this, its absence is a common reason developers switch away from Hoppscotch. Implementing this would directly improve day-to-day usability and bring Hoppscotch closer to feature parity with other leading API clients.

kerem added the

feature

label

2026-03-17 00:02:07 +03:00

kerem commented

2026-03-17 00:02:18 +03:00

Author

Owner

@homika482005 commented on GitHub (Mar 12, 2026):

Hello

I am interested in contributing to Hoppscotch and would like to work on this issue if it is available.
Please let me know if I can start working on it.

Thank you!

@homika482005 commented on GitHub (Mar 12, 2026): Hello I am interested in contributing to Hoppscotch and would like to work on this issue if it is available. Please let me know if I can start working on it. Thank you!

kerem commented

2026-03-17 00:02:23 +03:00

Author

Owner

@saksham242007 commented on GitHub (Mar 13, 2026):

Hi! This seems like a really useful feature—saving the response along with request history would make debugging much easier. I’d love to contribute to implementing this if it’s still available. Could you let me know if it’s available to work on?

@saksham242007 commented on GitHub (Mar 13, 2026): Hi! This seems like a really useful feature—saving the response along with request history would make debugging much easier. I’d love to contribute to implementing this if it’s still available. Could you let me know if it’s available to work on?

kerem commented

2026-03-17 00:02:28 +03:00

Author

Owner

@AbishekRaj2007 commented on GitHub (Mar 13, 2026):

Hi @homika482005 and @saksham242007, I've already been working on this issue and have a fix in progress. Could a maintainer please assign this to me officially? Happy to have the PR up soon!

@AbishekRaj2007 commented on GitHub (Mar 13, 2026): Hi @homika482005 and @saksham242007, I've already been working on this issue and have a fix in progress. Could a maintainer please assign this to me officially? Happy to have the PR up soon!

kerem referenced this issue

2026-03-17 01:20:09 +03:00

[PR #2347] [MERGED] feat: UI of shortcode actions #3750

kerem referenced this issue

2026-03-17 01:20:58 +03:00

[PR #2367] [CLOSED] Update TRANSLATIONS.md #3765

kerem referenced this issue

2026-03-17 01:21:46 +03:00

[PR #2391] [MERGED] chore(i18n): updated Chinese translation #3777