I've tried to use both Paw and Postman. Always ended up going back to HTTPie (https://github.com/jakubroztocil/httpie). It's much faster than clicking through a GUI, at least for basic requests (which is what 95% of requests are).
Don't get me wrong, Paw is a really nice app, but I don't feel that it rivals the productivity of bash-jitsu for most day-to-day use.
After trying to figure out why Postman was doing a double GET this morning on a coworker's computer, I finally told him to just install httpie. Took a little while but it's much easier to be explicit about a request. Bash command history does a lot of what these GUIs do.
You probably wanna tell the Postman team[0] about this. They are a bunch of helpful folks who are working very hard on building the product. They'll be glad to see the bug report.
Full disclosure: I interned with Postman for a short duration last year.
Maybe it was actually an OPTION/GET combination? In that case, it's actually useful that Postman is running in Chrome because it shares the same environment and constraints.
HTTPie is a CLI client, and I don't think it would make sense for it to save the requests you make (as opposed to a GUI). Though, it has a nice persistence feature with sessions (https://github.com/jakubroztocil/httpie#sessions).
It's the nice thing with GUIs (Paw, Postman...)! Paw saves all your work in ".paw" documents that you can share with your team on Dropbox or Git. You can have many documents, and organize your API calls.
Don't get me wrong, Paw is a really nice app, but I don't feel that it rivals the productivity of bash-jitsu for most day-to-day use.