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

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/VGq4Aw0 July 2, 2026 at 11:22PM

Show HN: PurRDF-High performance, cross platform RDF1.2 https://ift.tt/bkufVNF

Show HN: PurRDF-High performance, cross platform RDF1.2 https://ift.tt/btAgfO3 July 2, 2026 at 11:15PM

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

Show HN: Inkwell – An RSS reader for e-ink devices https://ift.tt/7iLam5s July 2, 2026 at 07:38PM

Show HN: Salt – a systems language with Z3 theorem proving in the compiler https://ift.tt/xPTKle1

Show HN: Salt – a systems language with Z3 theorem proving in the compiler https://salt-lang.dev July 1, 2026 at 09:05PM

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

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

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

Show HN: Z-Jail – A 130 KB Linux sandbox-C99 with 7 defense layers and zero deps https://ift.tt/WhyG0Np July 1, 2026 at 11:18PM

Show HN: Kage, verification and freshness for Google's OKF agent memory https://ift.tt/YZ1MHIT

Show HN: Kage, verification and freshness for Google's OKF agent memory Kage was always a document format memory with it's own memory standards... and was betting on file based memory + git native. It's good to see that Google also thinks the same and released OKF(Open Knowledge Format) and Kage has adopted OKF with open arms. Though Google has released the Memory standard and how to structure the memory, it doesn't do verification, when and how memories are created. That's where Kage comes in, Kage as a framework works with your agent, understand what to save, when to save, how to save, it also help the agent to recall relevant memory/maintain it's freshness. Kage is focused on maintaining your repo's memory for you and give you best experience when coordinating and working with teammates on the same repo. Just install Kage and let you agents do the memory maintenance job itself using Kage. Best support with Claude Code(Hook), also available and works with all the over coding agents. https://kage-core.com/ July 1, 2026 at 12:29AM