brunaxLorax

6 ms·

1.
by brunaxLorax 26d ago
Cool
2.
Ask HN: Is someone tweaking classic ROM games with AI?
3 points by brunaxLorax 26d ago|2 comments
3.
by brunaxLorax 2mo ago
It's hard to keep track of all those launches, I agree. I would separate 2 usages of LLMs: - LLM is integrated into a workflow/app for a classification or whatever job: scoring outputs (evals, KPIs) and choosing a fit between qual
4.
by brunaxLorax 2mo ago
a French human doing its best to sound punchy in English :)
5.
by brunaxLorax 2mo ago
Yes. orchestrator > smart router
6.
by brunaxLorax 2mo ago
Sounds like an orchestrator for me ratter than a router
7.
by brunaxLorax 2mo ago
Agree
8.
by brunaxLorax 2mo ago
We tried different things: heuristic, TF-IDF and LLMs. I voluntarily didn't talk about the tech because it doesn't fix the problems mentioned by switching models on the fly.
9.
by brunaxLorax 2mo ago
100% agree. MoE is the perfect example: reducing FLOPs while keeping intelligence
10.
by brunaxLorax 2mo ago
All inference providers (labs and neoclouds like TogetherAI or Fireworks) are incentivized to be efficient to be more competitive. For example MoE reduces compute without reducing output quality. I would not be surprised if they end up impl
11.
by brunaxLorax 2mo ago
Cheers, good luck!
12.
by brunaxLorax 2mo ago
Could be. In that case many routers are concerned as they all have more or less the same category buckets.
13.
by brunaxLorax 2mo ago
Yes, providers have downtime and retry/fallback solves this problem.
14.
by brunaxLorax 2mo ago
I didn't know that! I thought that all models had the same features no matter the provider
15.
by brunaxLorax 2mo ago
I didn't know about Tokenless, the approach seems really innovative, if it works it fixes the "Complexity cannot be deduced from the prompt alone" problem. However you still have the other hidden costs: cache, breaking behavi
16.
by brunaxLorax 2mo ago
If your router has GDPR/ZDR/EU compliant, it doesn't make your provider compliant. You're just adding a middleman.
17.
by brunaxLorax 2mo ago
Agree. The orchestrator pattern (big model managing smaller ones) works already well
18.
Everyone is building LLM routers, we deprecated ours(manifest.build)
132 points by brunaxLorax 2mo ago|86 comments
19.
Show HN: Modelparams.dev: AI Model Parameters Database (UI, API, NPM)(modelparams.dev)
2 points by brunaxLorax 4mo ago|0 comments
20.
by brunaxLorax 8mo ago
I agree. However as you said, you can consider code agents like human contributors. My feedback is that an army of Claude Code instances with a strict CLAUDE.md file is more rigorous than a human team.
21.
by brunaxLorax 8mo ago
I recently came across https://claudecode.run/ (not affiliated). There are currently several similar products that help that multi-instance Claude Code layout
22.
by brunaxLorax 8mo ago
How quickly? There is no limit to that. If I can do my day of work in few hours I would be glad to take the afternoon off or to go twice as fast (importunately that's more the second!)
23.
by brunaxLorax 8mo ago
With git worktrees you can you have your agents working on literally different folders so they don't step up on each other.
24.
Coding assistants are slow. So we multitask
4 points by brunaxLorax 8mo ago|8 comments
25.
Show HN: Convert any WordPress website into an MCP app(github.com)
1 points by brunaxLorax 10mo ago|0 comments
26.
by brunaxLorax 2y ago
Fixed ! thank you
27.
by brunaxLorax 2y ago
Hello, Manifest dev here, most backend-as-a-services rely on an UI and it's harder for AIs. In comparison, Manifest high-level DSL is really understandable by gen AIs. It's also very easy to validate in comparison to bootstrap fra
28.
by brunaxLorax 2y ago
correct :)
29.
by brunaxLorax 2y ago
Hello ! Manifest dev here, they are on the way ! There is a DB sync at the moment that does the job but we are going to implement the migrations soon :)
30.
Manifest – 1k Stars Later
1 points by brunaxLorax 2y ago|0 comments

More ›