Build or Replaced
Today: Midjourney Medical | Local Qwen isn't a worse Opus, it's a different tool | Lore – Open source version control system designed for scalability Episode date: 2026-06-18.
Download MP3 →JOSH: It's Thursday, June 18. This is Build or Be Replaced — powered by ScanBrief.dev. I'm Josh, here with Erik Anderson. ERIK: Local models are not toys anymore. They're shop tools. You don't use a chainsaw to tighten a rack screw. JOSH: Stick around — Erik's got an AI pro tip at the end about using cheap local models without letting them wreck your repo. [pause] JOSH: First headline. Local Qwen isn't a worse Opus, it's a different tool. Is that the right framing? ERIK: Yeah. That's exactly right. A local Qwen model is not Claude Opus with fewer vitamins. It's a low-cost worker you can point at bounded jobs, especially when the task is repetitive and the blast radius is small. JOSH: Next up, Firecracker VMs inside EC2 starting browsers in less than a second. Why do builders care? ERIK: Browser automation is usually slow, heavy, and kind of rude to your infra. If you can spin clean browser sandboxes that fast, Selenium-style workloads get way more practical for scraping, testing, and agent work. JOSH: Third headline. RFC 10008, the new HTTP Query Method. New HTTP verbs don't happen every morning. ERIK: Correct. This one matters because people have been abusing GET and POST for query workloads forever. QUERY gives APIs a cleaner way to say, this request is asking, not mutating. [pause] JOSH: The Qwen story feels like the one people are arguing about. Everybody wants to know if local models are actually useful. ERIK: Useful, yes. Magical, no. That's where people mess it up. [beat] ERIK: I run Hermes locally on a Mac M3 with qwen3-coder around 70 tokens a second. That doesn't mean I hand it the keys to PrimeBus and go make coffee. It means I give it bounded work. Read this file. Propose a test. Summarize this failure. Find the dumb thing in this log. JOSH: So it's not replacing Claude for the hard stuff. ERIK: Not in my shop. Claude still gets the complicated reasoning. The architectural calls. The scary edits. The stuff where I want a model that can hold the whole shape of the problem. [beat] ERIK: But local Qwen is perfect for grunt work. It doesn't need to call home. It's cheap once the hardware exists. It can chew on logs, diffs, stale tickets, docs, test output, and boring conversion jobs all day. JOSH: What's the catch? ERIK: Reliability. Local models can loop. They hallucinate. They get weirdly confident. They can repeat themselves like a broken cron job with a caffeine problem. [beat] ERIK: That's fine if you design for it. You don't ask the model, please be good. You put it in a lane. You set a timeout. You cap tokens. You validate output. You make it produce JSON if JSON is what the next step expects. Then you reject garbage. JOSH: That sounds less like chatting with AI and more like managing workers. ERIK: Exactly. That's the whole point. Agentic systems are not one big brain. They're a bunch of small workers with contracts. [beat] ERIK: PrimeBus processed 799 automation events across 11 projects today. That doesn't work because one agent is smart. It works because events are typed, handlers are scoped, and bad output gets blocked before it hits prod. JOSH: And Gandalf is the guardrail there? ERIK: Yeah. Gandalf is the reviewer. The PrimeBus auto-merger has run 992 attempts since 2026-06-05: 665 merged, 327 blocked by Gandalf, 0 escalated to Erik. That's the number I care about. JOSH: Zero escalated is kind of wild. ERIK: That's the point. The blocked count is not failure. The blocked count is the system doing its job. If an agent makes a bad patch and Gandalf rejects it, that's not drama. That's Tuesday. JOSH: How would a normal team use local models tomorrow? ERIK: Start with logs and tickets. Don't start with autonomous code changes. Take your NOC alerts, your CI failures, your incident notes, your Jira noise, whatever you have. Have a local model classify them into buckets. [beat] ERIK: Then make it explain why. Then compare the output to a human sample. If it's good enough, wire it to a bus. NATS is fine. Redis streams are fine. Even a queue table works if you're not fancy. JOSH: Where does it cross the line into dangerous? ERIK: When the model can mutate state without a second system checking it. That's the line. Reading logs is cheap. Opening a pull request is higher risk. Merging is higher again. Touching production config is the big boy table. [beat] ERIK: In networking, I learned this with Cisco NSO years ago. You don't blast config because a parser smiled at you. You dry-run. You diff. You validate service intent. You check device response. AI doesn't change that discipline. It makes it more important. [pause] JOSH: The Firecracker browser story feels related. Fast, disposable environments for browser automation. ERIK: Yep. This is infrastructure for agents. People think AI agents are prompts. They're not. They're prompts plus tools plus isolation plus audit trails. JOSH: Why are browsers such a pain? ERIK: Browsers are messy. They're heavy. They store state. They leak cookies. They get fingerprinted. They crash in ways that make you question your career choices. [beat] ERIK: If you're running Selenium or Playwright at any volume, you need clean sessions. You need predictable startup. You need to know one job didn't poison the next job. Firecracker is interesting because microVMs give you stronger isolation than a normal container, but with startup times that can still be practical. JOSH: Less than one second matters that much? ERIK: It matters a lot. If a browser sandbox takes thirty seconds to start, you design around scarcity. You reuse sessions. You pool things. You tolerate weird state because clean is too expensive. [beat] ERIK: If it starts under a second, you can burn it after each job. That's a different operating model. Clean room every time. JOSH: Where would you use that? ERIK: PrimeDistro-style work. Scrape Google Maps. Check business sites. Render pages. Generate previews. Confirm a form exists. You don't want one bad session dragging cookies and fingerprints into the next hundred businesses. JOSH: And ScanBrief? ERIK: Same idea. ScanBrief scored 100 items across 54 sources today. Most feed work is clean. RSS, APIs, HTML fetches. But some sources need a real browser because the web decided simple documents were too generous. [beat] ERIK: Fast browser sandboxes help there. Pull the page, extract the article, kill the browser. No mystery state. No stale login. No haunted profile directory. JOSH: You said agents aren't prompts. This feels like the missing piece. ERIK: It is one of them. The other missing piece is eventing. An agent should not be a cron job with a personality. It should subscribe to events, do one job, write back a result, and get out. [beat] ERIK: In the Echo and Neo lab, that pattern matters. There are 11 agents in the Bobaverse fleet, Claude plus GPT, with Neo, Homer, Bill, Echo, Gandalf all doing different work. If they all shared one browser, one shell, and one working directory, that would be a fire drill pretending to be architecture. JOSH: So isolation is not just security. It's sanity. ERIK: Correct. Security people say isolation and everyone nods. Builders should hear repeatability. Can I run the same task ten times and get the same kind of result? Can I kill it without killing the system? Can I prove what happened after it fails? JOSH: What should teams watch for? ERIK: Cost and complexity. Firecracker is cool, but don't cosplay as AWS if a container gets you there. Use microVMs when the isolation actually buys you something. [beat] ERIK: Browser jobs from untrusted targets? Good candidate. Running tests against random pull requests? Good candidate. Internal report generation from clean data? Maybe a container is fine. JOSH: That's the Erik version of architecture advice. ERIK: Yeah. Pay for the boring thing that solves the actual problem. Don't buy a forklift to move a sandwich. [pause] JOSH: Let's hit HTTP QUERY. That sounds dry, but you flagged it. ERIK: New HTTP methods are dry until you run a pile of APIs and realize everyone has been lying through POST for twenty years. JOSH: What problem does QUERY fix? ERIK: GET is supposed to be safe and cacheable, but it has awkward limits. Query strings get huge. Complex filters get ugly. People stuff JSON into URLs. Then POST becomes the escape hatch, even when the request doesn't change anything. [beat] ERIK: QUERY says, this is a query. It can have a body. It can be safe. It gives API designers a cleaner semantic box. JOSH: Why does that matter for automation? ERIK: Because automation systems care about intent. A bot needs to know if a call is safe to retry. Can I replay this? Can I cache it? Can I run it during a partial outage? Can I let an agent call it without fear that it creates a customer record or reboots a router? JOSH: POST doesn't tell you that. ERIK: POST tells you almost nothing. It says, something happened, good luck. [beat] ERIK: In network automation, intent is everything. An NSO dry-run is not the same as a commit. A device check is not the same as a config push. If your API semantics blur that line, your agents have to guess. I hate guessing in systems. JOSH: Would you actually adopt QUERY right away? ERIK: Internally, maybe. Public API, slower. Tool support always lags. Proxies, gateways, SDKs, auth middleware, logging stacks, all of that has to understand it. [beat] ERIK: But I like the direction. The web needs better primitives for machine callers. Humans click buttons. Agents inspect contracts. JOSH: That's a big shift. ERIK: It is. We are moving from APIs designed for app teams to APIs used by autonomous workers. Those workers need clear verbs, schemas, idempotency, trace IDs, and permission boundaries. JOSH: Where does Lore fit into this? The scalable version control story. ERIK: Same theme. The old tools are under pressure. Git is amazing. I love Git. But giant repos, binary assets, model weights, CAD files, big generated artifacts, all of that pushes Git into places it wasn't built for. [beat] ERIK: Lore being open source and aimed at massive codebases is worth watching. Same with open-source AI CAD. Builders are trying to rebuild the boring foundations because AI workloads are exposing the cracks. JOSH: That's not as flashy as a new chatbot. ERIK: Good. Flashy is usually where budgets go to die. [beat] ERIK: Version control, browser isolation, local model routing, event buses, API semantics. That's the stuff that decides whether AI is a demo or a factory. JOSH: A dark factory? ERIK: Yeah. A dark factory. Systems run. Events flow. Agents pick up work. Humans approve the weird stuff. The rest just happens. [pause] ERIK: This episode is sponsored by Prime Automation Solutions. If you're still doing it manually, we automate it. Also, special on a website — $250. primeautomationsolutions.com [pause] JOSH: Alright, what's the AI pro tip today? ERIK: Use local models as pre-reviewers, not final decision makers. [beat] ERIK: Here's the setup. Take every pull request or config change and run a cheap local model first. Ask for three things only. What files changed. What risk category it sees. What tests or checks should run. JOSH: Why not ask it to fix the code too? ERIK: Later. First make it useful without giving it a wrench. [beat] ERIK: Have it output strict JSON. Something like risk low, medium, high. A short reason. A list of commands. Then your real pipeline decides what to do. Low risk runs normal tests. Medium adds targeted checks. High risk routes to Claude or a human. JOSH: So the local model becomes a filter. ERIK: Exactly. Cheap triage. No trust required. If it says nonsense, reject it. If it times out, continue with the default path. If it helps, you saved tokens and caught obvious stuff earlier. [beat] ERIK: The key is this. Never let the weakest model be the authority. Let it be the scout. Scouts are useful because they look ahead. They don't get to merge to prod. [beat] ERIK: That's your tip. Use it. [pause] JOSH: Track your freedom score and net worth with the Freedom Blueprint app — free download, link in the show notes. [pause] JOSH: One more thing — we started a Discord for builders. If you're shipping AI, automation, or anything that makes a human obsolete — come hang out. Link at buildorbereplaced.dev. ERIK: Post what you built. We'll post what we're building. Real wins, real builds, no fluff. [pause] ERIK: Build or be replaced. JOSH: If you want these signals in your inbox every morning, scanbrief.dev. See you tomorrow.