I built basically this on top of my telegram setup last year. The thing that killed it was group chats, per-message LLM calls on a busy group eat your api budget alive, so I ended up putting a tiny local model in front as a first pass.
Such a rage bait title, but sure I'll take the bait.
It is easy to phrase anything as slaves. Are refrigerators and microwave ovens our slaves? But if you push the tech fare enough.. there is a boundary where we do cross the slave threshold.
The problem is that LLMs do not have a conceptual grounding in actual time. They estimate based on statistical correlation found in their training data which is filled with standard corporate project management timelines legacy codebases and waterfall estimates.
Good one. One thing that's becoming clear is that agent security is less about jail break prompts and more about permission boundries, hidden context flow and un intended tol behavior.
From the usage patterns I've seen for 90% of the use cases it seems to be fine, the one exception being Browser based use cases which chugs memory and so needs a beefier machine.
It's the damn chromium instances that chugs memory like an Irish man chugs beer. I experimented launching containers with it and quickly realized the tiny shared infra hosts are not a good fit. We're launching a higher prized plan that has more memory for such things.
Great point, we de-duplicate the search results by Repository Id. that largely filters out content from the same person , and note that search prioritizes github stars, so low quality one's get pushed to the bottom
Thank you!
We have limits around usage. Also as a startup we have a lot of Gemini credits from Google, so that helps in offering it. Not to mention the gemini 3 flash that it's running on is dirt cheap.
Regarding low quality skills, our search only surfaces top starrted and forked skills, so that largely addresses that. Kinda like google page ranking. You'll see that whatever you search for, you tend to only get high quality skills first.
We do back up data, although it's manual. The docker instance home directory and homebrew are backed up in a separate partition. So it survices restarts and container updates.
We only allow ttyd not ssh, so users only have access to their individual containers and isolated from the host. But inside the container they can do whatever they'd want.
There are also caps on CPUs and resource and PID limits so as to avoid noisy neighbor situations