← ClaudeAtlas

fennec-macos-developmentlisted

Build, sign, restart, and debug the Fennec macOS companion, shared-channel session operations, UI state synchronization, Keychain access, cloud takeover, and CLI launch errors. Use for Fennec macOS development or recurring signing, session latency, and takeover problems; not for unrelated Runta runtime work.
runta-dev/fennec · ★ 4 · AI & Automation · score 67
Install: claude install-skill runta-dev/fennec
# Fennec macOS development Preserve existing source changes, user credentials, cloud sessions, and unrelated processes. Do not rebuild credentials, reset model preferences, or blindly retry an uncertain launch. ## Reuse the local signing identity Development builds must use the existing `Fennec Local Development` certificate in the user's login Keychain. Never switch back to ad-hoc signing or generate a new certificate for each build: changing the signing identity can make macOS request Keychain authorization again. ```sh ./scripts/create-development-identity.sh go build -trimpath -o /tmp/fennec-local-build/fennec-daemon . FENNEC_DAEMON_BINARY=/tmp/fennec-local-build/fennec-daemon ./scripts/build-macos.sh codesign -dvv build/Fennec.app 2>&1 | grep Authority ``` The creation script is idempotent. It must return the existing identity rather than importing another certificate. The expected signature authority is `Fennec Local Development`. The packager defaults to this identity; `FENNEC_SIGN_IDENTITY=-` is only an explicit ad-hoc escape hatch, not the normal development workflow. The first use of a newly imported private key may require the user to allow `/usr/bin/codesign` in the system authorization dialog. Do not bypass the dialog, weaken Keychain ACLs, or allow every application to read credentials. After that one-time authorization, rebuild once more and verify that signing finishes without another prompt. The signing key and the Runta login token are separate Keycha