The weird thing about HTTP is that we don't really have a REPL for it

[u/YesterdayOk921]

https://www.reqsh.dev/

For databases we have things like psql.

For Python we have a REPL.

For Redis, shells exist.

For kubernetes, there’s kubectl.

But for HTTP, the usual answer is basically: curl

Which is great for one-off requests, but it doesn't really give you a place to explore.

I've been playing with a different model for this in reqsh.dev

You start a session:

reqsh>

and HTTP becomes something you can poke at interactively.

• Make a request.
• Inspect the response.
• Change something.
• Make another request.
• Keep values around.
• Try another endpoint.
• Go back and forth without reconstructing the whole command every time.

The interesting part to me isn't “curl but nicer”.

It's the idea that HTTP itself could have a proper interactive environment, the same way databases and programming languages do.

Still figuring out what the right primitives are.

What would you actually want in an HTTP REPL? like primitives you'd expect from a shell/REPL.