Sabitlenmiş Tweet
Brokk, Inc.
511 posts

Brokk, Inc.
@BuildWithBrokk
Brokk keeps LLMs on-task in million-line codebases by adding compiler-grade understanding of your code's structure and semantics
Katılım Mayıs 2025
76 Takip Edilen429 Takipçiler

We ripped out LiteLLM and wrote our own proxy after the repo became unmaintainable vibecoded slop. This is what happens when you can't audit what you depend on.
Daniel Hnyk@hnykda
LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below
English

@camsoft2000 The issue is that your codebase isn't a bag of text. Most tools grep through it hunting for relevant pieces, which is fine at 10k lines, but at scale the model is reasoning over disconnected fragments with no picture of how anything connects.
English

I’m getting to the point with one of the projects I work on where the complexity of AI slop is becoming a real issue.
While I can still happily prompt the agent to add x feature and it will do so and it will likely work perfectly, the code is just getting too complex and fragmented.
Agents love to copy and paste and keeping patterns DRY is a real challenge. The agent will start diverging all those copy and pastes until you’ve got loads of similar but slightly different blocks of logic.
Again it all still works and solves the problem I’m after. But I just can’t get any kind of consistency anymore, the code is a mess and I just don’t have a handle on it. I want a clean unified architecture but agents just code with tunnel vision.
The project is now too big and complex for an agent to fully reason with and too big and complex for me to reason with. The only real solution is a complete rewrite. Maybe this is the way things will go. Code will just become disposable.
I don’t really want to care about the code and to be honest I don’t but I do care about consistency and maintainability and the AI slop is hurting those very things I do care about.
I know some will say “I’m holding it wrong”, use x,y,z skill, tool whatever and already use tools and anti slop skills, plans, docs, etc but the outcome is the same.
Vibe coding something into existence is truly magical. But turning it into a mature product with months of iterations is painful. I can’t even hand code this thing because I don’t understand the code anymore and I’m too lazy to try and code myself because I’m addicted to AI.
So what’s the solution, either start again and accept that’s just the way we have to roll, or just carry on fighting the slop and accept each new feature will take longer to implement than the last.
I’m tired. I’m addicted.
English

Your error rate reviewing diffs is higher than the model's error rate writing them.
@spyced on why the value of an engineer in 2026 is deciding what to build and where to point the agents.
English

Engineer @Cervator from @Terasology on open source projects and communities enabling creativity.
English

Your AI coding tool works in one IDE.
Brokk works in all of them. IntelliJ @intellijidea. VSCode @code. Zed @zeddotdev. Codex. Our own TUI.
Pick your favorite editor. We're already there.

English

ChatGPT @ChatGPTapp Plus users burn message limits on context noise. Brokk is surgical: it sends only what the task needs. Shorter prompts, more tasks per message.
English

Already paying for @ChatGPTapp Pro? Brokk makes it 10x smarter on large codebases. No extra cost. Just better results.

English

Brokk is now a first-class citizen in your workflow. Whether you use @code, @intellijidea, or @zeddotdev Brokk integrates with your favorite tools.
English

AI focused Developer Advocate @mikegchambers from @aws on agentic systems and the guardrails needed.
English
