It could simply save a timestamp of the “begin timer” message and compare it to the timestamp of the “end” message. It’s not that complicated, and writing a script and executing it is overkill… It just needs access to a calculator skill.
Yes, it handles it better, but it’s still a dumb approach and waste of energy.
It could simply save a timestamp of the “begin timer” message and compare it to the timestamp of the “end” message. It’s not that complicated, and writing a script and executing it is overkill… It just needs access to a calculator skill.
Yes, it handles it better, but it’s still a dumb approach and waste of energy.
Aren’t we saying exactly the same? Give it an MCP server or a native skill that CAN track time.
Well, yes. I’m just responding to the anthropic doing it better part, yes but not by much.
‘const timePassed = (start, end) => end - start;’ is much simpler than creating a whole timer.