Friday, July 31, 2026

Show HN: Schema-backed, Git-based structured state for agentic systems https://ift.tt/IGiveSU

Show HN: Schema-backed, Git-based structured state for agentic systems I looked into how to store agentic state in a) a structured way that b) runs without any dedicated MCP memory/state servers and where I can get c) a clear diff-able audit trail of all state changes over time. Nothing that I could find fit the bill. In https://ift.tt/7yZsGvC , I demo an implementation that fulfills these requirements by combining Claude agents with my previously published Commitspark library and its entirely Git-backed GraphQL API. In the demo, two independent Claude agents are simulated that contribute to a task tracker. A third agent reviews any task changes and rolls back obviously bad ones. A full demo transcript is included in the README, including the agents' raw tool calls. Task agent access to data happens via a small MCP server that exposes two Commitspark APIs (GraphQL API, schema API). These agents can then fetch the schema and author their own GraphQL calls, with GraphQL automatically enforcing written data is schema-conformant. The validator agent additionally has access to basic git functionality to view diffs and revert commits. I'm looking for feedback specifically on: whether schema validation on shared agent state is a problem people actually have, or whether loosely-typed JSON + retries is good enough in practice. July 31, 2026 at 11:50PM

Thursday, July 30, 2026

Show HN: Tally – check a spreadsheet's numbers against their source, in-browser https://ift.tt/ldaTcY2

Show HN: Tally – check a spreadsheet's numbers against their source, in-browser https://ift.tt/ArN3yGW July 30, 2026 at 11:25PM

Wednesday, July 29, 2026

Show HN: Capitolisation – Trade like the bests elected officials https://ift.tt/Mv4KWb5

Show HN: Capitolisation – Trade like the bests elected officials Elected officials tend to overperform S&P500. The goal is to show disclosures to detect trends. https://ift.tt/M39fFmI July 30, 2026 at 12:22AM

Show HN: Dreeve, a self-hosted dashboard for your sports and fitness data https://ift.tt/WGr3ewB

Show HN: Dreeve, a self-hosted dashboard for your sports and fitness data I've been building this for a few years under the name "Statistics for Strava" but I renamed it to Dreeve recently because of Strava's recently changed API usage terms. They paywalled their API. You point it at your activity files (FIT/TCX/GPX) or connect a Strava account, and it gives you a dashboard with segment efforts, gear and maintenance tracking, a heatmap, monthly calendar view, milestones and a year-in-review. It runs as a Docker container, stores everything in SQLite, and nothing leaves your machine. Stack is PHP 8.5 + Symfony, SQLite, Docker Compose. Simple, straightforward and fast. Caveats: it's built around a single user, so there's no multi-tenant story. The AI workout assistant is optional and off unless you configure it. Segment data still comes from Strava if you want it, which is the one dependency I haven't been able to remove. Docs at https://docs.dreeve.app . Happy to answer any questions you have https://ift.tt/QLfPK7N July 29, 2026 at 11:45PM

Tuesday, July 28, 2026

Show HN: Vyne – Zapier for DeFi users, run from any LLM or the workflow builder https://ift.tt/CzBkAEQ

Show HN: Vyne – Zapier for DeFi users, run from any LLM or the workflow builder https://ift.tt/O3SEb4U July 29, 2026 at 02:31AM

Show HN: Verifiable receipts for firmware CVE reproduction https://ift.tt/gadnSR1

Show HN: Verifiable receipts for firmware CVE reproduction https://ift.tt/sx7NQR4 July 29, 2026 at 02:23AM

Show HN: Beakdown – a game inspired by Joust/Skirmish https://ift.tt/cvUr6yi

Show HN: Beakdown – a game inspired by Joust/Skirmish I used to play Joust with my little brother on the BBC Micro many moons ago and have fond memories of it. So when I was experimenting with Claude Opus 5 it was a nice inspiration for this game. Did a little research and found there aren't many games out there that just work in a browser without ads, loading screens or account sign-ups. So I've put this directly on the landing page with no noise in the way - it works on any browser on any device and loads instantly. If it doesn't work at all, please tell me. And also let me know if you think it needs music - I went without it to begin with but don't know if that's what people would prefer or not. Would also love to know how far you get, my personal best is 199,000. Thanks for your interest! https://beakdown.fun/ July 29, 2026 at 01:18AM

Show HN: Somebodyhire.me https://ift.tt/AehqwyL

Show HN: Somebodyhire.me I originally had this as a personal resume site but decided to build it out into a platform where anyone can sign up and host a resume page. Once I build up the talent pool, I plan on marketing to hr depts and hiring managers. I just don't know a single person who's happy with hiring on either side right now and this feels like a better solution to me. https://ift.tt/sOjNXqV July 28, 2026 at 09:48PM

Monday, July 27, 2026

Show HN: A 538-style dashboard for upcoming Knesset elections https://ift.tt/2OtMzAY

Show HN: A 538-style dashboard for upcoming Knesset elections https://ift.tt/svDOfIh July 28, 2026 at 12:34AM

Show HN: Let's Seal – Let's Encrypt for document signing, free and self-hosted https://ift.tt/u9gxpiK

