mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #5582] [feature]: Console feature like Postman #2156
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2156
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pmondal-int on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5582
Is there an existing issue for this?
Summary
It would be great if Hoppscotch had a console feature like Postman. Its a very useful feature that streamlines debugging issues with requests, and also writing the pre/post request scripts as well.
Why should this be worked on?
One problem we run into frequently is sometimes requests don't work as expected, and to debug it we want to confirm that the request had the right headers and data. While we can go to the Chrome network tab, its a lot of clicks to find the right request, and then look through the contents. It would be much easier if there was a dedicated console in the UI that showed the outgoing/incoming requests/responses
@liyasthomas commented on GitHub (Nov 13, 2025):
Hoppscotch already has the console.log() feature. You can write your console log statements in pre-request or post-request scripts and send the request to execute them. The console logs will be displayed on a separate tab next to the Tests tab in the Response panel.
@pmondal-int commented on GitHub (Nov 13, 2025):
Sure but as I mentioned, this isn't just for console logs. We would like the ability to see the outgoing request so that we can confirm the variable values, and any auto-generated values were populated correctly.
Also the console logs only show up when the "Experimental Scripting Sandbox" is enabled. We can't ask our users to use an experimental feature just for the console logs.
@mmgfrcs commented on GitHub (Dec 25, 2025):
Or something like this
New Requestbutton for folder and collection #3687