Skip to content

v0.1.2 — reject invalid admin handle at init

Choose a tag to compare

@pouriamrt pouriamrt released this 18 Apr 21:12

Patch release that prevents a foot-gun at relay init.

What was wrong

If you typed a capitalized handle at the Admin handle: prompt (e.g. Pouria), init happily wrote it to the DB. Everything superficially worked — mesh admin add-user succeeded, list_peers returned the entry — but every outbound message from that user hit invalid_message at the relay because HANDLE_REGEX (used by EnvelopeSchema on the from field) only allows ^[a-z][a-z0-9_-]{0,31}$.

Users on v0.1.0/v0.1.1 who created a capitalized admin will still see this. The fix prevents new installs from ending up in that state.

Fix

initTeam() now validates admin_handle against HANDLE_REGEX up front. Bad handle → clear error naming the rule, no partial DB writes.

Upgrade

docker pull ghcr.io/pouriamrt/claude-mesh/relay:v0.1.2
docker stop mesh-relay && docker rm mesh-relay
docker run -d --name mesh-relay --restart unless-stopped   -p 8443:8443 -v mesh-data:/data   ghcr.io/pouriamrt/claude-mesh/relay:v0.1.2

Data survives in the mesh-data volume.

If you already hit this on v0.1.0/v0.1.1

Your DB has an invalid handle row. Add a new lowercase admin and re-pair:

mesh admin add-user --handle mesh-admin --display-name "<your name>" --tier admin
mesh pair <paircode> --label "my-laptop"
# optionally: mesh admin disable-user <old-capitalized-handle>
claude --dangerously-load-development-channels server:claude-mesh-peers