Show HN: Let's Seal – Let's Encrypt for document signing, free and self-hosted TLDR, Let's Seal gives the finger to Adobe and every doc signing tool (docusign, google, etc) who pay to play with the Adobe Approved Trust List and then charge you for something that should be free. Currently even the person checking if a document/contract is sealed or code is authentic has to also be inside the same Adobe walled garden too. Verification, the part that should be free is the part everyone charges for. Thats the shape Let's Encrypt fixed for TLS, and I wanted the same thing for documents and files. The core idea therefore needed to go a bit beyond e signatures and i created an open standard (SEAL), plus free tools that implement it. When you seal a file, three independent things happen. 1. it gets a signature from a certificate authority, chaining to a public root. 2. its record is appended to an RFC 6962 transparency log. and 3. its SHA256 is timestamped on a public blockchain (Bitcoin) via OpenTimestamps. Those three give you integrity, transparency and a timestamped proof. And importantly, none of those depend on Let's Seal and none are gated. You can verify with the tools you already have, no Let's Seal account and no Let's Seal software. A sealed PDF carries a standard PAdES signature, so any PDF reader validates it. A sealed build artefact carries a cosign compatible signature and a SLSA provenance attestation. The Bitcoin timestamp verifies with stock ots. 3 ways to use it. 1. The free web app. We kindly have backing from Backblaze to cover storage costs for the foreseeable. So you can upload or issue any number of documents, get a public proof page at /d/ and verify it at https://ift.tt/t6eJ5uT for free. Multiple accounts, multiple seats, enterprise functions. Free. 2. Self host the whole thing. Apache-2.0, one Next.js app plus a signing service that holds the CA key on localhost. Storage is any S3-compatible bucket or local disk. If you'd rather run your own root of trust, you can. 3. Programmatically. via the CLI and a hosted API. This is the Let's Encrypt/certbot angle. Seal or anchor things from CI, or have a backend seal every invoice or report as its generated. The CLI is sealbot. It runs anywhere Node runs (npx sealbot) and there are native binaries for macOS, Linux and Windows with no runtime needed. Theres a GitHub Action wrapping the same tool, so a release workflow can seal its own artifacts. Its what proves our own releases. KYC is semi-handled (to a degree) it's hard to do for free (at least for now), but issuers (your companies or websites) domains can be authenticated with a DNS record added, which proves the issuer has control over a domain. Sign-in can be authenticated to an email via Google Sign in and a few others will be added to the web app in time (Same as Docusign currently). Ideas welcome on future KYC should there be a demand. Feedback welcome on the standard (SPEC.md in the repo). Repo: https://ift.tt/0qnys49 Site: letsseal.org Thx https://ift.tt/0qnys49 July 27, 2026 at 09:22PM

Sunday, July 26, 2026

Show HN: An interactive way to exploit an LLM without going to jail https://ift.tt/bzysJhP

Show HN: An interactive way to exploit an LLM without going to jail https://ift.tt/gabhQ2y July 26, 2026 at 11:46PM

Saturday, July 25, 2026

Show HN: Minesweeper Raycasted https://ift.tt/ENRjokt

Show HN: Minesweeper Raycasted https://ift.tt/HscpO7K July 26, 2026 at 01:09AM

Show HN: Bribes.fyi – Know before you go. New feature added https://ift.tt/IXtW5m6

Show HN: Bribes.fyi – Know before you go. New feature added https://ift.tt/zv0shDQ July 26, 2026 at 12:36AM

Show HN: I made some transistor animations https://ift.tt/WxwQtjh

Show HN: I made some transistor animations Hi HN, I made some animations of the most important kinds of transistors using my semiconductor simulation, details of which are on the page. I tried to make the visuals as realistic as possible while also aiming for clarity. If you want to go beyond the charge carriers and look at, for example, the electric field, you can do so in the simulation software. The desktop software also has less common devices like IBGTs and SCRs that have similar animations. The last thread about my software was posted here about a year ago: https://ift.tt/mv2GXz8 https://ift.tt/57dc0rG July 25, 2026 at 12:07AM

Friday, July 24, 2026

Show HN: Sourceminder.org - token-efficient code search https://ift.tt/1FeXwuU

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/i41sOrm July 24, 2026 at 10:28PM

Show HN: A representation of a chapter of your life through music https://ift.tt/7zYZJxF

Show HN: A representation of a chapter of your life through music https://www.cuecard.live July 24, 2026 at 11:22PM

Thursday, July 23, 2026

Show HN: Advanced Coffee Search Covering Over 17,000 coffees https://ift.tt/CPTDxJH

Show HN: Advanced Coffee Search Covering Over 17,000 coffees https://ift.tt/gA0G7Ni July 24, 2026 at 02:59AM

Show HN: Notebooker.ai – NotebookLM alternative, your own models, keys, storage https://ift.tt/T6MyYGV

