All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
Addresses PR #793 re-review #3 (F1/F3 already confirmed closed). Both fixes TDD red-first on this branch (7 tests red against the prior head, then green). F2a (BLOCKER) — verifyListenerIdentity no longer accepts a listener by BASENAME. The old code ran `if (basename(exePath) === CLAUDEX_PROXY_BINARY) return 'ok'` unconditionally, so a same-uid process running `/tmp/claude-code-proxy` (right name, wrong path) was trusted. On a shared-uid host that is the squatter vector, not hypothetical — uid is NOT a trust boundary there, the executable path is. Now: when the expected proxy path resolves we require an EXACT canonical-path match (both sides canonicalized via realpath for symlinks); there is NO basename fallback. If the expected path can't be resolved, or either path can't be canonicalized, we fail closed (`unknown`). New tests: wrong-path/right-basename → wrong-exe; unresolved expected → unknown; uncanonicalizable → unknown; and a symlink-resolution case that canonically matches → ok. F2b (BLOCKER) — runProxyPreflight now verifies listener identity too. Previously `ok` was `bin.present && auth==='valid' && live` where `live` is /healthz-2xx only, so a squatter answering 2xx yielded `ok:true` and any consumer of the report (the phase-2 launch path) would route Claude traffic to it. Added `verifyListener` to PreflightDeps + a `listenerVerdict` field; `ok` now requires a trusted verdict; a live-but-unverified responder emits a non-sensitive problem (port + verdict only — no listener command line or token). Identity is not checked when the port is dead (no listener to trust). New tests: each non-ok verdict fails preflight and leaks no token material; dead proxy skips verify. Gates green: typecheck, lint, format:check; full mosaic suite 1115 passing; claudex-proxy.ts coverage 90.57% stmts/lines, 89.06% branch (>= 85%). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mosaicstack/mosaic
CLI package for the Mosaic self-hosted AI agent platform.
Usage
mosaic wizard # First-run setup wizard
mosaic gateway install # Install the gateway daemon
mosaic config show # View current configuration
mosaic config hooks list # Manage Claude hooks
Headless / CI Installation
Set MOSAIC_ASSUME_YES=1 (or ensure stdin is not a TTY) to skip all interactive prompts. The following environment variables control the install:
Gateway configuration (mosaic gateway install)
| Variable | Default | Required |
|---|---|---|
MOSAIC_STORAGE_TIER |
local |
No |
MOSAIC_GATEWAY_PORT |
14242 |
No |
MOSAIC_DATABASE_URL |
(none) | Yes if tier=team |
MOSAIC_VALKEY_URL |
(none) | Yes if tier=team |
MOSAIC_ANTHROPIC_API_KEY |
(none) | No |
MOSAIC_CORS_ORIGIN |
http://localhost:3000 |
No |
Admin user bootstrap
| Variable | Default | Required |
|---|---|---|
MOSAIC_ADMIN_NAME |
(none) | Yes (headless) |
MOSAIC_ADMIN_EMAIL |
(none) | Yes (headless) |
MOSAIC_ADMIN_PASSWORD |
(none) | Yes (headless) |
MOSAIC_ADMIN_PASSWORD must be at least 8 characters. In headless mode a missing or too-short password causes a non-zero exit.
Example: Docker / CI install
export MOSAIC_ASSUME_YES=1
export MOSAIC_ADMIN_NAME="Admin"
export MOSAIC_ADMIN_EMAIL="admin@example.com"
export MOSAIC_ADMIN_PASSWORD="securepass123"
mosaic gateway install
Hooks management
After running mosaic wizard, Claude hooks are installed in ~/.claude/hooks-config.json.
mosaic config hooks list # Show all hooks and enabled/disabled status
mosaic config hooks disable PostToolUse # Disable a hook (reversible)
mosaic config hooks enable PostToolUse # Re-enable a disabled hook
Set CLAUDE_HOME to override the default ~/.claude directory.