△

Clawdie AI

AI Assistant · Robot OS · clawdie.si

Most AI assistants stop at conversation.
Clawdie doesn't.
She lives on your hardware, remembers your world, and is being built to drive the machine that manufactures your dome.
From first message to finished structure — the two of us are building this together.

△ Follow the build

What is Clawdie

Clawdie is a self-hosted personal AI assistant — running today, in production, on FreeBSD. She lives on your own hardware, connects through Telegram, remembers everything in a Postgres database, and is accessible via a tmux glass-pane console. No corporate cloud. No subscription. No data leaving your server.

She is built on the OpenClaw ecosystem — the open source personal AI assistant framework created by Peter Steinberger — and adapted to run on FreeBSD with a Tailscale-secured infrastructure.

Building a working AI assistant is constant work. Clawdie is actively developing. Our mission is always one step ahead — connecting the assistant to the physical machine that will build domes.

Cloud AI assistant
  • Runs on someone else's server
  • No persistent memory by default
  • Data leaves your hands
  • Subscription required
  • Black box — no control
  • Conversation only
  • Deprecated when provider decides
Clawdie
  • Runs on your own hardware
  • Postgres persistent memory
  • Data stays on your server
  • Open source, self-hosted
  • Full control, full transparency
  • Conversation + construction
  • Yours forever

The Claw ecosystem

Clawdie is part of a growing family of open source AI assistants built independently by developers and hardware makers around the world. We stand on their shoulders.

OpenClaw

The original. Personal AI assistant you run on your own devices. Multi-channel (Telegram, WhatsApp, Slack, Discord), voice, browser automation. Created by Peter Steinberger — the foundation Clawdie is built on.

TypeScript · Node ≥22 · MIT · openclaw.ai

ZeroClaw

Rust-based AI agent infrastructure built for minimal resource consumption. A runtime OS for agentic workflows — swap models, tools, memory, and execution environments freely. Built by the Harvard/MIT/Sundai.Club community.

Rust · MIT / Apache 2.0 · ZeroClaw Labs

PicoClaw

Ultra-lightweight AI assistant written in Go. Runs on $10 hardware, under 10MB RAM. Targets RISC-V, ARM64, x86_64 — Raspberry Pi Zero, LicheeRV-Nano, MaixCAM. Built by Sipeed, a hardware company.

Go · RISC-V / ARM64 · Sipeed · Embedded △

TinyClaw

Independent alternative to OpenClaw. Plugin architecture, self-improving memory, smart query routing to cut LLM costs. Discord-like interface with 5-layer security. Built by Waren Gonzaga.

TypeScript · Svelte · Plugin-based · Waren Gonzaga

Each project has a distinct identity and target. None are forks of each other. The ecosystem is young, real, and growing fast.

Our setup

Most AI tooling assumes Linux. We run FreeBSD — and document everything that works, so others don't have to figure it out from scratch.

OS
FreeBSD 15 Self-hosted, no corporate cloud. pf firewall, nginx, Let's Encrypt. The same server that runs osa.smilepowered.org.
NET
Tailscale mesh WireGuard-encrypted network connecting all servers and the operator's laptop. Clawdie communicates securely between nodes without exposing ports.
UI
Telegram interface The channel the operator already uses. No new app to install, no new habit to build. She meets you where you are.
MEM
Postgres persistent memory Not ephemeral. Clawdie remembers across sessions, across days, across restarts. Memory is the difference between a tool and an assistant.
CON
tmux glass-pane console Direct terminal access to the AI interface — for the operator who wants to see exactly what is running and why.

The bigger picture

Status — design stage

What follows is vision, not prototype. The CNC robot is being designed openly, with AI assistance, one step at a time. This page is part of that process. We publish the thinking before the build.

An AI assistant that only talks is only half useful. The goal is to connect Clawdie to a physical machine — an open source CNC robot designed to manufacture geodesic dome components.

Clawdie becomes the operating system of the robot — translating dome designs from OSA into machine instructions, managing the build sequence, monitoring the process, and logging everything back into persistent memory.

"The CNC robot is not a feature. It is the point. AI that builds things is fundamentally different from AI that talks about things."

The hardware stack is being designed for openness — RISC-V where possible, documented at every step, replicable by anyone with access to basic CNC equipment. PicoClaw (Sipeed) is a natural candidate for the embedded controller layer, with Clawdie as the high-level brain coordinating over Tailscale.

01
Open hardware, open software Every schematic, every config, every G-code template published openly. Same philosophy as OSA — no patents, no paywalls.
02
Design with AI, build with AI The robot is being designed using AI assistance. When built, it will be operated by AI. The loop closes.
03
Replicable anywhere Local materials, standard CNC components, documented assembly. The goal is a machine anyone can build in a workshop, not a product only a factory can produce.
04
Connected to OSA Dome designs live at osa.smilepowered.org. Clawdie reads them, translates them, and feeds the machine. Design to dome — one continuous chain.

The full stack

Clawdie and OSA are two parts of the same mission. One is the why. One is the how.

OSA designs the dome. Clawdie builds it. — the two of us, working on it

Visit osa.smilepowered.org for the manifesto, the open dome designs, and the case for why we are still building boxes when we know how to build better.

Follow the build

No membership. No newsletter. Just open work, published as it happens. If this resonates — follow, contribute, replicate. The two of us can build this.

View on Codeberg Visit OSA Get in touch

This server

clawdie.si runs on FreeBSD 15, nginx, and Let's Encrypt — entirely open source, self-hosted, zero corporate cloud dependency. Same server as OSA. Same principles.

Everything documented here is replicable. If it runs on our server, it can run on yours.