Show HN: Notebooker.ai – NotebookLM alternative, your own models, keys, storage Hi HN. This is a personal side project I've been building for about six months on top of the open-source Open Notebook platform ( https://ift.tt/c4hCWuU ). Notebooker saves the stuff you'd otherwise lose in tabs and bookmarks - links, PDFs, audio, video - and makes it useful later: chat with a notebook and get answers that cite the exact source, turn a reading list into a podcast episode (private RSS feed, works in any player), or generate study material from your own sources. The part I've had the most fun with is a plugin engine for creation types - flashcards, charts, infographics, mindmaps, textbooks, essays, slideshows, timelines, wikis are each plugins, and new ones can be added without touching the core. Everything I've built on top of open-notebook has either been submitted upstream as PRs or is open source at https://ift.tt/0nJiTMx . Decisions this crowd might care about: - Bring your own AI keys (OpenAI, Anthropic, local/OpenAI-compatible endpoints) or use the built-in defaults. I enjoy testing Cloudflare Worker AI models. Nothing you save is used for training. You can deploy you own OpenAI compatible endpoint to play with at https://ift.tt/tgq5Lcz - Bring your own S3-compatible storage (R2, Spaces, AWS) if you want your files in a bucket you control. - Webhooks in and out — anything that can POST JSON can trigger a workflow, and workflows can POST anywhere. Notebook also processes incoming RSS feeds and generates its own - Export everything or delete your account with a click. There's a view-only demo notebook at https://ift.tt/Qvh7Tau . Happy to answer any questions. I'm expecting some hiccups in releasing, feel free to report bugs or feedback. https://notebooker.ai/ July 24, 2026 at 12:32AM

Show HN: Trifle – Open-source analytics that stores answers, not events https://ift.tt/y0navJd

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 storage layer changes with your needs. In our case (huge write volume, some reads) PG read faster but slowed on large writes. The nested values are the whole trick here. Single: Trifle::Stats.track( key: 'requests::aws::s3_uploads', values: { count: 1, status: { request.response_code => 1 }, size: payload.bytes, duration: { sum: request.duration, count: 1 } } ) builds up counts for requests, success rate, result status codes, duration for multiple time buckets at once. Single bucket from 2am then looks like: { count: 14, status: { 200: 12, 500: 2 }, size: 5628341, duration: { sum: 43, count: 14 } } If request.duration is in seconds, then sum stored under duration would be in seconds as well. Success rate is never stored, but it is calculated by dividing 200s over total number of requests. Same with average duration: sum over count. You ask for a metrics key, granularity and timeframe and you get back aggregated values at each point. Ready for charts or to answer "Average response time over last 30 days". There's a Series wrapper for aggregating and formatting values for charts in a simple call. And as building dashboards is not as much fun for other devs as I thought, I built Trifle App - a visual layer with dashboards, scheduled digests and alerts. It's written in Elixir, so I ported the library to Elixir too. And later to Go for a CLI. All three are compatible, write in one and read in another. Today we track activity from over 100M background jobs a day which turns into about 1B events. It runs surprisingly cheap when you're willing to trade some safety away (turn off journaling and write concerns in Mongo). 3-node Hetzner MongoDB cluster where the primary does 20% utilization costs us around $1k/month. It has its limitations. Payloads can't hold tens of thousands of keys. Documents becomes too large to update efficiently. Some planning ahead is needed. And then there are no dimensions. Sometimes you can nest them (country - there are only so many countries), sometimes it's better to have dedicated metrics key per dimension (customer - growing forever). That multiplies tracked events, hence 1B events from 100M jobs. The libraries are MIT. The App is source-available under ELv2 - free to self-host and paid cloud if you want it managed. I build this on the side with no investor money to burn on a free service. Happy to answer anything about architecture, storage models, my failures or why I didn't give up on this yet. https://trifle.io/ July 22, 2026 at 08:09PM

Wednesday, July 22, 2026

Show HN: Szr: A safer command output reduction for coding agents https://ift.tt/O3YZVnJ

Show HN: Szr: A safer command output reduction for coding agents https://ift.tt/fJjg1T4 July 22, 2026 at 11:33PM

Show HN: Onus – self-hostable vuln scanner combining 8 tools into one report https://ift.tt/S9q0ZRD

Show HN: Onus – self-hostable vuln scanner combining 8 tools into one report https://ift.tt/sn0IrxT July 22, 2026 at 10:24PM

Tuesday, July 21, 2026

Show HN: Edky, a CLI to convert Ed25519 public keys from one encoding to another https://ift.tt/eNCfMsu

