It matters less to me that the helper is an AI/human than the kind of help I'm getting.
The bigger problem to me is "help" is always framed as my needing to be educated, not a problem with the service. This is especially prevalent for technical customers who are legitimately trying to draw attention to a bug in the platform only to get how-to help articles pasted back to them.
> "help" is always framed as my needing to be educated
For many users, this is often the case, and front line AI support like this can handle that pretty effectively while giving your case faster live support. Would you rather sit behind 4 people in the queue trying to figure out why their device doesn't work without batteries when it's not plugged in or have them deal with AI to solve the problem while you get your real issue sorted out quickly after dealing with a handful of basic prompts?
I agree that's why I would prefer to have AI if it does the job better and if it can be further trained to understand when to escalate in the case of a more technical user which I have found humans rarely do.
I wouldn't mind, if it ended up getting me a human at the end of the process.
It's not quite at the level of the "shibboleet" XKCD, but I did once manage to get a much higher support tier at Comcast who was able to verify that 1) I had a problem that was their fault and 2) fix it. Even that guy was halfway on a script. Y'know, after I've read you a ping timeout three times from the Windows command line, I probably shouldn't have to read it verbatim to you again. It hasn't changed.
Or technical customers with a case that was not handled properly. I'm thinking of long, long ago, ISP changed the Usenet server and didn't document it--not on their website, not with their tech support. It shouldn't have taken an hour and a third level support person to get we changed providers, here's the new address. First two levels simply couldn't comprehend that it was not a third party system that I was having trouble with.
I understand the article is actually not about support chatbots specifically but seeing the conversation here talked about that it's not out of place to join in that discussion.
Attempting to shame people by accusing them of not reading is hardly constructive. This isn't Reddit.
There are many concerns and areas for improvement with open claw and other similar projects (continuous loop script with broad OS access that manages your agents and interfaces with a standard messaging app)
However, file size I have never seen on that list. I would rather offer for something that is even bigger in file size so it afford certain functionality like better security tighter permissions however it would do that.
File size is a legit property to keep in mind if your goal is to create an agent that runs on ESP32 boards. They don't expect you to run Zclaw on Mac Mini.
For something like OpenClaw yes, but not for Zclaw. I think the naming is more about riding the current wave of Claw-related interest rather than positioning it as competition or replacement for other clawies.
Zclaw is about running an agent in your embedded system.
Before you know it your smart thermostat will be blogging. The joke is on everyone who thought IoT couldn't get any worse. Just imagine the new landscape of security vulnerabilities this opens up.
Everything runs in containers (I run it on a server along with everything else), plugins have a permission system so eg the AI can read emails but not delete or send, etc.
I really like it, I run it as my main agent and it has been extremely helpful.
So you do things one step at a time and timebox as you go? This method probably doesn't need its own name. In fact I think that's just what timeboxing is.
FWIW Mikado seems to be the name of that game where you pick up one stick at a time from a pile, while trying to not disturb the pile. (I forget the exact rules). So it isn’t as if somebody is trying to name this method after themselves or something, it is just an attempt at an evocative made up term. Timeboxing is also, right? I mean, timeboxing is not recognized by my spell checker (I’d agree that it is more intuitive though).
Mikado is the name of an opera (by Gilbert and Sullivan) in which someone is deemed to have been executed without actually having been executed. Sounds like an ideal test strategy to me: yes, all the tests were executed, just not actually run.
when I saw the title I was expecting a reference to the opera. was wondering if they were somehow going to work in the exchange
"Besides, I don't see how a man can cut off his own head." "A man might try." in reference to gradually removing bits of the old code.
I suspect it was invented the first time a parent dropped a pile of sticks because their bored kids were distracting them. “Ok kids, new game, pick those sticks up as quietly and tediously as possible.”
There are important additions beyond timeboxing, at least according to the post. Notably, reverting your changes if you weren't able to complete the chosen task in the time box and starting over on a chosen subset of that task. I can imagine that part has benefits, though I haven't tried it myself.
Not sure what you have against it. Works great for me. No subscription required. And if I do want to pay for ad free shows and support creators it's easy to do so.
Use whatever you like but I don't think Podcast app users are rare by any stretch of the imagination.
reply