Dear God, please don’t. FF does not want your AI slop bug reports. You people are ruining open source.
Especially from a 7b model
Pretty sure if you have to ask how to do it, you’re not qualified to do it.
This is the definition of a zero effort post.
You don’t want to put forth the effort to bug hunt, you want an AI agent to bug hunt for you. You don’t want to learn to even setup the agent, you want other people to explain step by step how to do that for you.
I’m assuming you aren’t even going to review before it submits. Honestly though, how would you review it given you don’t know anything about the topic its submitting on.
LMAO
Did you forget the body text? Or is this some bug? Looks like a question here, and like an AI fabricated tutorial in the original version of this cross-post.
This makes me genuinely curious, who thought that would be a good idea?
It feels like a lot of “contribution” to open source suddenly is fueled by AI hype. Is it a LinkedIn/TikTok “trick” that is being amplified that somehow one will get a very well paid job at a BigTech company if they somehow have a lot of contributions on popular projects?
Where does that this trend actually come from?
Did anybody doing so ever bother checking contribution guidelines to see which tasks should actually be prioritized and if so with which tools?
This seems like a recurring pattern so it’s not a random idea someone had.
run a local LLM like Claude!
Look inside
“Run ollama”
Ollama will almost always be slower than running vllm or llama.cpp, nobody should be suggesting it for anything agentic. On most consumer hardware, the availability of llama.cpp’s --cpu-moe flag alone is absurdly good and worth the effort to familiarize yourself with llamacpp instead of ollama.
I have used Ollama so far and it’s indeed quite slow, can you recommend a good guide for setting up llama.cpp (on linux). I have Ollama running in a docker container with openwebui, that kind of setup would be ideal.
I just run the
llama-swapdocker container with a config file mounted, set to listen for config changes so I don’t have to restart it to add new models. I don’t have a guide besides the README for llama-swap.
–cpu-moe
AI Acknowledgement
The joke is worth the slop, imo. “Cpu Moe”. 😂 Find me an anime drawing of a CPU (especially an iconic one) and I’ll use that instead.
In your defense, I’ve thought the same joke every time I’ve seen it lol
Props for putting something together and not burying it in a 20 minute YouTube video.
My mind initially went to OpenCode - I’m not familiarity lite-cc - any reason you opted for that? Is it just kinder on smaller local models?
I ended up using OpenCode, very useful thanks!
Judging by the github repo, it’s the very basic cousin, written (vibe-coded) in Python. It doesn’t do planning or anything, just preface your command with a system prompt telling your model it’s a coding assistant. And gives it tool access to read and write files. And execute commands.
And seems no human uses it, there’s no interactions like bug reports, PRs or people who star and like the repo.