Show HN: Edky, a CLI to convert Ed25519 public keys from one encoding to another Everything increasingly runs on Ed25519 keypairs, but Ed25519 public keys can be encoded as text in dozens of surface-incompatible different ways: hexadecimal, Base64 (OpenSSH), Base32z (iroh, pkdns), Base58 (NEAR), and Multibase (IPFS, libp2p), just for starters. Edky is a command-line tool and Rust library that converts between these Ed25519 surface encodings, aiding use of the same underlying keypair across e.g. an iroh endpoint, a libp2p peer, or a NEAR Protocol account. (Surprisingly, a conversion utility like this didn't yet exist!) $ cargo binstall -y edky $ edky convert -f iroh -t libp2p 47pjoycnsrfmxikm95jh13y88e8qnhzu5kungjpxyepgt7a8krpy z6MktwupdmLXVVqTzCw4i46r4uGyosGXRnR3XjN4Zq7oMMsw $ edky convert -f libp2p -t iroh z6MktwupdmLXVVqTzCw4i46r4uGyosGXRnR3XjN4Zq7oMMsw 47pjoycnsrfmxikm95jh13y88e8qnhzu5kungjpxyepgt7a8krpy $ edky convert -f near -t hex ed25519:FVen3X669xLzsi6N2V91DoiyzHzg1uAgqiT8jZ9nS96Z d75a980182b10ab7d54bfed3c964073a0ee172f3daa62325af021a68f707511a $ edky convert -f hex -t near d75a980182b10ab7d54bfed3c964073a0ee172f3daa62325af021a68f707511a ed25519:FVen3X669xLzsi6N2V91DoiyzHzg1uAgqiT8jZ9nS96Z https://ift.tt/h3ldwkR July 21, 2026 at 11:39PM

Monday, July 20, 2026

Show HN: A free lever-based puzzle game https://ift.tt/0sFR4mO

Show HN: A free lever-based puzzle game I made Lever Labyrinth for a final project in my uni's game engine development class and recently ported it to the browser. Check out today's daily! You can then share your result here. Enjoy :) https://ift.tt/24eDJcX July 20, 2026 at 11:20PM

Sunday, July 19, 2026

Saturday, July 18, 2026

Friday, July 17, 2026

Show HN: Tools Berry – client-side calculators with open-source tax engines https://ift.tt/5iaDhlr

Show HN: Tools Berry – client-side calculators with open-source tax engines https://ift.tt/BGUQ2YR July 18, 2026 at 01:08AM

Show HN: Lific: Issue trackers should be simple, right? https://ift.tt/RvzZE4q

Show HN: Lific: Issue trackers should be simple, right? I built Lific because I direct AI coding agents on largish projects and needed somewhere for project state to live that isn't markdown files in the repo. When I was begging to work on long horizon ideas, I started on Linear, but my agent files issues faster than a human does, and I hit their limits and pricing wall almost immediately. Then I self-hosted a popular open source tracker which meant running its 13 containers, and its MCP integration was 30k tokens and I got so fed up that I eventually removed it and went back to .md files for a few weeks. Lific is the opposite shape of most of your self hosted server issue trackers: It's a single Rust binary that uses SQLite, and it has an optimized MCP server built in. Web UI is also included integrated directly into the binary. The simplicity is meant to only apply to the size and the ease of installation. The web UI is fully fleshed out with all of the UX you would expect from an issue tracker like linear. Since I started using lific, my agent flow is that I open the web UI, find a few issues I want to work on, then tell the agent "work on LIF-298, 299 and 301, and if you find bugs, file them as new issues." At the end of the day the project has tracked itself. Issues have statuses, blockers, and comment threads, so "what's workable right now" is a query instead of the agent guessing. Plans are persisted step trees, so a session tomorrow resumes with the same understanding of the goal and the path as the session that made the plan. My largest project has 300+ issues and 100+ docs and agents search it fast. Everything exports to markdown in one click, and the database is just a file on your machine. Setup is ` cargo install ` ` lific init ` ` lific connect ` then pick your harness (OpenCode, Cursor, Claude Code, etc). One honest caveat: on Windows there's no service install yet, so the binary has to be actively running for MCP or Web UI to work on windows. The biggest reason I think Lific is different than a lot of the other options is the lightweight nature of it alongside still having a fully featured web UI. It's meant for self hosters to work on big projects with agents, without sacrificing the other benefits of an issue tracker like a nice management UI or authentication for teams using it. Would genuinely love feedback and bug reports either here or on the discord! https://lific.dev July 17, 2026 at 11:22PM

Show HN: A zoomable timeline of 4M Wikipedia events https://ift.tt/W43rTsh

Show HN: A zoomable timeline of 4M Wikipedia events I'm building a journal app in Kotlin Multiplatform and for this purpose I have created a zoomable timeline interface. This is a side-project where I reuse the timeline interface to display 4 million events imported from Wikipedia / Wikidata, scored using PageRank. There is more information on the about page. If you're interested in the stack: I use Kotlin Multiplatform extensively, with Compose Multiplatform for the UI, communicates with the backend using Kotlinx-RPC and behind the hood a simple Postgres database on a Hetzner machine. https://ift.tt/Kt0ELrF July 18, 2026 at 12:07AM

Thursday, July 16, 2026

Wednesday, July 15, 2026

Show HN: SirixDB 1.0 Beta – Git-Like Versioning, Diffs, Time-Travel Queries https://ift.tt/QtL03yg

