ClawSight 0.9.5.7 focuses on reliable fresh-install access and independent Claude Managed Agent operation. Persistent Claude memory and shared Telegram sessions were already available in 0.9.5.5.
Fresh-install activation: each installation stores its own relay credential in macOS Keychain. New installations currently require one-time support approval: click Check Access, provide the displayed support code to ClawSight support, then click Check Access again after approval. A different macOS user account counts as a separate installation. Self-service email activation is not yet available.
Claude independence: selecting Claude Managed Agent no longer probes OpenClaw or uses its speech system. Claude uses its own configuration and ClawSight voice services, with macOS speech fallback; OpenClaw, Hermes, and Google Managed Agents are not prerequisites.
Cleaner agent switching: transient conversation state and active speech are cleared when changing agents, and Telegram sharing and echo preferences are stored separately for each agent.
Client isolation: Telegram echo uses the selected client’s bot and chat binding. Device credentials are scoped to their client and cannot inherit the operator’s Claude credentials.
Telegram delivery correction, deployed on the relay: for Mac-initiated requests, Echo to Telegram on sends one copy and off sends none. Shared-session behavior remains independent of Echo. Messages sent directly to the Telegram bot still receive replies. This server-side correction does not require another app build.
Complete installer: use ClawSight-0.9.5.7-Complete.dmg. It contains the app, setup guide, four existing skill folders and their scripts, and beta terms. The bundled OpenClaw and Hermes setup resources are for those integrations, not requirements for Claude Managed Agents. The complete DMG is signed, notarized, stapled, and Gatekeeper-verified.
Existing Claude agent, environment, vault, API key, and memory configuration can be retained. Activation, voice, and corrected Echo behavior passed testing under a separate macOS user account; each client installation still needs its own approval and onboarding checks.