<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: zawakin</title><link>https://news.ycombinator.com/user?id=zawakin</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 29 Apr 2026 23:04:47 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=zawakin" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by zawakin in "Why Japan has such good railways"]]></title><description><![CDATA[
<p>Japanese trains run on time not because of the tracks or the signaling. It's that any delay makes the total apology burden on station staff, conductors, and drivers grow exponentially. JR's timetabling is, in practice, an apology inflation containment policy.</p>
]]></description><pubDate>Sun, 19 Apr 2026 20:47:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=47827498</link><dc:creator>zawakin</dc:creator><comments>https://news.ycombinator.com/item?id=47827498</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47827498</guid></item><item><title><![CDATA[New comment by zawakin in "Show HN: Faceoff – A terminal UI for following NHL games"]]></title><description><![CDATA[
<p>Same — similar pile accumulating, and GitHub has fallen way behind. I keep going back and forth on whether a monorepo is the right answer or if it'd just make the sprawl more legible without actually helping. How are you organizing yours?</p>
]]></description><pubDate>Sun, 19 Apr 2026 19:37:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=47826997</link><dc:creator>zawakin</dc:creator><comments>https://news.ycombinator.com/item?id=47826997</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47826997</guid></item><item><title><![CDATA[New comment by zawakin in "Let's talk space toilets"]]></title><description><![CDATA[
<p>We can see how our daily lives are supported by public welfare</p>
]]></description><pubDate>Wed, 15 Apr 2026 13:26:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=47778669</link><dc:creator>zawakin</dc:creator><comments>https://news.ycombinator.com/item?id=47778669</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47778669</guid></item><item><title><![CDATA[Show HN: AgTrace – Observability for AI Coding Agents via MCP (Claude Code etc.)]]></title><description><![CDATA[
<p>AI agents are getting more capable, but we're increasingly in the dark
about what they're actually doing. They run complex multi-step workflows,
call dozens of tools, reason through problems - and we just watch the
output scroll by. It's a black box, and humans end up being led around
by the agent rather than understanding it.<p>I wanted to flip this. The key insight: all these agents (Claude Code,
Codex, Gemini) already write detailed logs. The problem is they're in
different locations, different formats, incompatible schemas.<p>agtrace normalizes this "observation layer" across providers:<p>- Auto-discovers logs from Claude, Codex, Gemini
- Converts them into a unified event timeline
- Exposes this via CLI, TUI dashboard, and MCP<p>The MCP part is what makes it interesting for agents themselves. An agent
can now query its own past sessions:<p>- "What approach did we take when we refactored auth last week?"
- "Show me errors from yesterday's session"
- "How did we handle this edge case before?"<p>This enables agent self-reflection - using execution history to inform
current decisions.<p>Built in Rust for safety and speed. 100% local, no cloud dependencies.
The database is just a pointer index to original logs - rebuilable anytime.<p>Happy to discuss the architecture or use cases.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46499885">https://news.ycombinator.com/item?id=46499885</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 05 Jan 2026 15:27:57 +0000</pubDate><link>https://github.com/lanegrid/agtrace</link><dc:creator>zawakin</dc:creator><comments>https://news.ycombinator.com/item?id=46499885</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46499885</guid></item><item><title><![CDATA[Show HN: Agtrace – top and tail -f for AI coding agent sessions]]></title><description><![CDATA[
<p>Hey HN,<p>I built agtrace because I kept losing track of what was happening in my Claude Code sessions – context pressure, tool calls, costs.<p>It's basically `top` for AI coding agents:
- Live dashboard showing context window usage and activity
- Session history you can query and diff
- Works with Claude Code, Codex, and Gemini CLI
- 100% local, reads existing logs, no cloud<p>Install: `npm i -g @lanegrid/agtrace`<p>The core idea is pointer-based indexing (no log duplication) and 
schema-on-read (resilient to provider schema changes).<p>Would love feedback, especially from heavy Claude Code / Codex users.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46425670">https://news.ycombinator.com/item?id=46425670</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 29 Dec 2025 21:05:05 +0000</pubDate><link>https://github.com/lanegrid/agtrace</link><dc:creator>zawakin</dc:creator><comments>https://news.ycombinator.com/item?id=46425670</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46425670</guid></item></channel></rss>