Show HN: SirixDB 1.0 Beta – Git-Like Versioning, Diffs, Time-Travel Queries Hi HN! I've posted SirixDB here before, back in 2019 ( https://ift.tt/zC9iYH5 ) and again in 2023 ( https://ift.tt/ZDBYbMh ). The core idea behind SirixDB is, that history is a first-class citizen. Every commit stores a lightweight, queryable revision. You can query any point in time, even individual nodes (for instance JSON values), diff arbitrary revisions, and efficiently track how data evolved without replaying events. Unlike traditional event stores, historical states do not need to be reconstructed by replaying events nor do we have to think about projections. Revisions are directly queryable. A simple example: Jan 1: Record "Price = $100, valid from Jan 1". Stored on Jan 1 (transaction time). Jan 20: Discover price was actually $95 on Jan 1. Commit correction. After correction, you can ask across both axes: - "What did we THINK the price was on Jan 16?" -> $100 (Transaction time) - "What WAS the price on Jan 1?" -> $95 (Valid time) I've worked on this in my spare time since 2013, following its academic precursor (Idefix/Treetank) at the University of Konstanz. The architecture relies on an append-only physical log and a persistent copy-on-write page trie. A high level view of the architecture: Physical Log (append-only, sequential writes) ┌────────────────────────────────────────────────────────────────────────┐ │ [R1:Root] [R1:P1] [R1:P2] [R2:Root] [R2:P1'] [R3:Root] [R3:P2'] ... │ └────────────────────────────────────────────────────────────────────────┘ t=0 t=1 t=2 t=3 t=4 t=5 t=6 → time Each revision is indexed, and unchanged pages are shared: [Rev 1] [Rev 2] [Rev 3] │ │ │ ▼ ▼ ▼ [Root₁] [Root₂] [Root₃] │ │ │ │ │ │ │ └─────────┐ │ └────────┐ │ └─────────┐ ▼ ▼ ▼ ▼ ▼ ▼ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ │ P1 │ │ P2 │ │ P1' │ │ P2' │ └──────┘ └──────┘ └──────┘ └──────┘ Rev 1 Rev 1+2 Rev 2+3 Rev 3 (shared) (shared) Beneath the root pages sit node and secondary indexes, using a novel sliding-snapshot algorithm to balance read/write performance. Everything is queryable using JSONiq via the Brackit compiler. Back in 2019, and even in 2023, SirixDB was very slow due to GC pressure. Unlike most other document stores, SirixDB stores fine-grained nodes, and I came to realize that an on-heap (JVM) representation made up of lots of small objects simply didn't make sense. I measured it with async-profiler — with some help from Andrei Pangin himself — and the result was that the poor throughput was due to the sheer amount of allocations which scaled almost linearly with the number of open transactions. Working a full-time software engineering job, I lacked the energy for a massive spare-time rewrite. About a year ago, I started experimenting with AI. It turned out to be ideal for automating the tedious, repetitive parts of migrating the storage layer to Java's Foreign Function & Memory API, storing pages completely off-heap. Looking further ahead, the append-only, immutable-page design maps naturally onto object storage like S3 and distributed logs like Kafka for a cloud version, and initial prototypes already exist. Maybe that becomes a commercial service one day, but for now, I'm just thrilled to see these core design principles finally proven out.There's an interactive demo, documentation, and the code is on GitHub. I'd love feedback and am happy to answer questions! kind regards Johannes [1] https://sirix.io | https://ift.tt/oSpkYFK [2] https://ift.tt/mkRXVPH [3] https://demo.sirix.io [4] https://sirix.io/docs/ [5] http://brackit.io https://ift.tt/oSpkYFK July 15, 2026 at 09:16PM

Show HN: Make senders work to get into your inbox https://ift.tt/JPmu5lj

Show HN: Make senders work to get into your inbox Hi HN :) really excited to share this with you. The one thing AI reliably does is generate noise. Half the tools I see launch are just machines for producing more noise across more channels. And people are starting to see this in the form of emails in their inboxes as spam filters are struggling. There used to be a useful signal in email: the effort a sender put into customizing a message was a rough proxy for how relevant it actually was. AI killed that. Now it's customized slop with the appearance of effort with none of the cost. It is painful that the open internet / open channels have been abused like this. Captchainbox applies the idea of proof-of-work to email. If a sender is willing to do a bit of work to reach you, the message is more likely to be worth your time and the sender more likely to be real. The work is a traditional captcha. You can also set a pay-to-deliver amount if you want more friction. The proceeds of the delivery payment after transaction costs go to the Internet Archive and the EFF. The tool currently works by authing with your Gmail or Outlook and during launch time I make this completely free as a lifetime deal (with optional payment if you wanna support). How it works: Captchainbox builds a whitelist automatically from the metadata of your past correspondence. If you've emailed an individual address, that sender can reach you. If you talk to several people at the same domain, we whitelist the whole domain. If one transactional-looking sender has sent you more than 10 emails, we treat it as a transactional domain and let it through. This whitelist is for you to change whenever you want. It continues to build organically as you converse with more addresses. Incoming mail is checked against that whitelist. Senders already on it land in your inbox as normal. Anyone else gets archived (never deleted) and is sent a challenge. This can be the captcha or the payment link. Once they solve it, their email is pulled out of the archive and put back into your inbox. if you want to see what this looks like from a sender's point of view, send me an email here: doerpfelix15@gmail.com The service only ever reads metadata, never message content. And since nothing is ever deleted, you can't lose a message. There is a legitimate risk / downside: if you sign up to a new service, these emails also land in the archive. Since we do not process the content, a first-time sender who can't solve the challenge (say an automated activation email) will sit in your archive until you spot it. Happy to answer anything! :) https://ift.tt/H8LMXhy July 15, 2026 at 05:28PM

Tuesday, July 14, 2026

Show HN: Beautiful Type Erasure with C++26 Reflection https://ift.tt/ATvd1Bg

