Post #2365611
2026-02-23 06:14 UTC
@florenciocano@infosec.exchange I suspect it’s not designed with much resilience or user feedback for use cases where lesser models than the ones typically used from Anthropic / OpenAI are configured.
When I tried Azure Foundry hosted OpenAI models it was better
Instead of digging in to why the local models didn’t work (the channel / web chat didn’t help and there was no relevant info in logs) I decided instead to build my own agent.
The idea is to build it with more “robustness” including typescript class inheritance for key components like models, channels, skills, and agents. Also build in a containerisation layer so skills can be off loaded and isolated “properly”. Plus use different model configs for different discrete agent tasks eg. select your ideal model for a) planning b) skills parameter selection c) assessment of task completion and d) response to user.
The theory with multiple model config is you could use a lightweight instruct model to work out which skills are relevant to a task, similarly for assessment, etc. models could also be fine tuned for the skills related tasks…
Replies (1)
-
@rayk@techhub.social 2026-02-23 06:39
@mpowney@mastodon.au @florenciocano@infosec.exchange Wait, you think there was design involved? :) Seriously though, I was only willing to run it against an LLM on my own network, so I tried qwen-3-coder and glm-4.7-flash. Both made the assistant really hard to work with, as it would forget things, get stuck on little details from the SOUL.md file, and so on. I’m sure it was never tested with smaller models, but I wouldn’t call that a real design decision.