You can connect it to any anthropic compatible endpoint(kimi allows this) but it's a weird choice, given that Open code, pi.dev and others are open source.
Very timely, the final report has been released today.
I hadn't read the document you referenced, and I admit don't have the prior knowledge, nor the time, to fully understand all the implications of what it says. My opinion is then the result of reading and listening a variety of experts and news sources, and it will have some biases, for sure.
Still, I have skimmed the final report to see if there was something that I could understand from first hand (and to support my original point, not gonna lie), and I found this:
_The increasing penetration of variable renewable and
distributed generation, further market integration,
broader electrification, and evolving environmental
and geopolitical risks place the European electricity
system under increasingly challenging operational
conditions, requiring higher levels of resilience._
Do you really think that my original point (as uniformed as it might be), namely, that the levels renewable energy currently present in the spanish grid require significative investments, was wrong?
It's not that easy, and the 2025 blackout good evidence of that. Renewables need a grid that's engineered for them and that require significative investments. Without them, closing power plants (of any kind) is, IMO, nonsensical.
Ironically, Spain has plenty of Uranium, but there is an environmental law that doesn't allow its mining.
The difference is that in this case the agent loop is executed, which has all the caching and behaviour guarantees. What I assume OpenClaw is doing is calling the endpoint directly while retaining its own "agent logic" so it doesn't follow whatever conventions is the backend expecting.
How important is that difference, I can't say, but aside the cost factor I assume Google doesn't want to subsidize agents that aren't theirs and in some way "the competition".
Your question
So does nobody in Europe use an EDR or intercepting proxy since GDPR went into force?
Given that a regulator publishes a document with guidelines about DPI I think it rules out the impossibility of implementing it. If that were the case it would simply say "it's not legal". It's true that it doesn't explicitly say all the conditions you should met, but that wasn't your question.
(IANAL) I don't think there is a simple response to that, but I guess that given that the employer:
- has established a detailed policy about personal use of corporate devices
- makes a fair attempt to block work unrelated services (hotmail, gmail, netflix)
- ensures the security of the monitored data and deletes it after a reasonable period (such as 6–12 months)
- and uses it only to apply cybersecurity-related measures like virus detection, UNLESS there is a legitimate reason to target a particular employee (legal inquiry, misconduct, etc.)
I agree with the sentiment, but I think it's a pretty naive view of the issue. Companies will want all info they can in case some of their workers does something illegal-inappropiate to deflect the blame. That's a much more palpable risk than "local CA certificates being compromised or something like that.
And some of the arguments are just very easily dismissed. You don't want your employer to see you medical records? Why were you browsing them during work hours and using your employers' device in the first place?
GPT actions allowed mostly the same functionality, I don't get the sudden scare about the security implications. We are in the same place, good or bad.
Btw it was already possible (but inelegant) to forward Gpt actions requests to MCP servers, I documented it here
Custom connectors are cool and a good selling point but they have to be remote (afaik there is no Le Chat Desktop) so using it with local resources it's not impossible, but hard to set up and not very practical (you need tail scale funnel or equivalent).