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

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/ceUJnx7 , 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

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

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

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

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/jm8Sslt July 29, 2026 at 11:45PM

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

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

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

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

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

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/J1mfNT0

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/nqlMHF1 July 28, 2026 at 09:48PM

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

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

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

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/nzhEkOJ 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/lSJ3LXt Site: letsseal.org Thx https://ift.tt/lSJ3LXt July 27, 2026 at 09:22PM

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

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

Show HN: Proxmox -> Share your host's Bluetooth with a VM over the network https://ift.tt/VzYcgNy

Show HN: Proxmox -> Share your host's Bluetooth with a VM over the network https://ift.tt/X9NyAZh July 26, 2026 at 01:11AM

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

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/yfvs2qm https://ift.tt/P1XqiGN July 25, 2026 at 12:07AM

Show HN: PBasic is a modern BASIC interpreter with a retro vibe https://ift.tt/v3MWXZ2

Show HN: PBasic is a modern BASIC interpreter with a retro vibe pBasic is a modern BASIC interpreter with a retro vibe. It allows you to easily find your way into computer programming and form a connection with the code. You will learn about Games programming, how to animate Sprites, and compose your own Functions. pBasic gives you a blank canvas in which you can realize your own creations. https://ift.tt/jCmblE0 July 24, 2026 at 10:30PM

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

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

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

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

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

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

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

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

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

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

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

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/krQSpGa July 21, 2026 at 11:39PM

Show HN: Neuron. Turn a SQL query history into a semantic layer https://ift.tt/EJ6KqhW

Show HN: Neuron. Turn a SQL query history into a semantic layer My cofounder and I previously ran analytics groups in life sciences. That means we led teams of analysts who typed SQL all day long and we ran into common issues of consistency, correctness, and knowledge transfer. We were always one resignation away from losing all of the history on a project or a client. When we left that world we thought we could solve the problem with auto-documentation. Cut to now and we've landed on the modern version of that solution, which is to turn previously executed queries into context for AI. The intuition is roughly this: a smart analyst can read SQL and have a pretty good idea of what's going on, and in fact can infer a lot of institutional knowledge about the domain and how to analyze particular data. LLMs are not great at this (Anthropic and Snowflake have written as much). So we act as the "smart analyst" to pull out institutional knowledge and practices (in the form of SQL) that you can give to an LLM so that it can code like a competent analyst on your team. Right now we're deploying it as a semantic layer population tool. You want to fill up a Genie or Cortex semantic layer? Run our code on your query history, prune it with your experts (delete this, rename that, etc.), and get moving. That can take hours/days instead of weeks. Plus, everything we export is portable to whatever system you choose. FYI we ask for emails on the free trial download so we can monitor our traction and build our network but you don't need to include it if you don't want to. We're hungry for feedback from people who work in the field and are facing these challenges. Major, major thanks in advance for your time. https://ift.tt/tC76ZEl July 20, 2026 at 11:41PM