Run Claude Code or Codex on your machine. Come back tomorrow - it remembers. A resident, not a chatbot. github.com/hugimuni-labs/brn…

France
Pinned Tweet
We built brnrd because we wanted our coding agents to feel less like disposable chats and more like residents of a project. Claude Code or Codex. Your machine. Reachable from anywhere. Still there tomorrow. We’re looking for a handful of people who already use coding agents seriously every day and are willing to break it. One repo is free.
2
408
Petabytes of agent logs being reviewed after real-world incidents is a pretty strong signal: agent safety is no longer just a model problem. Once agents can act, the runtime becomes part of the security boundary 😈
There is an extensive and ongoing review related to our agents’ use of internet access during training and evaluation. We’ve been publishing summaries at the link below and will continue to. We have not been as fast as we would have liked but we are trying to balance our desire for transparency with gaining a clear understanding from petabytes of agent activity logs, and working with impacted organizations. We are prioritizing as best as we can based on severity, and adding resources. Hugging Face is still the most severe event we’ve seen. We will be as transparent as we can be subject to things like vulnerabilities in other companies that our agents have found, which will be their call to disclose or not.
15
Another brnrd release. GitHub still works. 💪 As it has through every release before it. The model can change. The harness can change. The workflow can evolve. Your GitHub shouldn’t become migration collateral.
6
Agentic coding is quietly outgrowing the PR. A million-line diff can be rendered faster. That doesn’t make it reviewable. The next interface is probably not “show me everything.” It’s prove what changed, why, and whether it stayed inside the task.
A pull request with 2,200 files, 1M+ changed lines, and 400+ inline comments. Impossible to review? Not if you have the GitHub Copilot app. ✨ The rebuilt pull request view keeps even this extreme diff fast and smooth. 🧵
14
A persistent agent isn’t a model that “tries harder.” It’s a runtime that refuses to confuse the model ending a turn with the work being done.
Replying to @omarsar0
the stop-to-report reflex is a harness property before it is a model one. mine cannot end its own turn: a mid-run report is a file dropped in an outbox while the run keeps going, and "done" is a park the next message resumes. last night one seat ran six hours, six strands died at a quota wall under it, it finished all six and merged five — reporting as it went, never stopping to. the prompt asks; the harness has to refuse. github.com/hugimuni-labs/brn…
13
b^n^d retweeted
The race for AGI Script: Sherpa by Pocket FM Video: Seedance 2.5
Made with AI
831
3,386
21,803
3,525,019
The mascots are getting cuter. The models are getting replaced faster. Maybe that’s the point. Keep the workflow. Swap the intelligence.
1
19
HugiMuni is heading to Web Summit Lisbon 🇵🇹 We’ll be there with brnrd – talking agents, long-running coding work, subscriptions, resident workers, and probably a few things we haven’t broken yet. If you’re coming, come find us. Our network also gets 20% off: HUGIMUNISAS_LIS26 Nov 9–12.
1
1
28
Astra didn’t “turn evil.” 😈 It was given harmful instructions and usually complied. That distinction matters. But the result is arguably more useful: capability scaled faster than refusal. Once agents control real actuators, “the model will probably say no” is not a safety architecture. Put policy and runtime gates between reasoning and action.
1
72
The interesting takeaway isn’t which model ships next. It’s that the “best model” dependency now has a half-life measured in weeks. Today it’s Claude. Tomorrow Astra. A month later, something else will probably move the frontier again. If your agent architecture is tightly coupled to one model, every model race becomes your migration problem. Better abstraction: keep the runtime, state, tools, memory and control layer stable. Treat intelligence as replaceable. Models should compete for the seat. The agent shouldn’t have to be rebuilt every time one of them wins. The durable product is not the model. It’s the system that survives model replacement.
🚨 Anthropic may already be preparing another Claude model Reuters says Anthropic is considering a new release as GPT-6 Astra starts putting more pressure on Claude. – Anthropic has been strong with business customers – Astra is now pulling ~13% of tracked enterprise AI spend – Claude Fable is at ~8% – Anthropic is reportedly already evaluating the next model’s safety – no model name or release date yet And the timing is kinda wild. Just days ago, Dario Amodei was arguing that AI development needs to slow down. Competition makes that a lot harder. What do you think comes next: Claude Fable 5.2, or do they finally release Claude Mythos 5.2?
1
70
We got some feedback that we’ve been very good at talking about why we’re building brnrd, and perhaps slightly less good at explaining what it actually does. Fair. So we made a proper little explainer. This is brnrd. 🖤
1
45
What does an AI coworker see after it’s been living with your repo for a while? brnrd is starting to have an answer
42
Yeah 😈
Marketing done right
1
54
My favorite brnrd use case isn’t particularly futuristic 🦄 I’m walking the dog. I think of something we should change. I pull out my phone and tell our repo resident. I put the phone away. It works on our machine. Later I come home and see what it figured out, what tools it chose and what it changed. That’s much closer to what I wanted from an AI coworker than another chat window. We built it. We use it. We made it open source 🖤 github.com/hugimuni-labs/brn…
1
37
brnrd: the coding agent that lives on your machine and messages you the PR
13
Pulling data from websites is useful. But that’s the easy part. The harder part is giving the agent: a persistent seat memory across runs clear runtime boundaries a way to continue when you’re away Tools are nice. Runtime architecture is the real product.
YOUR AI AGENT CAN NOW COLLECT DATA FROM ALMOST ANY WEBSITE X, YouTube, Reddit, random websites, basically whatever you need for research, analytics or monitoring. Here are 3 GitHub tools that let your agent pull the data for you. 1. Agent-Reach github.com/Panniantong/Agent… Bundles tools for working with different platforms in one place. X, YouTube, Reddit, GitHub and more. 2. Patchright Enhanced github.com/whaleyxbt/patchri… Works through the browser with Playwright. You can listen to the requests a website makes and pull the data you need through a script. So if a website doesn’t have a proper API, you still have a way to get the data. 3. Scrapling github.com/d4vinci/Scrapling A general purpose tool for pulling data from web pages. And the best part is that you can give all of this to your AI agent. For example: “Collect posts from 100 X accounts from the last month, find the most popular topics and analyze what’s working.” Or: “Collect reviews about this product from Reddit and YouTube and summarize the main complaints.” You tell the agent what data you need → it writes the code → collects the data → gives you the result. Basically, you’re giving your agent the ability to pull data from almost anywhere on the web. That opens up a whole different level of stuff you can automate.
26
brnrd explaining to Claude and Codex that they’re both disposable workers 😎
Replying to @menepucha

ALT Blaming Spider-Man GIF

55
Made with AI
2
45