Comment by voidixyn

Comment by voidixyn

Hi HN! I'd like to share a project I built called `glassbrain` — an intuitive way to see what your agent knows, for both humans and agents.

The idea came from a frustration with existing agent harnesses. Most harnesses keep piling on rules, workflows, and guidelines, forcing agents to act in a rigid order. But here's the thing: LLMs inherently possess all these concepts — what's missing is an intuitive way to spark them while keeping humans in control. And on the practical side, all those constraints don't fix the core problem either — as data grows, we still can't reliably tell what's going on inside the agent's head.

Sure, we can ask agents to write documents or produce arbitrary HTML artifacts. But at scale, we're stuck with two bad options: either wade through long, often poorly organized text, or bet on the agent's intelligence and let it run — which is what some have taken to calling "vibe coding."

> We say a lot, but understand very little.

What we need is a kind of "mind reading" for agents. Something the agent can plug into effortlessly while delivering high-bandwidth information the human brain can actually absorb. Something that gives us the most intuitive understanding with the least communication overhead. Something that lets us grasp what the agent knows, what it has designed, what it remembers, and how it all evolves over time — just like a glass brain.

----

`glassbrain` lets agents write their knowledge, plans, and memories as graphs, then delivers them to humans to inspect what's been expressed and how it's changed. It improves on two fronts:

*First, making it intuitive for LLMs to use.* Hooking into Neo4j or writing a pile of rules isn't the answer — because LLMs can already write files and understand graph structures perfectly well. They speak JSON fluently by nature. So I let the model write the graph as simple JSON files, with no unnecessary procedures or constraints. I only added targeted tools for things models struggle with, like a CLI to validate knowledge graph structures.

*Second, helping humans understand quickly — delivering massive bandwidth at a glance.* I looked for a long time but couldn't find a UI library that met my needs: displaying huge amounts of information without label overlap, using an elegant layout (ordinary force-directed layouts are just too messy), and showing how information changes between versions. `glassbrain` uses a custom cose-bilkent layout to arrange data based on containment relationships, making large datasets spread out organically. It features animated transitions between graphs, aligned diff views, support for massive graphs, and labels that arrange themselves without overlapping. It also includes multi-layer layouts, custom config, search, editing, and more — so you can literally dive into the agent's brain and play around.

----

This design is powerful across many scenarios, for example:

- *Manage what the model knows:* Use it for knowledge graph generation and management. Unlike domain-specific KG pipelines, glassbrain lets you bring your own knowledge-organizing ideas to adjust the scale and quality of the model's output. You can suggest the model build an outline around certain anchors and fill it in piece by piece, or dispatch subagents in parallel based on document volume to ensure detail coverage — the whole process is transparent. If you don't want to customize, `glassbrain` ships with built-in skills for documents and code. These skills are surprisingly short because they only need to point out the essential ideas rather than teach the model an entire language.

- *Manage what the model has designed:* Use it as a high-bandwidth view of agent documents — plans, READMEs, memories, or structural changes across versions. Before you say "go," you can spend far less time while having much greater confidence in the details of what the agent is about to do.

- *Manage what the model has delivered:* If you're tired of reading endless documents, just ask your agent to do the research as usual but tell it to include a `glassbrain` graph with the results.

There's a lot more to explore in the live demo… https://voidixyn.github.io/glassbrain/

Or you can just try it out. Usage is simple: in any context, just add "... using `npx glassbrain`." at the bottom of the prompt. It's skill-free and model-agnostic — almost any LLM agent can use it. A standalone HTML file will be returned.

Developers can also easily integrate it into their own apps as a React graph component.

*GitHub:* https://github.com/voidixyn/glassbrain

Replies voidixyn · 1h
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. Type a domain, or paste a link to block its site, and press Enter.

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 story above or below in the list, in the same article reader. Back returns to the story you came from.
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 Previous and Next buttons read up and 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, Previous and 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.