shipped v0.3.0 of reqsh today
been slowly building this CLI because i wanted something that makes curl requests less annoying.
it’s still pretty rough and there’s probably a lot i’m doing wrong.
curious how other people approach this problem. do you use something similar? or is this solving a problem that doesnt really exist for you?
would appreciate any feedback.
Link: reqsh.dev
I got tired of paper trading apps that just replay charts and instantly fill every order.
So I built paperdrill.dev
It's basically a paper trading exchange with a live order book and an actual matching engine behind it.
No KYC.
No deposits.
No real money.
Just a place to test ideas without pretending fills magically happen.
Still early, but it's finally at the point where other people can break it.
Would love feedback, especially from people who've built trading systems or exchanges before.
I'm a student and I've been building a exchange from scratch mainly to learn backend engineering.
Matching engine, order book, WebSockets, Redis, PostgreSQL... all the usual stuff.
The thing I'm stuck on now isn't technical.
I don't know whether I should keep building it as "just another exchange" for learning or try solving a smaller problem that traders or developers actually have.
If you were building this today, where would you focus?
Not looking for startup ideas or billion-dollar businesses. Just curious what problems are still worth solving around trading.
I'm a student and I've been building a exchange from scratch mainly to learn backend engineering.
Matching engine, order book, WebSockets, Redis, PostgreSQL... all the usual stuff.
The thing I'm stuck on now isn't technical.
I don't know whether I should keep building it as "just another exchange" for learning or try solving a smaller problem that traders or developers actually have.
If you were building this today, where would you focus?
Not looking for startup ideas or billion-dollar businesses. Just curious what problems are still worth solving around trading.
I'm a student and I've been building a exchange from scratch mainly to learn backend engineering.
Matching engine, order book, WebSockets, Redis, PostgreSQL... all the usual stuff.
The thing I'm stuck on now isn't technical.
I don't know whether I should keep building it as "just another exchange" for learning or try solving a smaller problem that traders or developers actually have.
If you were building this today, where would you focus?
Not looking for startup ideas or billion-dollar businesses. Just curious what problems are still worth solving around trading.
I'm a CS student building a centralized exchange project mostly to learn system design and backend engineering.
Initially it was just another portfolio project but now I'm wondering if I can actually build something people would want to use.
So instead of guessing, I thought I'd just ask.
What's one thing that annoys you about exchanges like Binance, Bybit, Coinbase, OKX, etc.
Could be anything:
Been working on a small side project for the last few months called reqsh.
The idea started because I was constantly jumping between curl commands, Postman, editing headers, copying tokens, changing base URLs... it just felt more annoying than it should.
So I ended up building a terminal-first HTTP REPL where you stay in one interactive session. You can save base URLs, keep headers around, use variables, organize requests and just experiment without rewriting the same command over and over.
It's written in Rust and still pretty early, but people have started opening PRs which has been really cool to see.
Not trying to replace every API client out there. I just wanted something that fits the terminal workflow better.
I'd genuinely love some feedback from people who spend a lot of time working with APIs. What's missing? What feels awkward? Or is there something you wish tools like this did better?
GitHub: https://github.com/hars-21/reqsh
Website: https://www.reqsh.dev/
Been working on a small side project for the last few months called reqsh.
The idea started because I was constantly jumping between curl commands, Postman, editing headers, copying tokens, changing base URLs... it just felt more annoying than it should.
So I ended up building a terminal-first HTTP REPL where you stay in one interactive session. You can save base URLs, keep headers around, use variables, organize requests and just experiment without rewriting the same command over and over.
It's written in Rust and still pretty early, but people have started opening PRs which has been really cool to see.
Not trying to replace every API client out there. I just wanted something that fits the terminal workflow better.
I'd genuinely love some feedback from people who spend a lot of time working with APIs. What's missing? What feels awkward? Or is there something you wish tools like this did better?
GitHub: https://github.com/hars-21/reqsh
Website: https://www.reqsh.dev/
Still building reqsh.
Shipped more fixes and improvements since last post.
It’s a Rust-based HTTP REPL, interactive API testing with sessions, history, vars, autocomplete, pretty JSON.
Need real feedback from people who do API work.
Try it.
Break it.
Tell me what sucks.
Site: https://www.reqsh.dev/
Github repo: https://github.com/hars-21/reqsh (Give a star if you like it)
Still building reqsh.
Shipped more fixes and improvements since last post.
It’s a Rust-based HTTP REPL, interactive API testing with sessions, history, vars, autocomplete, pretty JSON.
Need real feedback from people who do API work.
Try it.
Break it.
Tell me what sucks.
Site: https://www.reqsh.dev/
Github repo: https://github.com/hars-21/reqsh (Give a star if you like it)
Hey everyone,
A while back I shared reqsh, a small Rust-based HTTP REPL I built. Since then I've added Windows support and release binaries, so it's a lot easier to try now.
The idea is basically an interactive curl-like shell with session state, history, tab completion, variables and pretty JSON responses.
Just looking for people who do a lot of API work and are willing to try it, break it and tell me what's annoying or missing. I'm still figuring out what users actually need.
Any feedback is appreciated.
Github repo (Give it a star if you like it)
Hey everyone,
A while back I shared reqsh, a small Rust-based HTTP REPL I built. Since then I've added Windows support and release binaries, so it's a lot easier to try now.
The idea is basically an interactive curl-like shell with session state, history, tab completion, variables and pretty JSON responses.
Just looking for people who do a lot of API work and are willing to try it, break it and tell me what's annoying or missing. I'm still figuring out what users actually need.
Any feedback is appreciated.
Github repo (Give it a star if you like it)
Hey everyone,
A while back I shared reqsh, a small Rust-based HTTP REPL I built. Since then I've added Windows support and release binaries, so it's a lot easier to try now.
The idea is basically an interactive curl-like shell with session state, history, tab completion, variables and pretty JSON responses.
Just looking for people who do a lot of API work and are willing to try it, break it and tell me what's annoying or missing. I'm still figuring out what users actually need.
Any feedback is appreciated.
Github repo (Give it a star if you like it)
Hey everyone,
A while back I shared reqsh, a small Rust-based HTTP REPL I built. Since then I've added Windows support and release binaries, so it's a lot easier to try now.
The idea is basically an interactive curl-like shell with session state, history, tab completion, variables and pretty JSON responses.
Just looking for people who do a lot of API work and are willing to try it, break it and tell me what's annoying or missing. I'm still figuring out what users actually need.
Any feedback is appreciated.
Github repo (Give it a star if you like it)
I've been working on backend projects recently and found myself constantly jumping between curl, Postman, browser docs, and terminal windows.
Mostly as a learning project, I started building a small tool called reqsh.
The idea is simple: Instead of repeatedly typing curl commands, you open a shell and interact with APIs from a REPL.
Current features:
{{name}} syntax in paths, headers, and bodyparam: key=value linesIt's still very early and I'm mostly looking for feedbacks.
What's the first feature that would stop you from using something like this?
GitHub: https://github.com/hars-21/reqsh (Star the repo for regular updates)
Website: https://reqsh.vercel.app/
Hey folks
Lately I’ve noticed more devs moving away from Postman mostly because it feels bloated and not very Git-friendly.
At the same time, tools like curl are great but not really built for collaboration or structured workflows.
So I’ve been thinking about building something new:
Before I start building, I’d love some honest feedback:
Also curious if you’ve tried tools like Bruno, HTTPie, or Hoppscotch? how was your experience?
Trying to validate whether this is a real problem or just my own itch
Appreciate any thoughts!
Hey folks
Lately I’ve noticed more devs moving away from Postman mostly because it feels bloated and not very Git-friendly.
At the same time, tools like curl are great but not really built for collaboration or structured workflows.
So I’ve been thinking about building something new:
Before I start building, I’d love some honest feedback:
Also curious if you’ve tried tools like Bruno, HTTPie, or Hoppscotch? how was your experience?
Trying to validate whether this is a real problem or just my own itch
Appreciate any thoughts!
Hey folks
Lately I’ve noticed more devs moving away from Postman mostly because it feels bloated and not very Git-friendly.
At the same time, tools like curl are great but not really built for collaboration or structured workflows.
So I’ve been thinking about building something new:
Before I start building, I’d love some honest feedback:
Also curious if you’ve tried tools like Bruno, HTTPie, or Hoppscotch? how was your experience?
Trying to validate whether this is a real problem or just my own itch
Appreciate any thoughts!