Clawdi

Genuine q as a builder, when an agent has persistent memory + cron + app connections all running in your cloud, what does the off ramp look like if I want to pull my setup out 6 months in ? Memory state is usually the part that locks you in hardest, hard to replicate elsewhere once its built up context.

forcing people to share personal API keys or personal agent memory. In other words: team-level vaults, team-level environments, and permissioned access instead of one giant shared account.We started with personal AI environments first because that pain was immediate, but multi-user / org workflows are one of the next big things we want to support.

This is the missing infrastructure layer. The agents get all the attention but the environment they run in is what makes or breaks long-term usability. Great insight from the Clawdi team.

That's a legitimate concern—abstraction layers only work if they reduce complexity, not add to it. Have you looked into their uptime SLA and whether they offer fallback mechanisms or local-first options for critical agents? Understanding their infrastructure resilience would probably be the first thing I'd validate before committing.

Congrats on launch⭐. How does persistence work for memory and API keys between agents?

I like the vision, but I'm a bit wary of adding another abstraction layer on top of my already-complex agent stack. What happens to my workflow if Clawdi has downtime

Genuinely excited about this. Most AI agent tools compete on flashy capabilities. Clawdi is competing on reliability and persistence — which is actually what matters for daily use. Rare positioning.

Installed in 5 minutes, synced my OpenClaw config to the hub, then spun up Hermes pointing at the same environment. Actually worked. This is the boring-but-essential infrastructure the space has been missing.

Solid concept, but "shared memory across agents" needs a strong access control story. If one compromised agent can write to the shared context, it could affect all others. How are you thinking about isolation?

Is there a way to selectively share part of an environment with a collaborator without giving full access? Thinking about pair-programming-style AI workflows.

Hey, do you have plans for team or org accounts? I'd love to let my team access shared environments without sharing personal API keys.

Been waiting for something like this. I've rebuilt my agent setup from scratch 3 times this year switching between frameworks. The "iCloud for AI agents" framing really clicks. Upvoted and sharing this with my team.

Running OpenClaw on Telegram and Claude Code locally — this is literally built for my setup. Installing now. Congrats on the launch! 🎉

Hey Product Hunt! 👋 I'm Xiaolu, part of the team at Clawdi, specifically focusing on product research and agent development. It's incredibly exciting to finally share what we've been building with this community.The honest origin of Clawdi: I kept losing my agent setup. Every time I switched from one framework to another, or picked up a new device, I'd spend the first hour just reconstructing context, re-entering API keys, and re-teaching the agent how I work. It felt like the AI was getting smarter, but the infrastructure around it was still completely fragile.So we built the layer that was missing. Not another agent, not another framework, just a persistent environment that travels with you. Your memory, skills, secrets, and connected tools live in Clawdi. Every agent you run connects to it. Switch frameworks, add a device, spin up a new agent , your entire setup is already there.What I'm most proud of: it's MIT-licensed and self-hostable from day one. We didn't want anyone to have to trust a black box with their API keys.Would love to hear from anyone who's felt this pain, especially if you're running multiple agents in parallel or switching between Claude Code and Codex regularly. That's exactly the use case we've been obsessing over.Happy to answer any questions below. 🙌

I’ve known the team for a few years. They’ve always been one of the scrappiest teams building in this space. When they told me they built Clawdi on top of OpenClaw, my first question was simple: What can it actually do?I actually tried OpenClaw briefly when it came out because I heard a lot of AI savvy people had already been using agents to build their "team.” But I gave up after 30 minutes. Well, it was because I didn’t want to spend my time setting things up, not because it wasn’t powerful. Hermes is powerful too, but setup is still the hard part. Clawdi is where it clicked for me. It took me about 2 minutes to get started, and now I use it for running parts of my Instagram workflow and a bunch of other things. Nothing fancy, just small things that save time every day.And before anyone asks, yes, your data stays yours. API keys are encrypted and only accessible by you.These days I’d go to Clawdi just to see what new agents or integrations they’ve shipped, and what else I can offload to my little lobster assistant.Would love to see how others are using it and what workflows you try on Clawdi.