clawdie-iso/live/operator-session/START-HERE.txt
Sam & Claude ba2f09f290 feat(seed): route seeded provider keys to provider.env for zero-touch boot
The live seed importer merged the active agent's provider keys into the
operator ~/.env, but colibri_daemon reads /usr/local/etc/colibri/provider.env
(rc.conf colibri_daemon_provider_env). So a personalized seed carrying real
provider keys never reached the daemon and no agent auto-spawned.

Route the active agent's non-BW_* keys into provider.env (0600 root) in
addition to ~/.env. The importer runs as root BEFORE LOGIN and colibri_daemon
REQUIREs LOGIN, so the daemon starts after the keys land and auto-spawns the
agent on first boot — no Join Hive click, no Vaultwarden round-trip, no typing.

This makes a personalized seed the zero-touch onboarding primitive: the image
stays generic/publishable, the FAT32 seed is the (offline) personalization
layer. BW_* still route to vault-bootstrap.env for the vault-fetch path.

Docs: seed README, START-HERE, and ONBOARDING-SIMPLIFICATION updated to
describe the direct-keys path (supersedes the xdg-autostart plan).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-22 08:56:46 +02:00

89 lines
1.8 KiB
Text

CLAWDIE OPERATOR USB — START HERE
=================================
This desktop opens quiet on purpose.
Colibri runs in the background; you choose when to open the operator UI.
FIRST ACTIONS
-------------
1. Save any notes you want in this file or close it.
2. Open "Colibri Dashboard" on the desktop when you are ready.
3. Use "Clawdie Hardware Report" if this machine needs diagnostics.
COLIBRI
-------
The daemon should already be running.
Check:
service colibri_daemon status
If needed:
mdo -u root service colibri_daemon start
Desktop launcher:
Colibri Dashboard
Terminal commands:
colibri status
colibri snapshot
colibri list-tasks
colibri list-skills
colibri-mcp tools
SECRETS / PROVIDERS
-------------------
Provider env:
/usr/local/etc/colibri/provider.env
If you are using Vaultwarden bootstrap:
- the image already knows the Clawdie Vaultwarden URL
- add BW_CLIENTID, BW_CLIENTSECRET, and BW_PASSWORD
- keep the file mode 0600
- restart colibri_daemon after edits
Example:
mdo -u root ee /usr/local/etc/colibri/provider.env
mdo -u root chmod 600 /usr/local/etc/colibri/provider.env
mdo -u root service colibri_daemon restart
LIVE SEED
---------
Seed partition label:
CLAWDIESEED
If this stick was seeded with provider keys, there is nothing to do: the
agent's keys were loaded before the daemon started, so Colibri auto-spawns
the agent on boot. Check with:
colibri status
Readable operator guide:
/usr/local/share/clawdie-iso/seed/README.txt
REFERENCE
---------
Full HTML reference:
/usr/local/share/clawdie-iso/bootstrap/index.html
Open manually:
firefox file:///usr/local/share/clawdie-iso/bootstrap/index.html
HARDWARE REPORT
---------------
Desktop launcher:
Clawdie Hardware Report
Terminal:
mdo -u root hw-report
PRIVILEGE MODEL
---------------
This USB does not use sudo.
Use:
mdo -u root <command>