It didn't behave contrary to what I told it. I specifically told it to use Fable 5.2 for all the review subagents. I didn't realize it was going to drain my usage that fast. This was my mistake.
Fair. I read it as it using the wrong model to spin up the agents. The general question of liability remains valid and interesting, even if your case it wasn't a match to the premise of the question.
I think it's about the balance or so. These days, I spend an incredible amount of time on GitHub pull requests, trying to outsmart the AI and find its mistakes. At best, this results in even better code or solutions. But I also make sure the AI has to convince me why it's right.
Can't get that data, for a few reasons. Number one, German petrol stations are only required to report E5, E10, and diesel to the MTS-K, which then distributes this data to authorised consumers.
Number two, there is no national standard for high-octane fuels: Super E5 and Super…
I see there's MCP integration. Does it support creating subdomains? For example, I have myapp.test, and tenant.myapp.test. Will the agents be able to create tenant2.myapp.test, tenant3.myapp.test, etc.? 🎉
Not trying to bash on you, just genuinely curious -- why do people build demo apps, examples, etc., in any language other than english? I clicked on the link, I don't see an obvious language selector, and I immediately closed the browser tab.
Fair point! The first demo defaults to Japanese and doesn’t have a language selector.
I’ve also deployed a separate branch with a locale switcher supporting 8 languages, including English.
You can try it here:…
They’ve given so many hints that are “dark avatar”-adjacent without being overtly clear about it. Personally I won’t believe she’s a dark avatar until the evidence is crystal clear.
It doesn't need to do it from scratch. You can find a free, or buy a nice looking vue template (I don't want to advertise anyone, but I went with TailAdmin), chuck all the template files into a /resources/template, and tell the agent to use those files to build you the admin…
Is this approach paired with a totally headless API and for a relatively small admin panel? If so then I can see the logic. Otherwise there are too many benefits to Filament and its growing list of plugins to ignore it as a fast and effective way to build a feature-rich admin…