Just gave this a try and I really like it. Was able to interact with Eve via iMessage and web UI to download a sample healthcare dataset and run some analyses on it. (Currently it's a bit unpredictable about which UI it returns results to, but if that gets fixed then this would be great for doing development on the move.) Also set it up to run some scheduled news summarisation tasks. I like how it allows for safe experimentation on OpenClaw functionality. Like others on this thread, I'm a bit hesitant about connecting to email services without knowing more about the developer and how they use data from connected services, but there's a lot of interesting things you can do with this even without connecting to anything. (The free credits are v helpful too, although the underlying Claude models burn through them quickly.) Thanks zachdive for sharing this, I had fun trying it out!
Glad you enjoyed it and thanks sm for the feedback! Working on inter-agent rn, so it should be more deterministic about where it surfaces results back very soon!
Hey my bad, it's fixed now! Eve deployed it on my account as a static site (hosted in cloudflare R2) but the cloudflare worker wasn't pointing at it correctly, which led to a weird fallback behavior from cloudflare where it just gives back an empty file (zero bytes). Fixed :)
“All .new domain names are required to comply with the .new Registration Policy, which features a usage-based restriction to ensure that all domains are being used for new actions. That means that all .new domains registrations must:
Be used for action generation or online content creation;
Take the user directly into the action generation or content creation flow;
Resolve to the action within 100 days of registration;* and
Allow Google Registry to verify compliance at no cost.
While anyone can register, domains that don’t comply with this usage policy may be suspended or deleted by Google Registry without refund. So be sure you review the full .new Registration Policy before you register your .new domain to ensure that it meets our policy requirements.”
Interesting approach. What's the main difference between
this and just self-hosting OpenClaw with a simple wrapper?
Trying to understand where the managed layer adds the most
value — is it mostly around auth and multi-user, or
something deeper in the infrastructure?
I think this boils down to the ICP of white collar workers.
Mainly:
- It make it super accessible to begin using the agent with no setup friction
- Mitigates security concerns by users not comfortable with using openclaw for their job
Just gave this a try and I really like it. Was able to interact with Eve via iMessage and web UI to download a sample healthcare dataset and run some analyses on it. (Currently it's a bit unpredictable about which UI it returns results to, but if that gets fixed then this would be great for doing development on the move.) Also set it up to run some scheduled news summarisation tasks. I like how it allows for safe experimentation on OpenClaw functionality. Like others on this thread, I'm a bit hesitant about connecting to email services without knowing more about the developer and how they use data from connected services, but there's a lot of interesting things you can do with this even without connecting to anything. (The free credits are v helpful too, although the underlying Claude models burn through them quickly.) Thanks zachdive for sharing this, I had fun trying it out!
Glad you enjoyed it and thanks sm for the feedback! Working on inter-agent rn, so it should be more deterministic about where it surfaces results back very soon!
Let me just log into this random site with my Google account with literally zero information about what it is
Yikes and a link in their post just downloads a file. I don't like this.
Hey my bad, it's fixed now! Eve deployed it on my account as a static site (hosted in cloudflare R2) but the cloudflare worker wasn't pointing at it correctly, which led to a weird fallback behavior from cloudflare where it just gives back an empty file (zero bytes). Fixed :)
Right…it was “Eve” who did it.
Maybe spend more than twelve seconds looking at the slop your LLM produces before posting it where people might click?
Lol fair! There is sign up with email!
Any more info I could provide upfront?
It's very telling of the current state of this industry that OP comes only 2 h after this other post: https://news.ycombinator.com/item?id=47721955
What does it tell us exactly?
Do you have a personal take on this?
“All .new domain names are required to comply with the .new Registration Policy, which features a usage-based restriction to ensure that all domains are being used for new actions. That means that all .new domains registrations must: Be used for action generation or online content creation; Take the user directly into the action generation or content creation flow; Resolve to the action within 100 days of registration;* and Allow Google Registry to verify compliance at no cost. While anyone can register, domains that don’t comply with this usage policy may be suspended or deleted by Google Registry without refund. So be sure you review the full .new Registration Policy before you register your .new domain to ensure that it meets our policy requirements.”
Thanks! I wasn't aware of that
Interesting approach. What's the main difference between this and just self-hosting OpenClaw with a simple wrapper? Trying to understand where the managed layer adds the most value — is it mostly around auth and multi-user, or something deeper in the infrastructure?
Please do not post AI generated replies on this site.
See: Don't post generated/AI-edited comments. HN is for conversation between humans https://news.ycombinator.com/item?id=47340079
I think this boils down to the ICP of white collar workers.
Mainly: - It make it super accessible to begin using the agent with no setup friction - Mitigates security concerns by users not comfortable with using openclaw for their job