News updates

Show HN: Sourceminder.org - token-efficient code search Hey HN, The code indexing tools released in December now have added capabilities (Rust, Perl support), better token efficiency, easier install method, and a website! The website has a wasm port of the query tool, qi, so you can try it out in the browser. Let me know what you think. Thanks! https://ift.tt/Rafs1Nv July 24, 2026 at 10:28PM

Show HN: Trifle – Open-source analytics that stores answers, not events Trifle is an open-source time-series analytics library that aggregates nested counters instead of storing raw events. All in the database you already have. After rebuilding it twice over 10 years, it now tracks ~1B events a day at my day job. It started in 2015 as my own Rails APM. I plugged into ActiveSupport::Notifications, got a few small users, and one bigger one whose scraping app broke everything. That sparked the core idea: aggregate counters into pre-defined time buckets, so a single write increments multiple buckets at once. The APM eventually faded away without much traction. Later in 2021 I needed analytics at my day job. Instead of going for something out there I revised the idea of Trifle as a more generic analytics library, borrowing some data warehouse ideas. First used Redis, then Postgres, eventually MongoDB. Hence why Trifle::Stats comes with multiple drivers that keep the DSL unified while storag...

Show HN: Setoku – Self-hosted knowledge server for AI agents hey hn, I wanted to share a side project we’ve been using and iterating at Hedgy for the past couple weeks. It’s our take on a self-hosted company brain that is powered entirely by our claude subscriptions. It includes a ClickHouse data lake for ingesting data and light knowledge infrastructure for storing knowledge about the data (e.g. this is how we count a user as active, check column X when determining LTV). This is exposed to our AI’s via MCP. No inference happens in setoku itself, it’s just a data tool you give your agent. The MCP encourages the AI to record gotchas and insights as it finds them and there’s a minimal admin interface for auditing and pruning knowledge [0]. I had been pretty impressed with claude code’s data analysis abilities on my local postgres, so I was excited to ship this capability to my non-technical teammates to use from claude.ai and cowork. They thought of way more things to do with it than I d...

Show HN: Millwright – Rust-based, self-hosted LLM router Hey HN, With the news of OpenRouter possibly being acquired and proliferation of hosted LLM routers (i.e. Ramp Router, Vercel’s AI Gateway), I saw the need for a self hosted solution focused on cost savings, transparency, and performance. So, I built an open sourced router with a simple CLI interface that can easily sit between coding agents and GenAI workloads. For the curious and lazy, at the moment, Millwright has the tools for, - Providers: OpenAI-compatible APIs, Anthropic, Amazon Bedrock - Routing: policy-controlled model roles (cheap, mid, frontier), cheapest healthy route selection - Protocols: OpenAI Chat Completions, Anthropic Messages, text and tool translation - Cache Affinity: role-scoped session lanes without serializing concurrent agent traffic - Spend Tracking: per-team costs, cache usage, model/provider mix, request traces - Cost Analysis: measured usage and modeled candidate economics (HTML, Markdown, JSON) - Re...

Show HN: PDF tools that run in the browser, no upload https://pdfcdf.com July 22, 2026 at 08:47PM

Show HN: CodeAlmanac – Karpathy-style codebase wiki from your conversations Hey HN! This is Divit from Almanac (YC S26). We built CodeAlmanac, a wiki for your coding agents that updates as you talk to them. It is open-source, local, and free. Here’s a demo: https://www.youtube.com/watch?v=XNQWV3TFBWM Your CC/Codex conversations contain a LOT of knowledge that is forgotten because it was never documented. People have their own methods of documenting their chats. We used to make Markdown files like MANUAL.md and DESIGN.md, and would prompt Claude to keep them updated. The problem is that these files quickly become outdated and messy, and there’s only so much you can put in a single file. So we set out to build CodeAlmanac. We wanted something that was 1) maintained automatically, 2) lived inside our repository, and 3) used our existing Codex/Claude Code subscriptions. CodeAlmanac maintains an almanac/ folder inside your repository. It contains connected Markdown pages that cover things...