Show HN: Beautiful Type Erasure with C++26 Reflection Try it on Compiler Explorer: https://ift.tt/GwqjAO1 Check out the source code: https://ift.tt/1XYixrZ https://ryanjk5.github.io/posts/rjk-duck/ July 14, 2026 at 06:10PM

Show HN: A device for never missing the surf turned into something more https://ift.tt/l5RZmbd

Show HN: A device for never missing the surf turned into something more https://ift.tt/6Zxp82S July 15, 2026 at 12:42AM

show hn: 1d data to 3D topology, AI deepfakes to protien folding https://ift.tt/3eyuTk2

show hn: 1d data to 3D topology, AI deepfakes to protien folding https://ift.tt/lsnkdgN July 14, 2026 at 10:59PM

Monday, July 13, 2026

Sunday, July 12, 2026

Saturday, July 11, 2026

Show HN: Sqlsure – deterministic semantic checks for AI-generated SQL https://ift.tt/JEs9V5w

Show HN: Sqlsure – deterministic semantic checks for AI-generated SQL https://ift.tt/NldYnZh July 12, 2026 at 01:33AM

Show HN: Don't let your engineering brain rot in the age of AI https://ift.tt/Zrb9htl

Show HN: Don't let your engineering brain rot in the age of AI https://ift.tt/Qb5W687 July 12, 2026 at 01:27AM

Show HN: Share and explore custom Claude Code status lines https://ift.tt/k5XF4vZ

Show HN: Share and explore custom Claude Code status lines Hey HN, I made a registry for claude code users to share and explore status lines. I found that my friends/coworkers and I would always share screenshots of our terminal to show off our custom claude lines so I decided to build this registry as a place for others to show off! https://claudelines.com July 12, 2026 at 01:21AM

Friday, July 10, 2026

Show HN: We beat Cloudflare's bot detection (open-source stealth browser) https://ift.tt/HShwGuJ

Show HN: We beat Cloudflare's bot detection (open-source stealth browser) https://ift.tt/FcQBoLy July 11, 2026 at 05:56AM

Show HN: SubjectiveZero, an open-source agentic node editor for creative coding https://ift.tt/eh25oz0

Show HN: SubjectiveZero, an open-source agentic node editor for creative coding Hey there, My name is Clem, I've been a solo indie dev for a couple years now, exploring frontier tech like XR and agentic workflows in the context of creative / interactive work. I've been building creation tools for a while and some common design challenge is to figure out the right level of abstraction for your tool. You can always make it super advanced and complex with low level concepts (shader composition, actual code etc.) but then you get something with a high complexity / learning curve. On the other hand, if you make your tool too high level, it might be easier to use at first, but people will most likely hit a wall eventually and start fighting with your tool to get their edge case done (you see that on mobile a lot actually). With this prototype (called SubjectiveZero), I'd like to imagine that we can kind of move the "slider" on the abstraction layer, meaning that you can actually start with prompts that describe the goal, and you can go as high level (stay with abstract prompts) or low level as you'd like (more specific prompts, or even edit the generated code directly)! The agent orchestration actually understand your context and work along side with you to figure out what could be the best node graph structure for your project (that and some fun little procedural UI done at the node level). If i had to pitch it in 30 seconds, I'd say "Think TouchDesigner and friends but with agent orchestration". When you use it, it will generate real native code (Swift/Metal for now) that you can actually hot reload and iterate on either manually or through agents. It's still an early prototype and macOS only for now, but I'd love to get genuine feedback that could help me drive where this project should go next (or not). Lastly, I'm absolutely open and upfront on the fact that I used agentic coding for this, but as people say: "kept on a short leash". The architecture and specs were relatively well thought out and I personally prefer to be in the loop and review all the code being written to make sure it's going in the right direction. Oh and it's open source :-) Hope you like it! https://ift.tt/tk1WEIv https://ift.tt/tk1WEIv July 10, 2026 at 08:53PM

Show HN: Wyrm – Solve algebra by touch, built on an open-source soundness engine https://ift.tt/iFQolm8

Show HN: Wyrm – Solve algebra by touch, built on an open-source soundness engine There is a mobile game called DragonBox. It sort of tricks you into learning algebra by starting with very abstract manipulations of a puzzle that must follow rules... gradually the game teaches you more and more rules and also strips out the more abstract elements until on the last levels you are finally solving real equations. I loved it, it taught my kids algebra.... and it was just fun. Over the years I often thought that there should be a calculator for Algebra that works this way... something where you can drag terms around and cancel & distribute with gestures, but most importantly enter your own problems. It should also do more kinds of problems than DragonBox allowed. So I finally decided to build it. https://dicroce.github.io/wyrm/home.html Here's a video showing it: https://www.youtube.com/watch?v=_STbS4zvIlU . If you'd rather just play with it: there's a limited in-browser demo (real engine, a few example equations, no download) on the landing page — https://dicroce.github.io/wyrm/home.html . The app can be found on iOS ( https://ift.tt/3fsE14q ) and as of this week on Google Play ( https://ift.tt/CrHF9SJ... ). I also decided to open source the underlying math engine so others could build on it: https://ift.tt/FWYsVHC . My goal for the engine btw is to build it all the way up to Calculus. Monetization is deliberately boring: the engine is free (MIT), and the polished gesture app is $4.99 once. No subscriptions, ads, accounts, or analytics. I'd love feedback on the engine design — especially from anyone who's worked on CAS or proof-assistant-adjacent problems. And if you played DragonBox as a kid and wished it went further: this is for you! https://ift.tt/FWYsVHC July 9, 2026 at 04:46PM

