Show HN: GAI – A Go runtime for typed, tool-using LLM agents https://ift.tt/ENyfhQj

Show HN: GAI – A Go runtime for typed, tool-using LLM agents https://ift.tt/dyWb4Gx August 1, 2026 at 02:53AM

Show HN: Offline Flock Navigation https://ift.tt/iAke3Tr

Show HN: Offline Flock Navigation Hello HN! A little side project I have been working on a fork of OsmAnd with offline ALPR/Flock camera avoidance routing. Also, took the time to at least create a paper on the project as well. https://ift.tt/eRPNa57... And yes, I did use AI to help me with this. All of it open sourced and available for use. Though I don't intend to build Apple version of this, or submit it to the play store. I am looking for feedback! Thank you all and have great weekend. :) https://ift.tt/xJ3mBn0 August 1, 2026 at 12:10AM

Show HN: How to build and self-host a code review agent https://ift.tt/MShdcFg

Show HN: How to build and self-host a code review agent Hey HN, I've had a side-project that I've slowly ticked away at over the last year called Tilde. Tilde is a harness SDK platform - I've tried to take the best things of OpenClaw, Hermes & other harnesses and decompose them and make them available as cloud API building blocks. You can use Tilde to create AI agents for your use case, fast and self-host the agent's yourself. The documentation (and attached blog post) leave a lot to be desired in terms of technical documentation but hopefully the attached git repo does a good job of showcasing the API. https://ift.tt/lzL8JEH https://ift.tt/iaZhJmN August 1, 2026 at 12:27AM

Show HN: Local text, image, video, music and 3D from one CLI, no Python https://ift.tt/4Kw3ag6

Show HN: Local text, image, video, music and 3D from one CLI, no Python Hi HN! I'm the author of mere.run a local first inference runtime built around an installable CLI. I believe that whenever possible we should use the stuff we already own (like our Mac laptops, decent machines gathering dust, our gaming PC) and the limited electrical power we have easy access to, like the socket in the wall next to most of us. We shouldn't have to send our data to the cloud hoping some T&C will prevent it from being used in a way that we'd regret. Most of the local AI solutions are technical, involved, and land a curious body in some package hell. People are optimizing for one system and not another, the fun stuff is on PC if you own a Mac, and on Mac if you own a PC. So mere.run was my choice to begin to patch many of those things that I saw as problematic. Text, chat, code, image gen, speech tts+asr, vision (caption/ground/segment/track/pose/depth/face/OCR/etc), music, sfx, video, 2d->3d, persistent worlds, lora training plus a few more things I am probably forgetting all in one place to work the way you work, with a scriptable CLI, an openAI compatible serve, and optionally a native app on Mac. It's native swift on MLX, no python, PyTorch, diffusers for inference. For text lanes with GGUF it uses llama.cpp and for a/v muxing its FFmpeg. Most upstream releases that don't have an MLX variant are converted offline and hosted on huggingface. All release packages are built for arm64 (Mac & Cuda) plus x86. They're signed and ship SHA256SUMS. No windows at the moment. > mere.run model capabilities --recommended # That inspects your machine before recommending to prevent pulling models that don't fit your spec There's a workflow layer with typed, validated graphs so you can create immutable job bundles and run them locally, over an ssh executor or using a fleet of machines and the relay service. (It's hosted at relay.mere.run and is currently invite only while I test, but its also totally open MIT so you can set it up yourself) The whole runtime is MIT along with the companion packages, models carry their own licenses and the CLI makes it clear when something has specific terms. Once you've pulled the models, everything works fully offline. I've been working on a (hopefully) comprehensive docs -> https://docs.mere.run No account, no API key, no analytics or phone home. Any network calls in the source are all at your request only like huggingface.co (models), GitHub.com (Pi install). I'm just getting started, but it's finally at the point I'd love feedback, contributions, and just folks to generally find it useful. I hope it helps you make things and explore what's possible with the stuff you've already got in your home. Would love any thoughts, questions, ideas and maybe a star if you do that kinda thing. -Kyle https://ift.tt/Pg90sjX July 30, 2026 at 05:25PM

Show HN: Collie – a local AI harness that runs the browser, desktop and code https://ift.tt/SNHk4wZ

Show HN: Collie – a local AI harness that runs the browser, desktop and code https://ift.tt/D7cvI8T July 31, 2026 at 12:24AM

Show HN: Supapool – a Supabase per coding agent in ~400 ms https://ift.tt/oydFhYL

Show HN: Supapool – a Supabase per coding agent in ~400 ms hi HN, I built supapool.io, an ephemeral full copy of supabase's services that you can spin up in ~400 ms (Auth, postgres, storage, realtime). so if you run multiple coding agents in parallel in different worktrees, they can now have their own copy of supabase without making changes that conflict with eachother. > why not use supabase docker locally? when I run 3-4 instances locally, my macbook gets hot and sometimes freezes. > why not use supabase branches? branches take minutes to setup, and are designed for persistence. this is expensive, and for a dev environment, it is too slow. > why not use mocks? mocks are bad for agents. i expect agents to test their migrations, SQL against real prod service behavior. agents hallucinate working mocks often. However, upside of mocks is that its faster and runs locally, but with supapool, the upside is less convincing. > how does it work/how is this economically viable? starting supabase in 400ms requires a few things: 1. a pool of ready supabase instances running warm, and colocated with region failover (us-east, us-west, europe-west, asia-southeast) 2. fast autoscaling when pool starts to shrink with microVM/firecracker 3. gutting strong persistence guarantees. dev agents don't need WAL, fsync, PITR, replication. anything for HA on a ephemeral supabase instance is bloat its in beta right now, and i'm using our gcp credits to bankroll this, so its free. the eventual pricing will be something like $/instance second and more cost effective than branching or self hosting/maintaining a supabase cluster. would love to get your feedback if you use supabase, and if you think there's something better that would fit your local coding agent setup. Thanks! https://supapool.io/ July 29, 2026 at 09:34PM

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

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/GMvUWqz July 29, 2026 at 10:52PM