Stories

Comment by mattm

Comment

Comment by mattm

Your other comment is flagged as dead so I'll reply here:

> I like the idea of using a “local inbox for agent sessions” because switching between different contexts can be more frustrating than the actual time it takes the agent to run.

> But I’m curious about how you see the inbox being useful beyond simply storing and replaying conversations.

> A few things would help me understand the practical value:

> What does a session actually contain? Is it just the conversation, or does it also include things like prompts, code changes, test results, Git commits, and other context? Can you reliably replay a session? Ideally, someone should be able to see what task was given, what the agent changed, what tests were run, and whether the task actually passed. What happens when work gets interrupted? If I pause one task and start another, can I come back later without losing the context or putting the project into a confusing state? How do you prove the work was completed? For example, can the system show the tests that were run, the changes made, and whether they passed? How is everything kept safe? If everything runs locally, that's great, but I'd still want to know how filesystem, network access, and logs are controlled.

> Even a small example showing something like how long it takes to go from starting a task to getting a working result, compared with the current workflow, would make the benefits much easier to understand.

---

Thanks for the questions! I like your suggestion about providing a small example. I'll put that together. Email me at matt@alcubi.ai and I will send it to you when it's ready. In the meantime, this page from the documentation may help to provide some of the details you're looking for https://alcubi.ai/delegator/docs/dev/concepts/ticket-lifecyc...

A session includes the scoped task request (ticket) and the code changes that are made on a separate git branch in a new worktree. You can enter the agent session at anytime with the "dg chat" command. That will allow you to look into the details of how the agent accomplished its work. So even though the runs execute in the background, the agent session is always available if you want to jump into it. I'll use this command when something was unclear to ask for follow-up changes. The agent will still have all the context in its session from the work it previously did so there's no extra context loading needed in these case.

If works gets interrupted, the ticket status moves to the Failed inbox. You'll see that clearly from the output of the "dg" command which shows the various inboxes. When this happens I'll use "dg chat" to attach to the agent session to understand what went wrong. Usually, this is something like the Claude/Codex API being down. When the API is back up, I run "dg restart" to restart the processing from where it left off. Since all work is done in separate branches and worktrees there's no ability for your project's main branch to be left in a confusing state.

The agents will run your test suite that's setup. delegator is just the orchestration layer. You can customize any steps you'd like the agents to follow via your AGENTS.md file. That will be taken into account when the agents run. So for example, you could add in your AGENTS.md file that for any delegator ticket they work on to include details in the commit of tests that were run. It's very flexible like that so you can customize it for your setup.

For safety, I've gotten to the point where I trust that agents are only accessing data that they need so there are currently no guardrails in place. This is something you could add to your AGENTS.md file to get information about but that's not deterministic. I could add in features to support this. Please email me at my email above to let me know a bit more about what you'd like to see and I can work on that.

Hope this helps and thanks for taking a look!

Replies mattm · 1d
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.