Thank you for your message. English is not my native language, so I sometimes use translation tools. I will try my best to reply to you in more direct and understandable language. Thank you for your patience.
No telling if this "hack" wasn't really just prompt engineering followed by hallucinations, particularly if the "hacker" was attempting to exfil data via the agent.
It's interesting... Different LLM models seem to have a few sentence structures that they seem to vastly overprefer. GPT seems to love "It's not just X, it's Y", Claude loves "The key insight is..." and Gemini, for me, in every second response, uses the phrase "X is the smoking gun". I hear the smoking gun phrase around 5 times a day at this point.
I can't help but feel there is a funny pattern going on.
A lot of companies want to embrace AI, agents, etc. so they make their platforms easier to use by AI, implementing whatever the latest craze is.
I imagine we're going to see a lot more APIs open up (agentic finances?), a lot of granular access controls, etc.
Where was all of this when regular users had been asking for it for _years_?
Empowering users in general is a good thing, so, in a way, it's a good thing that OpenClaw and things of this nature are exposing all the issues with access controls and API interactions that many of our services have.
Now we just need a reason for AI agents to need "dark mode" on websites...
TIL there's a batch API.. This seems like something a lot of AFK coders should be using.
The pattern for those users is typically they would set some kind of token budget, but their agent would still try to burn through those tokens as quickly as possible, rather than a more sensible "do this at your own leisure over the next ~8 hours".
Looking forward to further commodification of LLM usage in the future to make it more affordable. Batch APIs and more freedom over scheduling/priorities/deadlines seems like the more sustainable approach to driving costs down.
I tried teams, good way to burn all your tokens in a matter of minutes.
It seems that the Claude Code team has not properly taught Claude how to use teams effectively.
One of the biggest problems I saw with it is that Claude assumes team members are like a real worker, where once they finish a task they should immediately be given the next task. What should really happen is once they finish a task they should be terminated and a new agent should be spawned for the next task.
reply