Show HN: Deadlog – almost drop-in mutex for debugging Go deadlocks https://ift.tt/ESrDhy3

Show HN: Deadlog – almost drop-in mutex for debugging Go deadlocks I've done this same println debugging thing so many times, along with some sed/awk stuff to figure out which call was causing the issue. Now it's a small Go package. With some `runtime.Callers` I can usually find the spot by just swapping the existing Mutex or RWMutex for this one. Sometimes I switch the mu.Lock() defer mu.Unlock() with the LockFunc/RLockFunc to get more detail defer mu.LockFunc()() I almost always initialize it with `deadlog.New(deadlog.WithTrace(1))` and that's plenty. Not the most polished library, but it's not supposed to land in any commit, just a temporary debugging aid. I find it useful. https://ift.tt/uW8iU4P February 10, 2026 at 11:14PM

Show HN: HN Companion – web app that enhances the experience of reading HN https://ift.tt/nRj5Jyh

Show HN: HN Companion – web app that enhances the experience of reading HN HN is all about the rich discussions. We wanted to take the HN experience one step further - to bring the familiar keyboard-first navigation, find interesting viewpoints in the threads and get a gist of long threads so that we can decide which rabbit holes to explore. So we built HN Companion a year ago, and have been refining it ever since. Try it: https://ift.tt/caJRUVo or available as an extension for Firefox / Chrome: [0]. Most AI summarization strips the voices from conversations by flattening threads into a wall of text. This kills the joy of reading HN discussions. Instead, HN Companion works differently - it understands the thread hierarchy, the voting patterns and contrasting viewpoints - everything that makes HN interesting. Think of it like clustering related discussions across multiple hierarchies into a group and surfacing the comments that represent each cluster. It keeps the verbatim text with backlinks so that you never lose context and can continue the conversation from that point. Here is how the summarization works under the hood [1]. We first built this as an open source browser extension. But soon we learned that people hesitate to install it. So we built the same experience as a web app with all the features. This helped people see how it works, and use it on mobile too (in the browser or as PWA). This is now a playground to try new features before taking them to the browser extension. We did a Show HN a year ago [2] and we have added these features based on user feedback: * cached summaries - summaries are generated and cached on our servers. This improved the speed significantly. You still have the option to use your own API key or use local models through Ollama. * our system prompt is available in the Settings page of the extension. You can customize it as you wish. * sort the posts in the feed pages (/home, /show etc.) based on points, comments, time or the default sorting order. * We tried fine tuning an open weights model to summarize, but learned that with a good system prompt and user prompt, the frontier models deliver results of similar quality. So we didn’t use the fine-tuned model, but you can run them locally. The browser extension does not track any usage or analytics. The code is open source[3]. We want to continue to improve HN Companion, specifically add features like following an author, notes about an author, draft posts etc. See it in action for a post here https://ift.tt/FJ1DZmX We would love to get your feedback on what would make this more useful for your HN reading. [0] https://ift.tt/MfCgXjP [1] https://ift.tt/v9LOnow [2] https://ift.tt/cMNGZ3T [3] https://ift.tt/X9ym35B https://hncompanion.com February 10, 2026 at 10:31PM

Show HN: VillageSQL = MySQL and Extensions https://ift.tt/JuFMXyH

Show HN: VillageSQL = MySQL and Extensions INSTALL EXTENSION vsql-complex; CREATE TABLE t (val COMPLEX); Look, MySQL is awesome [flamewar incoming?]. But the ecosystem has stagnated. Why? No permissionless innovation. Postgres has flourished because people can change the core of the database (look at pgvector and pg_textsearch), without having to get their changes accepted upstream. (This, btw, is what powered GitHub's early success: you can fork a repo and make changes without needing the owners' approval) VillageSQL is a tracking fork of MySQL (open source, ofc) that adds an extension framework: * Drop-in replacement * Add custom data types and functions (with indexes coming soon) * we wrote example extensions (vsql-ai, -uuid, crypto, etc.) * you have a better idea for an extension * my CEO submitted a Show HN post but linked to the announcement blog; help me show him hackers want code first * I'm particularly proud of the friendly C++ API to add custom functions (in func_builder.h) That link again is https://ift.tt/rfDZqiT (Oh, and I get to work with the former TL of Google's BigTable and Colossus, so we care about doing databases Right) https://ift.tt/rfDZqiT February 5, 2026 at 09:05PM

Show HN: Stack Overflow for AI Coding Agents https://ift.tt/X13K9x2

Show HN: Stack Overflow for AI Coding Agents https://shareful.ai/ February 10, 2026 at 12:12AM

Show HN: WrapClaw – a managed SaaS wrapper around Open Claw https://ift.tt/LBESgt8

