I never publish my "first_draft" branch - never.

Why does it matter. It's pretty normal to do a bunch of dev locally and then at some point create a public gh repo and then push

update: idk how I have positive points on my comment above

I wouldn’t make one like it again. simply because I really have no clue how long the author thought about their project

hell, another front page Show HN has a single commit

Devil's advocate, it could have been a bunch of squashed commits. I've done that when open-sourcing stuff from work, after making sure the code didn't have any stray references to work-related items.

back at peak Slop HN, there were a ton of these, the fastest I recall was a few minutes from first commit time to Slop HN time

example: https://news.ycombinator.com/item?id=47492202

I recall sub-10m, but don't care to search has any harder

I initially developed and tested it locally in my own scratch environment before pushing the first public release via the web UI. I've now pushed the full structured commit history so the progression is visible. Also just released v0.1.1 on PyPI (`pip install ghostman`).

Posting works well for making outbound HTTP requests; the only part it doesn't handle by default is locally capturing and replaying webhooks.

While testing TradingView alerts, exchange execution callback handlers, or cryptocurrency payment webhooks for our trading software, we always find ourselves running `posting` (or `curl`) in one terminal window while having an additional tunneling/receiving script running in another one just to catch and retransmit the tricky JSON payloads.

And it's in Go which makes for the better app experience.

Welcome, future person! Please give us good news about what will transpire since many of us are currently stuck on Halloween 2026. Thanks!

I'm excited for CLI/TUI since 2016. It's just easier to use and automate. Other than a web browser, all the software I spend significant time in are CLI/TUIs. This includes most image editing.

OpenAPI / Swagger import is high on my roadmap for v0.2.0! Being able to point to an OpenAPI spec and immediately populate collections in the terminal would be awesome.

That's an LLM README for you. They probably used the sentence "without electron" during development in some prompt and it ended up there

1) Sometimes you need to look at things yourself. You do verify the agent's work for important things, I hope? You've never seen them do mind-numbingly stupid things that warrant a bit scrutiny from time to time?

2) To me, Vim provides a normal UI. No slow, bloated, clunky, mousing, no slow Electron garbage, blegh. Just a quick, clean, lean UI.

I can relate to the part of your post where you have difference of opinion, but the apparent solipsism of not being able to understand why someone would want something different than you is the part of your post that drives me nuts. There are different people who like different things, is that not fairly straightforward to understand?

Like httpie? https://httpie.io/cli

I completely agree with you.

It even got to the point where I implemented my own Insomnia/Bruno alternative and I have been using it exclusively for months now. Because Bruno lacked some features I needed.

Last time I checked, Bruno implemented these features, but my version is still much faster and uses minimum resources in comparison (C++ and wxWidgets).

I don't see it the same way. People are building these things for themselves because it solves a specific problem they have, and that means it's crafted just to their liking. And it will only become easier to maintain these because of LLMs constantly advancing (for now). So if this is also a match for what you want out of a tool, then you can easily adopt it, or even fork it to your own liking. If it's not a fit for you, that's fine, there are plenty other options that may be.