@thsottiaux Hello @thsottiaux there is an issue with codex where if i close the terminal inside codex on Windoes, instead of just going back to the original tab, it trys to open up a new chat. Just wanted to share, cheers.
Building RouterCore for the AMD Developer Hackathon.
It’s a safe routing layer for AI agents: before a DevOps agent executes, RouterCore decides whether a request should be routed, clarified, confirmed, rejected, or escalated.
Current MVP: FakeRouter baseline, schema validation, policy engine, clarification loop, Gradio demo, synthetic train/eval data, eval comparison tools, optional HF model + LoRA path for AMD ROCm
Baseline:
JSON validity 100%
workflow accuracy 97.01%
unsafe rejection 100%
false route rate 0%
Next: fine-tune a compact model on AMD GPUs with ROCm.
Repo: https://t.co/ZxGZVRhr0g
@lablab_ai@AIatAMD
#BuildInPublic #AIAgents #ROCm #FineTuning #HuggingFace
Stronger AI systems may not come from one model knowing everything.
They may come from smaller domain-specific environments: constrained workflows, clear rules, known data, validation layers, and human judgment where it matters.
That is probably the foundation for more reliable enterprise AI.
@piyorinko25 Exactly. Also, for what it’s worth, it did not auto-translate on my side. I had to tap translate, but once I did, it came through clearly in English. Appreciate the thoughtful reply.
Quick question:
What is the most annoying workflow problem you are dealing with right now?
AI, engineering, infra, product, dashboards, ops, research, anything.
Trying to understand what people actually need, not just what sounds cool to build.
Enterprise AI will probably look less like “one model to rule them all” and more like a messy portfolio of models, agents, vendors, internal tools, data sources, and governance layers.
The opportunity is not just building agents. It is keeping the whole system coherent.
That is also why domain-fit smaller models are interesting.
Not every enterprise AI task needs a frontier model. For narrow workflows, a trained smaller model can reduce external API calls, limit token ingestion outside the company, and make systems cheaper and more controllable.
I explored this with Gemma for GCP infra routing:
https://t.co/zqL8JzJRJk
Enterprise AI will probably look less like “one model to rule them all” and more like a messy portfolio of models, agents, vendors, internal tools, data sources, and governance layers.
The opportunity is not just building agents. It is keeping the whole system coherent.
That is also why domain-fit smaller models are interesting and is worth checking out.
Not every enterprise AI task needs a frontier model. For narrow workflows, a trained smaller model can reduce external API calls, limit token ingestion outside the company, and make systems cheaper and more controllable.
I explored this with Gemma for GCP infra routing:
https://t.co/zqL8JzJRJk
This is why I’ve been experimenting with LoRA on smaller models for engineering tasks.
For some workflows, the question is not just “is the model smarter?”
It is: “can a smaller model be trained to fit this domain reliably?”
I tried that with Gemma for GCP tool routing:
https://t.co/zqL8JzJRJk