1 pointby medivhX11 days ago2 comments
  • rizzo948 days ago
    I’ve been in a similar spot—spent a lot of time trying to get Moltbot (Clawdbot) running 24/7 on my own hardware. The troubleshooting, permissions, and skill integrations can easily take hours, and even small configuration mistakes break the whole setup.

    While exploring ways to reduce that friction, I came across PAIO. The setup was essentially one click, but it still gives control over credentials with BYOK and a privacy-first approach. For me, it highlighted how much overhead self-hosting introduces versus a managed, secure personal AI—though I still see the value in projects like yours for learning and experimenting with local-first AI.

    It might be worth adding a section comparing “full DIY vs managed but privacy-preserving AI” workflows—could help newcomers decide which path fits their goals.

  • medivhX11 days ago
    Hi HN,

    I’ve been following the development of Clawdbot (a local AI OS) and realized that while the core project is brilliant, there’s a steep learning curve for non-hardcore developers—especially when it comes to 24/7 deployment on hardware like the new Mac Mini M4.

    I built getclawdbot.org to bridge that gap. My goal is to make it the "missing manual" for the project. A few things I’ve added beyond the official README:

    Hardware Optimization: Deep dives into why Mac Mini is the ideal low-power host.

    Searchable Troubleshooting: I’m indexing common errors (like the notorious Gateway Pairing issue) to save people hours of debugging.

    Skill Showcase: A more visual way to explore what these agents can actually do (browsing, Notion sync, etc.).

    It’s still early days, and I’m actively adding more skill guides and local-first automation tips. I'd love to hear your thoughts on what’s missing or what local AI use cases you're most excited about!