// ITS FOSS — LINUX & OPEN SOURCE
Local AI Weekly #2: Agents Everywhere
Welcome back to Local AI Weekly. I promised a weekly, and then took a month to send the second one. So let's call the first one the pilot episode. From here, the show will run weekly 🤘
This issue leans heavily toward agents, because that's where most of the interesting local AI tooling is landing right now.
Before we see all that, let me thank Atomic Chat, who is supporting this edition of Local AI Weekly.
Atomic Chat lets you run open-source LLMs privately on your own device, fully offline. It has Turboquant built-in providing faster local inference with longer context windows. Which means you can run bigger models smoothly, right on your device.
I downloaded Unsloth this week. It's an open source framework for fine-tuning and running open models faster and on far less VRAM than the usual setup. It's probably best known for its Dynamic GGUF quants, the ones that let people run 27B-class models in around 17GB of RAM, with 1-bit builds that squeeze onto 8GB.
Yeah...that's the kind of claim I don't want to repeat until I've tested it myself. So consider this a heads-up, not a review or recommendation. I'll try it on my ZimaCube (with Nvidia RTX Ada 2000) and give you the full verdict in a coming issue.
Three of this week's finds are about making your local agents "behave". tehy are smart, but they have to be accountable, too. All of these tools are open source.
The first is agent-inspect, a local-first debugger for TypeScript AI agents. It turns an agent run into a readable execution tree, so you can see every tool call, model call, and the exact point where things went wrong. It can also fail a CI check when the agent takes the wrong path, and bundle up a redacted trace to share with someone else.
Next is AutoMem, a persistent memory layer that plugs into agents over MCP. Most agents start every session from zero. AutoMem stores what matters in a graph for relationships and a vector index for meaning, so recall gives you the answer and the thread it belongs to. You can run the whole thing locally in Docker, offline, with your data staying on your machine.
The third is BrowserSkill from Tencent. It lets an AI agent use your real, already logged-in broswer instead of a fresh sandbox with throwaway accounts. The interesting part is that it runs tasks in a separate, visible Agent Window and only borrows a tab you have open when it explicitly asks, so you can keep working while it does. When it hits a captcha or a login, it hands control back to you and picks up after. Agents can still not tick all the traffic lights, it seems 😉