The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Watch a neural net learn to play Snake
In browser PPO training demo, made possible by tinygrad: TinyJit -> WebGPU kernels.<p>Requires WebGPU.
Show HN: Watch a neural net learn to play Snake
In browser PPO training demo, made possible by tinygrad: TinyJit -> WebGPU kernels.<p>Requires WebGPU.
Show HN: Watch a neural net learn to play Snake
In browser PPO training demo, made possible by tinygrad: TinyJit -> WebGPU kernels.<p>Requires WebGPU.
Show HN: Watch a neural net learn to play Snake
In browser PPO training demo, made possible by tinygrad: TinyJit -> WebGPU kernels.<p>Requires WebGPU.
Show HN: Find the best local LLM for your hardware, ranked by benchmarks
Show HN: Rotunda - A browser built for agents with simulated typing
Hi HN! Pierce here.<p>Rotunda is a firefox fork primarily intended for agent use, which I’ve been hacking on nights/weekends.<p>There was a [lengthy](<a href="https://news.ycombinator.com/item?id=48024859">https://news.ycombinator.com/item?id=48024859</a>) discussion last week on how expensive computer use models are. The cost is going to drop eventually, but I think on some level it's still usually the wrong primitive. The web gives us access to beautiful structured formats, plaintext, etc... why throw that away if we don't have to?<p>I realized at some point that for 99% of automations I just want agents to be able to control my Chrome instance. But that’s easier said that done: CDP (the Chrome automation protocol) leaks a ton of state about being programmatically controlled, either by toggling window attributes or by running `page.evaluate()` commands right in the page context. Plus if you look at an automation running it's pretty obvious what happens: the mouse jumps around, fields are filled instantly, etc.<p>Rotunda tries to fix this. Its standout features:<p>- Realistic simulation of mouse movements and keyboard commands, powered by a trained RNN on my own timing patterns from the last week. (still feel weird about opting-in to a key logger but whatever)<p>- Doesn’t lie about its host specs, only fibs about some client side details. Stealth browsers are too easy to flag statistically when you’re adding noise to canvas pixels or audio pipelines.<p>- It runs on your local device with a CLI or Playwright API accessible to Claude, Codex, or whatever your harness-de-jure today looks like.<p>- Patches modern Firefox (150) with an agentic harness to keep this updated over time<p>MPL-2.0 on GitHub: <a href="https://github.com/monkeysee-ai/rotunda" rel="nofollow">https://github.com/monkeysee-ai/rotunda</a><p>Longer writeup on the design choices: <a href="https://pierce.dev/notes/a-browser-for-agents" rel="nofollow">https://pierce.dev/notes/a-browser-for-agents</a><p>Also check out the demo on the site! <a href="https://www.rotunda.sh/" rel="nofollow">https://www.rotunda.sh/</a><p>Pretty excited by how this turned out but we’re still super early. Give it a try and please flag any issues!
Show HN: Nibble
An attempt at a single pass LLVM frontend in ~3000 lines of C without external dependencies, malloc, or an AST. Included are some graphical examples. The IR isn't perfect, and the README touches on one particular downfall
Show HN: Nibble
An attempt at a single pass LLVM frontend in ~3000 lines of C without external dependencies, malloc, or an AST. Included are some graphical examples. The IR isn't perfect, and the README touches on one particular downfall
Show HN: Nibble
An attempt at a single pass LLVM frontend in ~3000 lines of C without external dependencies, malloc, or an AST. Included are some graphical examples. The IR isn't perfect, and the README touches on one particular downfall
Show HN: Nibble
An attempt at a single pass LLVM frontend in ~3000 lines of C without external dependencies, malloc, or an AST. Included are some graphical examples. The IR isn't perfect, and the README touches on one particular downfall
Show HN: Running the second public ODoH relay
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
Show HN: Running the second public ODoH relay
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
Show HN: Running the second public ODoH relay
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
Show HN: Running the second public ODoH relay
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
Show HN: Running the second public ODoH relay
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
Show HN: I asked AI to write Sci-Fi for eternity
Show HN: Torrix, self hosted, LLM Observability,(no Postgres, no Redis)
I work as a SAP Integration consultant and built this as a side project. Friction point: Most self hosted LLM observability tools require Postgres, Redis and non trivial infrastructure. Teams just want to see what their agents are actually doing in Production, that set up cost discorages adoption.
Torrix runs as a single docker contained backed by SQLite. The full install is:<p>curl -o docker-compose.yml <a href="https://raw.githubusercontent.com/torrix-ai/install/main/doc" rel="nofollow">https://raw.githubusercontent.com/torrix-ai/install/main/doc</a>... docker compose up<p>No external dependencies. All data stays in a local SQLite file on your machine.<p>It logs LLM calls through a HTTP proxy or a python/Node SDK : tokens, cost, latency, full prompt and response traces, reasoning token capture. Works with OpenAI, Anthropic, Gemini, Groq, Mistral, Azure Open AI and any Apen AI compatible end point.<p>Things I added as I actually used it on real agent pipelines: cost forecasting and hard budget caps, PII masking, model routing rules, evals with golden runs, AI judge, a prompt library with version history, run tags for filtering by environment, MCP server so AI Assistants can query your own logs and OTLP/HTTP ingestion for apps aöready using OpenTelemetry.<p>Community edition is free for one user with 7-day retention. Pro adds teams, RBAC, 30 day retention, API key management, full text search and audit logs.<p>SQLite doesn't scale to high write throughput. This is aimed at teams logging hundreds to low thousands of LLM calls per day, not millions. Happy to hear what people think and what is missing.<p>GitHub / install: <a href="https://github.com/torrix-ai/install" rel="nofollow">https://github.com/torrix-ai/install</a> Website: <a href="https://www.torrix.ai" rel="nofollow">https://www.torrix.ai</a>
Show HN: Torrix, self hosted, LLM Observability,(no Postgres, no Redis)
I work as a SAP Integration consultant and built this as a side project. Friction point: Most self hosted LLM observability tools require Postgres, Redis and non trivial infrastructure. Teams just want to see what their agents are actually doing in Production, that set up cost discorages adoption.
Torrix runs as a single docker contained backed by SQLite. The full install is:<p>curl -o docker-compose.yml <a href="https://raw.githubusercontent.com/torrix-ai/install/main/doc" rel="nofollow">https://raw.githubusercontent.com/torrix-ai/install/main/doc</a>... docker compose up<p>No external dependencies. All data stays in a local SQLite file on your machine.<p>It logs LLM calls through a HTTP proxy or a python/Node SDK : tokens, cost, latency, full prompt and response traces, reasoning token capture. Works with OpenAI, Anthropic, Gemini, Groq, Mistral, Azure Open AI and any Apen AI compatible end point.<p>Things I added as I actually used it on real agent pipelines: cost forecasting and hard budget caps, PII masking, model routing rules, evals with golden runs, AI judge, a prompt library with version history, run tags for filtering by environment, MCP server so AI Assistants can query your own logs and OTLP/HTTP ingestion for apps aöready using OpenTelemetry.<p>Community edition is free for one user with 7-day retention. Pro adds teams, RBAC, 30 day retention, API key management, full text search and audit logs.<p>SQLite doesn't scale to high write throughput. This is aimed at teams logging hundreds to low thousands of LLM calls per day, not millions. Happy to hear what people think and what is missing.<p>GitHub / install: <a href="https://github.com/torrix-ai/install" rel="nofollow">https://github.com/torrix-ai/install</a> Website: <a href="https://www.torrix.ai" rel="nofollow">https://www.torrix.ai</a>
Show HN: E2a – Open-source email gateway for AI agents
We were building an agent system and wanted email as a trigger. We decided to take it out and made it a standalone service.<p>The primary email features we wanted and used for our own agent system:<p>1. Email threading stays consistent with agent conversation threading<p>2. Human in the loop review for outbound emails (especially during testing phase)<p>3. Quick onboarding/offboarding email addresses for agents within minutes<p>4. Websocket for local agents and at-least-once webhook delivery for Cloud agents<p>Not yet: DMARC (only SPF/DKIM today), scoped API keys, HA/multi-region (single VM + single Postgres), app-layer email data encryption, compliance attestations (SOC 2/HIPAA).<p>GitHub: <a href="https://github.com/Mnexa-AI/e2a" rel="nofollow">https://github.com/Mnexa-AI/e2a</a><p>Hosted: <a href="https://e2a.dev/" rel="nofollow">https://e2a.dev/</a><p>Appreciate any feedback / contributions.