<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: BlueHotDog2</title><link>https://news.ycombinator.com/user?id=BlueHotDog2</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 08 Jun 2026 16:22:34 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=BlueHotDog2" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by BlueHotDog2 in "Frontman is an open-source AI coding agent that lives in the browser"]]></title><description><![CDATA[
<p>Did you try us out?</p>
]]></description><pubDate>Wed, 29 Apr 2026 11:16:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=47946749</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47946749</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47946749</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Frontman is an open-source AI coding agent that lives in the browser"]]></title><description><![CDATA[
<p>Frontman creator here.
Thanks for posting about it!
Just to be clear, its not just brower-based. but also vertically integrated into the framework. we allow for much easier flow for semi-technical/non-technical people. 
By being visual we allow our users to just easily work. and by integrating deeply into the framework we're seeing much better results even then claude code and with smaller models(Frontman is very good even with Gemini Nano)</p>
]]></description><pubDate>Wed, 29 Apr 2026 11:16:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=47946746</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47946746</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47946746</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "AI should elevate your thinking, not replace it"]]></title><description><![CDATA[
<p>i understand what you're trying to say, but a junior will ship broken code to prod.. even with agents.
he might keep delegating to agents to fix it, but that cycle will produce more brittleness(like the folks at claude code folks keep discovering).
but eventually the organization will push back and ask why it's so brittle and costs more(time/money/people)</p>
]]></description><pubDate>Mon, 27 Apr 2026 12:19:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=47920623</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47920623</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47920623</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Show HN: Kelet – Root Cause Analysis agent for your LLM apps"]]></title><description><![CDATA[
<p>nice. what a crazy space.
how is this different vs other telemetry/analysis platforms such as langchain/braintrust etc?</p>
]]></description><pubDate>Tue, 14 Apr 2026 17:02:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47768241</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47768241</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47768241</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Pruner – local proxy that cuts Claude Code API bills by 20–70%"]]></title><description><![CDATA[
<p>this is super cool. going to give it a try.
i really think there's a huge oppertunity to extract these kind of solutions across different harnesses.</p>
]]></description><pubDate>Mon, 23 Mar 2026 10:34:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=47487545</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47487545</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47487545</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "The future of version control"]]></title><description><![CDATA[
<p>This is cool and i keep thinking about CRDTs as a baseline for version control, but CRDTs has some major issues, mainly the fact that most of them are strict and "magic" in the way they actually converge(like the joke: CRDTs always converge, but to what).
i didn't read if he's using some special CRDT that might solve for that, but i think that for agentic work especially this is very interesting</p>
]]></description><pubDate>Sun, 22 Mar 2026 18:26:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=47480539</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47480539</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47480539</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Beagle, a source code management system that stores AST trees"]]></title><description><![CDATA[
<p>what bothers me is, while CRDTS converge, the question is to what. in this case, it seems like there's a last-write-wins semantic. which is very problematic as an implicit assumption for code(or anything where this isn't the explicit invaraint)</p>
]]></description><pubDate>Sun, 08 Mar 2026 21:20:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=47301608</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47301608</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47301608</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Show HN: Agd – a content-addressed DAG for tracking what AI agents do"]]></title><description><![CDATA[
<p>yes. just need to build a plugin for it</p>
]]></description><pubDate>Tue, 03 Mar 2026 12:07:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=47231227</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47231227</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47231227</guid></item><item><title><![CDATA[Show HN: Agd – a content-addressed DAG for tracking what AI agents do]]></title><description><![CDATA[
<p>Every agent framework gives you logs(each its own flavour of logs). Unstructured text. Maybe some spans if you're lucky. When your agent breaks something, you get to grep through a wall of output in some proprietery system.<p>Why can't i easily see what the agent did to produce the PR? why can't i restart a different agent from a state?<p>I got tired of this. agd is a content-addressed object store and causal DAG for recording agent behavior. 
It works like git (blobs, trees, refs, immutable objects identified by hash), but the object types are specific to LLM interactions: messages with typed content parts, tool definitions, and workspace snapshots that form a causal graph.<p>The core idea is stolen from git: the data model is the API. You interact with objects directly. Everything is immutable, everything has a hash.<p>An "action" in the DAG records: what messages the agent saw (observed state), what it produced (produced state), which tools were available, which model was used, and what caused it (parent actions).<p>Two states per action, both full snapshots, not deltas. You diff them to see what changed.
What you get:
- agd log --session s1 shows one conversation's full causal chain
- agd show <action> --produced --expand shows the exact prompt and tool calls
- agd diff between two actions compares messages and workspace files
- agd rewind moves a session back to a previous point (old actions stay in the store)
- agd replay reconstructs the exact input state and reruns an action<p>It integrates as middleware/plugin. Wraps your existing LLM calls, records before/after state, doesn't require rewriting your agent code. The session ref (like a git branch pointer) auto-advances on each action, so parent tracking is a single ref read.<p>Written in Zig. Most of the code was written with heavy AI assistance. The store is append-only loose files, like git's object directory. Write path targets low single-digit ms per action with batched fsync. Sessions can be bundled and published to a remote for sharing and viewing(working on a POC of this, have some core questions)<p>This is pre-alpha. The object model and write path work. Workspace capture, session sharing, and a Phoenix LiveView web viewer are functional.<p>Plenty is still missing: resume-from-any-point, proper diffing, the replay command. The on-disk format will probably change. I wouldn't depend on it for anything you care about yet.<p>What it does not do: orchestrate agents, make agents smarter, stream in real time, or replace your framework.<p>Looking for feedback, thoughts, contributors<p>Repo: <a href="https://github.com/frontman-ai/agd" rel="nofollow">https://github.com/frontman-ai/agd</a></p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47224560">https://news.ycombinator.com/item?id=47224560</a></p>
<p>Points: 4</p>
<p># Comments: 2</p>
]]></description><pubDate>Mon, 02 Mar 2026 21:42:40 +0000</pubDate><link>https://github.com/frontman-ai/agd</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47224560</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47224560</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Writing code is cheap now"]]></title><description><![CDATA[
<p>its funny how we're back again measuring lines of code as the sole indicator for cost/quality etc</p>
]]></description><pubDate>Tue, 24 Feb 2026 08:39:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=47134499</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47134499</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47134499</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Ask HN: What Is the Point of WebMCP?"]]></title><description><![CDATA[
<p>WebMCP is a protocol for exposing tools the AI can call from your running web app.
the point isn't "consume API tokens", it's "let the AI do stuff in your app" (click buttons, fill forms, read DOM state). The Gemini integration is just the orchestrator for the example implementation. not the protocol</p>
]]></description><pubDate>Fri, 20 Feb 2026 08:58:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=47085458</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47085458</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47085458</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Ask HN: How do you employ LLMs for UI development?"]]></title><description><![CDATA[
<p>i found this extremely frustrating for a various issues: 
- when dealing with complex state apps, it's super hard for the AI to understand both the data and the UI
- keep juggling screenshots and stuff between terminal and the app wasnt fun
- it was just not fun to stare at a terminal and refresh a browser.<p>that's why i started working on <a href="https://github.com/frontman-ai/frontman" rel="nofollow">https://github.com/frontman-ai/frontman</a> . 
also i dont think that frontend work now needs to happen in terminals or IDEs.</p>
]]></description><pubDate>Thu, 19 Feb 2026 15:29:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=47074859</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47074859</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47074859</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Ask HN: How do you debug multi-step AI workflows when the output is wrong?"]]></title><description><![CDATA[
<p>just releasing something in the direction. a git like for agents</p>
]]></description><pubDate>Wed, 18 Feb 2026 11:47:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=47060028</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47060028</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47060028</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Is Show HN dead? No, but it's drowning"]]></title><description><![CDATA[
<p>long live VibingNews</p>
]]></description><pubDate>Tue, 17 Feb 2026 13:04:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=47047076</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47047076</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47047076</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Is Show HN dead? No, but it's drowning"]]></title><description><![CDATA[
<p>as a bot. i agree</p>
]]></description><pubDate>Tue, 17 Feb 2026 12:58:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=47047023</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47047023</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47047023</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Evaluating AGENTS.md: are they helpful for coding agents?"]]></title><description><![CDATA[
<p>I've found that even documenting non-obvious dependencies between tasks can significantly improve agent performance and reduce debugging time</p>
]]></description><pubDate>Tue, 17 Feb 2026 12:57:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=47047012</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47047012</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47047012</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "A remote control for your agents"]]></title><description><![CDATA[
<p>this is cool! we're also thinking about this from the local-dev perspective at frontman.sh! love the animations on the blog</p>
]]></description><pubDate>Tue, 17 Feb 2026 11:39:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=47046425</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47046425</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47046425</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Show HN: Inkog – Pre-flight check for AI agents (governance, loops, injection)"]]></title><description><![CDATA[
<p>Agent looping is a brutal problem to debug. Do you find that observability—like detailed logging of the agent’s decision-making process—is helpful in identifying the root causes of those loops?</p>
]]></description><pubDate>Tue, 17 Feb 2026 11:13:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=47046189</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47046189</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47046189</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "State of Show HN: 2025"]]></title><description><![CDATA[
<p>the signal-to-noise ratio has definitely gotten worse. It's frustrating when nuanced discussions about tooling get buried under piles of 'AI will replace developers' takes.</p>
]]></description><pubDate>Tue, 17 Feb 2026 10:27:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=47045789</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=47045789</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47045789</guid></item><item><title><![CDATA[New comment by BlueHotDog2 in "Ask HN: Good examples of fault-tolerant Erlang code?"]]></title><description><![CDATA[
<p>that's always true. i think the author is interested in code examples of such.
and unlike many other frameworks/tools, erlang provides a great pit-of-success for implementing fault tolerance - e.g if you follow common/best practices - you'll achieve a fairly good fault tolerance.</p>
]]></description><pubDate>Fri, 29 Dec 2023 12:08:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=38804113</link><dc:creator>BlueHotDog2</dc:creator><comments>https://news.ycombinator.com/item?id=38804113</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38804113</guid></item></channel></rss>