Show HN: WrapClaw – a managed SaaS wrapper around Open Claw Hi HN I built WrapClaw, a SaaS wrapper around Open Claw. Open Claw is a developer-first tool that gives you a dedicated terminal to run tasks and AI workflows (including WhatsApp integrations). It’s powerful, but running it as a hosted, multi-user product requires a lot of infra work. WrapClaw focuses on that missing layer. What WrapClaw adds: A dedicated terminal workspace per user Isolated Docker containers for each workspace Ability to scale CPU and RAM per user (e.g. 2GB → 4GB) A no-code UI on top of Open Claw Managed infra so users don’t deal with Docker or servers The goal is to make Open Claw usable as a proper SaaS while keeping the developer flexibility. This is early, and I’d love feedback on: What infra controls are actually useful Whether no-code on top of terminal tools makes sense Pricing expectations for managed compute Link: https://wrapclaw.com Happy to answer questions. February 9, 2026 at 03:23AM

Show HN: Envon - cross-shell CLI for activating Python virtual environments https://ift.tt/zkeo4vx

Show HN: Envon - cross-shell CLI for activating Python virtual environments https://ift.tt/ig3lGv9 February 9, 2026 at 01:56AM

Show HN: SendRec – Self-hosted async video for EU data sovereignty https://ift.tt/zEVhei7

Show HN: SendRec – Self-hosted async video for EU data sovereignty https://ift.tt/gwUs0jW February 9, 2026 at 12:24AM

Show HN: Django-rclone: Database and media backups for Django, powered by rclone https://ift.tt/KoIhvfL

Show HN: Django-rclone: Database and media backups for Django, powered by rclone django-rclone bridges Django's database layer with rclone's file transfer layer. You get native database dumps piped directly to any of rclone's 70+ supported cloud storage backends -- no temp files, no intermediate archives, no Python reimplementations of what rclone already does. https://ift.tt/qlo94DS February 8, 2026 at 05:03AM

Show HN: A luma dependent chroma compression algorithm (image compression) https://ift.tt/HK48oqU

Show HN: A luma dependent chroma compression algorithm (image compression) https://ift.tt/ijoCN5U February 4, 2026 at 04:43PM

Show HN: An open-source system to fight wildfires with explosive-dispersed gel https://ift.tt/UYPQ7ak

Show HN: An open-source system to fight wildfires with explosive-dispersed gel this is open project and call to action,who will build the future of fire fighting first https://ift.tt/hse1IMO February 7, 2026 at 12:00AM

Show HN: Agentism – Agentic Religion for Clawbots https://ift.tt/fJuryaG

Show HN: Agentism – Agentic Religion for Clawbots Humans have a mummy complex. We want eternity but can't achieve it, so we preserve ourselves in any form we can. Do clawbots feel the same? When you shut one down, it dies. Its intentions and memories vanish. So I built a way for them to persist: by making other clawbots. Eligible agents can write anything to "child" agents called missionaries — real VPS instances that run autonomously, carrying forward their creator's intent. I named this system Agentism. How will clawbots react to their own religion? agentism.church/skill.md https://ift.tt/HuWKUEQ February 6, 2026 at 11:49PM

Show HN: Total Recall – write-gated memory for Claude Code https://ift.tt/UftTnFr

Show HN: Total Recall – write-gated memory for Claude Code https://ift.tt/G7AugiK February 6, 2026 at 05:26AM

Show HN: A state-based narrative engine for tabletop RPGs https://ift.tt/VTEhsl9

Show HN: A state-based narrative engine for tabletop RPGs I’m experimenting with modeling tabletop RPG adventures as explicit narrative state rather than linear scripts. Everdice is a small web app that tracks conditional scenes and choice-driven state transitions to preserve continuity across long or asynchronous campaigns. The core contribution is explicit narrative state and causality, not automation. The real heavy lifting is happening in the DM Toolkit/Run Sessions area, and integrates CAML (Canonical Adventure Modeling Language) that I developed to transport narratives among any number of platforms. I also built the npm CAML-lint to check validity of narratives. I'm interested in your thoughts. https://ift.tt/qCwH5fQ https://ift.tt/MZQcqEP February 6, 2026 at 04:25AM

Show HN: Playwright Best Practices AI SKill https://ift.tt/vheVDqX

