clawdie/clawdie-ai
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

release: v0.8.0 Warden

Browse source 
Wayland-first display architecture — worker jails now use cage + Chromium
for agent browser automation, no bhyve VM required. Full subnet layout
defined (.1–.10 + .101+ workers). Shared ZFS pkg cache. Wayland stack and
bhyve prerequisites in host baseline by default, no feature flags.

New architecture docs: jail vs Docker IPC, Wayland display model, prompt
injection research with hardening checklist. CNC module section rewritten.
Sponsor link added. Version bump 0.7.2 → 0.8.0.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---
Build: pass | Tests: pass — Tests  414 passed | 10 skipped (424)
This commit is contained in:
Sam & Claude 2026-03-16 07:09:01 +00:00
parent 7947f5306e
commit 417418ded6
3 changed files with 31 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
html/docs-clawdie-si/docs/index.html
View file

@ -87,13 +87,13 @@
<div class="info-box success">
<span class="info-label">Current Release</span>
<p>
<strong>v0.7.2 — Docs Redesign + Skills Artifact Plan</strong><br>
Introduces <code>clawdie-hostd</code>: a root daemon on a Unix socket that
handles all privileged host operations (bastille, zfs, pf, service) via
whitelisted op handlers. PF RDR is now the canonical web edge — nginx runs
inside the <code>cms</code> jail, traffic arrives via <code>rdr pass</code>
rules written by <code>setup/pf.ts</code>. Self-healing control plane checks
at startup and every 5 minutes via <code>src/controlplane.ts</code>.
<strong>v0.8.0 Warden — Wayland-First Display, Full Subnet Layout, Security Docs</strong><br>
Worker jails now use <code>cage</code> + Chromium for agent browser automation —
no bhyve VM required. Full subnet layout defined (.1–.10 + .101+ workers).
Shared ZFS pkg cache wired into all jail steps. Wayland stack and bhyve
prerequisites in host baseline by default, no feature flags. New architecture
docs: jail vs Docker IPC, Wayland display model, prompt injection research
with hardening checklist.
</p>
</div>

32
html/docs-clawdie-si/index.html
View file

@ -78,7 +78,7 @@
<p>
Clawdie is a Self Hosted AI System built on top of FreeBSD. It follows the
<a href="/guides/nanoclaw-upstream.html">NanoClaw</a> upstream line, but runs with native <a href="https://docs.freebsd.org/en/books/handbook/jails/" target="_blank" rel="noopener">jails</a>, <a href="https://docs.freebsd.org/en/books/handbook/firewalls/#firewalls-pf" target="_blank" rel="noopener">PF</a>, <a href="https://docs.freebsd.org/en/books/handbook/zfs/" target="_blank" rel="noopener">ZFS</a>, and a
local <a href="https://codeberg.org/Clawdie/Clawdie-AI/src/branch/main/docs/BUILT-IN-KNOWLEDGE.md" target="_blank" rel="noopener">built-in knowledge</a> layer designed to reduce first-install LLM
local <a href="https://codeberg.org/Clawdie/Clawdie-AI/src/branch/main/docs/BUILTIN-KNOWLEDGE-SPEC.md" target="_blank" rel="noopener">built-in knowledge</a> layer designed to reduce first-install LLM
setup friction.
</p>
@ -229,7 +229,7 @@
<tr>
<td>Onboarding goal</td>
<td>General framework</td>
<td>Lower-friction bootstrap with local <a href="https://codeberg.org/Clawdie/Clawdie-AI/src/branch/main/docs/BUILT-IN-KNOWLEDGE.md" target="_blank" rel="noopener">built-in knowledge</a></td>
<td>Lower-friction bootstrap with local <a href="https://codeberg.org/Clawdie/Clawdie-AI/src/branch/main/docs/BUILTIN-KNOWLEDGE-SPEC.md" target="_blank" rel="noopener">built-in knowledge</a></td>
</tr>
<tr>
<td>Memory model</td>
@ -245,16 +245,30 @@
<section>
<h2>CNC module (concept)</h2>
<p>
Clawdie is moving beyond chat: setup, maintenance, docs lookup, and
machine-related workflows. The CNC module is currently a concept. Split
brain keeps stable operator knowledge separate from changing user context.
No public roadmap is promised yet.
The long-term goal is a CNC-enabled AI assistant — a system that understands
shop workflows, machine state, and operator context well enough to be genuinely
useful at a workbench, not just a chat window. That is the design target.
We are not there yet, and we are not pretending otherwise.
</p>
<p>
Agent System Skills carries the stable operating playbook. User/Agent Memory
carries shop, operator, or agent-specific context. That separation makes the
system easier to trust, audit, and grow.
What we are building now is the foundation that makes it possible: a stable
agent runtime, jail isolation, a privilege model that can be trusted in a real
shop environment, and Stripe built into core so the agent can eventually manage
its own hardware development lifecycle — from sponsorship intake to prototype
procurement. Code has little cost. Hardware is a different story.
</p>
<div class="info-box">
<span class="info-label">How to support hardware development</span>
<p>
When the sponsorship path is ready, it will live inside the agent itself —
not on a separate campaign page. Early sponsors will be the first to access
the CNC prototype. If this direction matters to you, the simplest thing you
can do right now is run the software, give feedback, and
<a href="mailto:hello@clawdie.si?subject=Become%20a%20Sponsor">become a sponsor</a>.
That is how a prototype becomes viable.
</p>
</div>
</section>
<div class="divider"></div>

2
package.json
View file

@ -1,6 +1,6 @@
{
"name": "clawdie",
"version": "0.7.2",
"version": "0.8.0",
"description": "Personal AI assistant. Lightweight, secure, customizable.",
"license": "BSD-3-Clause",
"type": "module",