Love the idea. This would have been a game-changer in previous projects I've worked on.
Show HN: Stage CLI – An easier way of reading your AI generated changes locally
11–20 of 39 posts
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#12This feature exists already. It's called git.
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#13Minor nitpick: This isn't what I expected when I read "CLI". I envisioned a terminal-native experience. Unless I skimmed over this way too fast, this is a browser experience that you trigger from the terminal.
EDIT: I should mention that I think the idea is cool. We're in a new age where reviewing large amounts of unfamiliar code has become a larger problem than it was previously.
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#14Minor nitpick: This isn't what I expected when I read "CLI". I envisioned a terminal-native experience. Unless I skimmed over this way too fast, this is a browser experience that you trigger from the terminal. EDIT: I should mention that I think the idea is cool. We're in a new age where reviewing large amounts of unfamiliar code has become a larger problem than it was previously.
yep sorry about that, we weren't exactly sure what the best framing was
glad you like the idea though! let us know what you think
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#15Looks cool! Chapters is definitely something I've been angling towards as well. Any plans on going in the other direction (directly incorporating rich feedback/review into the agent loop through Stage)?
appreciate it! and yep, we've got lots of ideas on the roadmap to bring a more complete iteration experience closer to the coding agent. we've found it pretty silly that we have to push to GitHub in order to get comments from a review bot, pull them down locally, then rinse and repeat. the whole agentic coding landscape could benefit from some centralization
yeah, i definitely feel like we're currently in a very time-sparse model for review, when a lot of changes can be condensed locally. it'd reduce a lot of friction and also save a lot of compute costs if we were able to left-shift a lot of our current review work
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#16Minor nitpick: This isn't what I expected when I read "CLI". I envisioned a terminal-native experience. Unless I skimmed over this way too fast, this is a browser experience that you trigger from the terminal. EDIT: I should mention that I think the idea is cool. We're in a new age where reviewing large amounts of unfamiliar code has become a larger problem than it was previously.
I mean it’s quite literally a command line interface to their tool… what else should it be called that differentiates it from a pure browser flow?
What you are describing sounds more like “TUI” than “CLI” imo. A CLI is an interface—it’s about the input step. It makes no promise about what happens after that.
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#17Interested to try this! Have you thought about separating the parts of a PR that are routine/uninteresting from the parts that are load-bearing and need more careful review?
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#18Interested to try this! Have you thought about separating the parts of a PR that are routine/uninteresting from the parts that are load-bearing and need more careful review?
yes! we've found that reading changes this way make it very easy to separate the important stuff from the unimportant stuff, and we're thinking of ways to make that more visible in the UI
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#19Minor nitpick: This isn't what I expected when I read "CLI". I envisioned a terminal-native experience. Unless I skimmed over this way too fast, this is a browser experience that you trigger from the terminal. EDIT: I should mention that I think the idea is cool. We're in a new age where reviewing large amounts of unfamiliar code has become a larger problem than it was previously.
I mean it’s quite literally a command line interface to their tool… what else should it be called that differentiates it from a pure browser flow? What you are describing sounds more like “TUI” than “CLI” imo. A CLI is an interface —it’s about the input step. It makes no promise about what happens after that.
While you are not factually incorrect, my expectations were subverted in the same way that OOP's were.
Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally
#20This looks useful. With AI generated code the hardest part is reviewing it.
A normal git diff gets messy once the agent changes several files for different reasons. Grouping the change into “chapters” seems like the right idea.
Do you infer those chapters only from the diff, or can you also use the agent’s original plan/task history?