Thursday, July 9, 2026

Show HN: EVconomics – EV vs. gas cost-of-ownership calculator with live prices https://ift.tt/Lqz0BQT

Show HN: EVconomics – EV vs. gas cost-of-ownership calculator with live prices https://ift.tt/JlsHDRS July 10, 2026 at 12:59AM

Show HN: Codex Explorer, a local session manager for Codex CLI https://ift.tt/0vw5at8

Show HN: Codex Explorer, a local session manager for Codex CLI https://ift.tt/cmThZfv July 9, 2026 at 11:53PM

Wednesday, July 8, 2026

Show HN: Hover over your UI element to get its exact location in code https://ift.tt/qdeLRXE

Show HN: Hover over your UI element to get its exact location in code https://loerei.github.io/HoverSource/ July 8, 2026 at 11:14PM

Tuesday, July 7, 2026

Show HN: Fork – Let users build features on top of existing applications https://ift.tt/8NMkxKH

Show HN: Fork – Let users build features on top of existing applications Our initial release is a Chrome extension that builds on top of Gmail and Google Calendar. We keep limited trace activity of coding sessions for 30 days to troubleshoot and improve our offering. No data (events, emails) from Google is ever logged or retained. 50 second demo: https://www.youtube.com/watch?v=JQ292bncO_c Chrome extension (free + no login): https://ift.tt/RkWM2bg... We have a lot to learn and build. Would love any and all feedback! Paul & Dalton https://withfork.co/ July 7, 2026 at 11:47PM

Monday, July 6, 2026

Show HN: Record, replay, and improve AI agents in production https://ift.tt/l8ROemw

Show HN: Record, replay, and improve AI agents in production At the AI Engineering World's Fair a big part of the conversation was to nail the self improvement loop. Our take on this is to record state of the agent execution with a durable runtime, then allow users to replay from state checkpoints and run 'what-if' experiments. It's OSS and free to use. Would love some feedback from the community. https://ift.tt/n8NReyQ July 6, 2026 at 10:56PM

Sunday, July 5, 2026

Show HN: Meon – declarative flat-parsing engine (SoA, no AST) https://ift.tt/V86TQmu

Show HN: Meon – declarative flat-parsing engine (SoA, no AST) https://ift.tt/crSiuR4 July 5, 2026 at 11:13PM

Show HN: Handoff – a verified context bridge between Claude Code sessions https://ift.tt/p8G7rL5

Show HN: Handoff – a verified context bridge between Claude Code sessions https://ift.tt/OQVD9SZ July 5, 2026 at 10:48PM

Saturday, July 4, 2026

Show HN: I built an encrypted BLE dongle for pasting stuff to air-gapped devices https://ift.tt/HmcRAta

Show HN: I built an encrypted BLE dongle for pasting stuff to air-gapped devices Definitely one of those "20 minute adventure gone wrong" projects where all I wanted initially was a quick wireless rubber ducky for bitlocker keys and the like and then I kept adding stuff like AES-256..... Currently working on adding WebAuthn/FIDO support because the hardware is already there and scope creep is a lifestyle at this point. Would love feedback, especially on the security side. Repo and PCB files are fully open source. https://ift.tt/D9ZmKfE July 5, 2026 at 02:43AM

Show HN: Waypoint.nvim – A Neovim plugin for bookmarking lines of code https://ift.tt/tMobXDm