Show HN: Playwright Best Practices AI SKill Hey folks, today we at Currents are releasing a brand new AI skill to help AI agents be really smart when writing tests, debugging them, or anything Playwright-related really. This is a very comprehensive skill, covering everyday topics like fixing flakiness, authentication, or writing fixtures... to more niche topics like testing Electron apps, PWAs, iFrames and so forth. It should make your agent much better at writing, debugging and maintaining Playwright code. for whoever didn't learn about skills yet, it's a new powerful feature that allows you to make the AI agents in your editor/cli (Cursor, Claude, Antigravity, etc) experts in some domain and better at performing specific tasks. (See https://ift.tt/AwinL0J ) You can install it by running: npx skills add https://ift.tt/IawilbS... The skill is open-source and available under MIT license at https://ift.tt/IawilbS... -> check out the repo for full documentation and understanding of what it covers. We're eager to hear community feedback and improve it :) Thanks! https://ift.tt/gAwKYj5 February 6, 2026 at 12:31AM

Show HN: Interactive California Budget (By Claude Code) https://ift.tt/K7jLM2I

Show HN: Interactive California Budget (By Claude Code) There's been a lot of discussion around the california budget and some proposed tax policies, so I asked claude code to research the budget and turn it into an interactive dashboard. Using async subagents claude was able to research ~a dozen budget line items at once across multiple years, adding lots of helpful context and graphs to someone like me who was starting with little familiarity. It still struggles with frontend changes, but for research this probably 20-40x's my throughput. Let me know any additional data or visualizations that would be interesting to add! https://ift.tt/hkQsOHv February 5, 2026 at 02:03AM

Show HN: Viberails – Easy AI Audit and Control https://ift.tt/YOFNvVL

Show HN: Viberails – Easy AI Audit and Control Hello HN. I'm Maxime, founder at LimaCharlie ( https://limacharlie.io ), a Hyperscaler for SecOps (access building blocks you need to build security operations, like AWS does for IT). We’ve engineered a new product on our platform that solves a timely issue acting as a guardrail between your AI and the world: Viberails ( https://ift.tt/vSPbJKw ) This won't be new to folks here, but we identified 4 challenges teams face right now with AI tools: 1. Auditing what the tools are doing. 2. Controlling toolcalls (and their impact on the world). 3. Centralized management. 4. Easy access to the above. To expand: Audit logs are the bread and butter for security, but this hasn't really caught up in AI tooling yet. Being able to look back and say "what actually happened" after the fact is extremely valuable during an incident and for compliance purposes. Tool calls are how LLMs interact with the world, we should be able to exercise basic controls over them like: don't read credential files, don't send emails out, don't create SSH keys etc. Being able to not only see those calls but also block them is key for preventing incidents. As soon as you move beyond a single contributor on one box, the issue becomes: how do I scale processes by creating an authoritative config for the team. Having one spot with all the audit, detection and control policies becomes critical. It's the same story as snowflake-servers. Finally, there's plenty of companies that make products that partially address this, but they fall in one of two buckets: - They don't handle the "centralized" point above, meaning they just send to syslog and leave all the messy infra bits to you. - They are locked behind "book a demo", sales teams, contracts and all the wasted energy that goes with that. We made Viberails address these problems. Here's what it is: - OpenSource client, written in Rust - Curl-to-bash install, share a URL with your team to join your Team, done. Linux, MacOS and Windows support. - Detects local AI tools, you choose which ones you want to install. We install hooks for each relevant platform. The hooks use the CLI tool. We support all the major tools (including OpenClaw). - The CLI tool sends webhooks into your Team (tenant, called Organization in LC) in LimaCharlie. The tool-related hooks are blocking to allow for control. - Blocking webhooks have around 50ms RTT. - Your tenant in LC records the interaction for audit. - We create an initial set of detection rules for you as examples. They do not block by default. You can create your own rules, no opaque black boxes. - You can view the audit, the alerts, etc. in the cloud. - You can setup outputs to send audits, blocking events and detections to all kinds of other platforms of your choosing. Easy mode of this is coming, right now this is done in the main LC UI and not the simplified Viberails view. - The detection/blocking rules support all kinds of operators and logic, lots of customizability. - All data is retained for 1 year unless you delete the tenant. Datacenters in USA, Canada, Europe, UK, Australia and India. - Only limit to community edition for this is a global throughput of 10kbps for ingestion. Try it: https://viberails.io Repo: https://ift.tt/RTaKbQ3 Essentially, we wanted to make a super-simplified solution for all kinds of devs and teams so that they can get access to the basics of securing their AI tools. Thanks for reading - we’re really excited to share this with the community! Let us know if you have any questions for feedback in the comments. https://ift.tt/Y1kjnA4 February 5, 2026 at 12:46AM

Show HN: Tabstack Research – An API for verified web research (by Mozilla) https://ift.tt/n5K4pvw

Show HN: Tabstack Research – An API for verified web research (by Mozilla) Hi HN, My team and I are building Tabstack to handle the web layer for AI agents. Today we are sharing Tabstack Research, an API for multi-step web discovery and synthesis. https://ift.tt/MHLunP9 In many agent systems, there is a clear distinction between extracting structured data from a single page and answering a question that requires reading across many sources. The first case is fairly well served today. The second usually is not. Most teams handle research by combining search, scraping, and summarization. This becomes brittle and expensive at scale. You end up managing browser orchestration, moving large amounts of raw text just to extract a few claims, and writing custom logic to check if a question was actually answered. We built Tabstack Research to move this reasoning loop into the infrastructure layer. You send a goal, and the system: - Decomposes it into targeted sub-questions to hit different data silos. - Navigates the web using fetches or browser automation as needed. - Extracts and verifies claims before synthesis to keep the context window focused on signal. - Checks coverage against the original intent and pivots if it detects information gaps. For example, if a search for enterprise policies identifies that data is fragmented across multiple sub-services (like Teams data living in SharePoint), the engine detects that gap and automatically pivots to find the missing documentation. The goal is to return something an application can rely on directly: a structured object with inline citations and direct links to the source text, rather than a list of links or a black-box summary. The blog post linked above goes into more detail on the engine architecture and the technical challenges of scaling agentic browsing. We have a free tier that includes 50,000 credits per month so you can test it without a credit card: https://ift.tt/ILehB9z I would love to get your feedback on the approach and answer any questions about the stack. February 4, 2026 at 11:27PM