Stories

Comment by pnezis

Comment

Comment by pnezis

Hi HN, author here.

Agents can now do real work on their own: they review pull requests, draft emails, write documents and generate images. The hard part is no longer getting the work done, but reviewing it well before it is used.

Pinrail is a desktop app for that review. The agent submits what it made and waits. You see it in a view made for that kind of content, such as comments on a diff, a set of draft emails or an image you can mark up, and you decide item by item. The agent then continues with your decision.

I built it because I kept approving agent work in the worst possible place: a terminal scrollback. When the agent drafted twelve review comments for a pull request, I either let it post all of them or argued about them one by one in chat. Neither worked well, so I had the agent write its comments into a custom HTML page that showed them on the diff. There I could accept some, reject others with a reason, edit one, and hand the whole decision back at once. That page worked so well that I wanted the same for everything else my agents asked me about, and that is how Pinrail started.

It works like this. In the agent's instructions you name the steps that need a person, for example "before posting review comments, submit them to Pinrail and wait". When the agent reaches that step, it runs:

    pinrail submit code-review --title "Dedup tickets on save" --data proposals.json --wait
The review appears in the app's inbox and you get a notification. You decide in a view made for that kind of content. The command then prints your decision as markdown, or as JSON with `--json`, and exits with a code that says how the review ended. If you ask for changes, the agent sends a new round with `--revises`, and the app shows your previous verdicts next to it. If you discard a review, the command exits 5 and the agent stops the work the review was gating.

Some details:

- It works with any agent that can run a command: Claude Code, Codex, Cursor, OpenCode, Gemini CLI, or a CI job. The app can install a skill that teaches the agent how to submit and wait. - Each kind of review is a plugin: a manifest, two JSON Schemas (what the agent sends and what comes back) and an HTML view, which runs in a sandboxed iframe. The app comes with plugins for lists, questions, code review, images and markdown documents. Others cover emails, calendars, HTML pages, logos and 3D models. `pinrail plugins new` creates your own. - Everything is local. The app runs its server on 127.0.0.1, stores reviews in SQLite, and has no account and no telemetry. - It is built with a Rust core, Tauri and React. It runs on macOS and Linux. Windows is planned. - It is free and open source under Apache 2.0.

It is early, and I expect rough edges.

Site and downloads: https://pinrail.dev Docs: https://pinrail.dev/docs/

Replies pnezis · 20h
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.