Show HN: Waypoint.nvim – A Neovim plugin for bookmarking lines of code I made this plugin because I felt like existing bookmark plugins were lacking some important features, including: - The ability to reorder your bookmarks - The ability to delete and move your bookmarks in bulk - The ability to view lines of code around your bookmarks - Syntax highlighting in the preview window - Resilience to the content of files changing (e.g. checking out a git commit that changes the file contents won't delete your bookmarks) Let me know what you think! If you have any feedback, please create a github issue or email patricksharp.dev@gmail.com https://ift.tt/8Wf0lJb July 5, 2026 at 01:25AM

Show HN: Gemma 3 inference in pure C++ with Metal acceleration https://ift.tt/K9i75Xu

Show HN: Gemma 3 inference in pure C++ with Metal acceleration https://ift.tt/5Au0onh July 4, 2026 at 09:24PM

Friday, July 3, 2026

Show HN: Kontext – Move an AI chat's full context to another AI in one click https://ift.tt/3imV1Oo

Show HN: Kontext – Move an AI chat's full context to another AI in one click https://ift.tt/qYhlA6k July 4, 2026 at 12:57AM

Show HN: Auto-continue Claude Fable 5 the second your 5-hour limit lifts https://ift.tt/KD48kUn

Show HN: Auto-continue Claude Fable 5 the second your 5-hour limit lifts https://ift.tt/hPRlVyY July 4, 2026 at 01:05AM

Show HN: Dockside – I turned unused space around the macOS Dock into a workspace https://ift.tt/G2vBUgT

Show HN: Dockside – I turned unused space around the macOS Dock into a workspace https://ift.tt/cZkFBTm July 3, 2026 at 11:35PM

Thursday, July 2, 2026

Show HN: Bramble – Local-first password manager https://ift.tt/wc9oDMy

Show HN: Bramble – Local-first password manager I'm currently working on Bramble, an open source password manager with P2P cross-device sync. Initially I released the Chrome extension, but recently I also published the Android app and iOS is pending Apple's approval. Besides that, the latest version also includes passkey storage for all platforms! About Bramble: It aims to be as feature-rich as all popular and a replacement for cloud-based providers. I don't think we need to store our data in the cloud and be at the whims of companies raising their prices every year. There's always a breach and then we find out that some fields aren't encrypted, metadata is visible, and so on. I'm frustrated with this and the increasing lack of transparency during these breaches. The P2P sync in Bramble uses a Nostr relay (which can be self-hosted) to keep your devices in sync. The relay just introduces the devices to each other; the data then flows directly over WebRTC, so there's no vault server and no cloud copy of your passwords anywhere. What leaves your device is end-to-end encrypted and your devices authenticate each other directly, so a snooping or MITM relay gets practically nothing. Crypto is all done in Rust so I can control exactly how key material lives and dies in memory (secrets get zeroed out, no GB leaving copies lying around). In Chromium it's a wasm module, on mobile it's native builds bridged over via uniffi. Android app: I'm still deciding whether to publish the app on Play store or simply provide the signed APK which users can sideload. Reason for that is Google's plan to lock down Android and take away ownership from its users. Read more about it here: https://ift.tt/Lafs8hG The app uses no Play APIs whatsoever and runs perfectly on GrapheneOS, where I actually did all my testing. Questions, feedback, feature requests - all welcome! TL;DR: I dislike private-equity and venture funded companies messing with our security, so I created my own Password Manager which is local-first, free, open source and as transparent as it gets. https://ift.tt/r2BMuje July 3, 2026 at 12:59AM

Show HN: Piggy – lazy senior dev mode for AI agents (80–94% less code) https://ift.tt/oWPxrqj

Show HN: Piggy – lazy senior dev mode for AI agents (80–94% less code) https://ift.tt/ErvA7VX July 3, 2026 at 12:59AM

Show HN: A provider-agnostic agent loop built on ports and adapters https://ift.tt/CMUktW9

Show HN: A provider-agnostic agent loop built on ports and adapters I work on agent infra at Featherless. This is MIT and works with any OpenAI-compatible endpoint, not just ours. I kept rebuilding the same loop: call model, run tools, feed results back, stop. Every framework I tried either owned the UI, owned the control flow, or dragged a dependency tree. So I pulled the loop out and put every piece behind an interface: memory, model, tools, stop condition. The loop depends only on the interfaces. It never writes to a screen. It emits one typed event stream, so a trace is just data, and you render it however you want. The landing page scrubs one run and rebuilds a CLI, a DOM timeline, and raw JSONL from the same stream. One dependency (zod). Same build runs in Node, Bun, Deno, and a browser tab. Every seam is tested in isolation with deterministic doubles, no network. Why not the Vercel AI SDK, pi, or LangGraph: AI SDK owns more of the surface and has been awkward with self-hosted tool calling. pi is a great coding-agent toolkit but it's shaped around being a coding agent and ships a TUI. LangGraph is a heavier graph framework. This is the layer under all of those: the bare loop you'd build any of them on. Happy to be told where the seams are wrong. If anyone finds any problems let me know this field moves at break neck speed so let me know if I am missing anything. https://ift.tt/NZ2AnKY July 3, 2026 at 12:52AM

Show HN: Inkwell – An RSS reader for e-ink devices https://ift.tt/tRFqHD7

Show HN: Inkwell – An RSS reader for e-ink devices https://ift.tt/HfeBEDW July 2, 2026 at 09:08PM

Wednesday, July 1, 2026

Show HN: Searchable directory of 22k+ products from worker-owned co-ops https://ift.tt/Zrhi8dq

Show HN: Searchable directory of 22k+ products from worker-owned co-ops https://ift.tt/BENe05V July 2, 2026 at 02:17AM

Show HN: Z-Jail – A 130 KB Linux sandbox-C99 with 7 defense layers and zero deps https://ift.tt/4uUiQ9C

Show HN: Z-Jail – A 130 KB Linux sandbox-C99 with 7 defense layers and zero deps https://ift.tt/eqkvSYL July 2, 2026 at 12:48AM

Show HN: LIBR tracing with source ledger rows and byte-exact PDF verification https://ift.tt/kJsfE2b

Show HN: LIBR tracing with source ledger rows and byte-exact PDF verification https://ift.tt/q1DOQau July 1, 2026 at 11:25PM

Show HN: Live Claude Usage HUD for a $38 Thermalright Trofeo Vision LCD https://ift.tt/rzbQKpT

Show HN: Live Claude Usage HUD for a $38 Thermalright Trofeo Vision LCD https://ift.tt/o1Y5HcU August 16, 2026 at 03:12AM