中文導讀（編輯整理）
辨識到驗簽安裝與 HTTP 防護；提醒敏感對話存取、遠端權限及 hosted 用戶端信任。未驗證發行二進位檔。
實際閱讀範圍：README、權限／Cloud 文件、安裝與 HTTP 防護；無法取得發行 manifest。
這份回覆針對固定來源 239adc8ad 與 v2.1.2。該來源的 README 仍寫 v2.1.1，後來主線已改為 v2.1.2；這不代表 v2.1.2 發行檔缺失。閱讀者未追蹤的認證／換鑰接線，不等於已證實該機制不存在。
下載完整英文原文 · SHA-256 307d8d934ab504d2bba17d2e10fd22fa230c1e3dd9188689390bd6ef3e45ab54
完整英文原始回覆（未翻譯）
Yes—there is meaningful security risk because Clawdline can read sensitive development data and enable remote control of your computer. My limited review found useful safeguards, but it does not establish that v2.1.2 is safe to install.
The main risks are:
- Sensitive information exposure. It reads Claude/Codex conversations, terminal screens and project files used by its features. Credentials or customer data appearing there could become visible in the console. Data-access disclosure
- Remote execution through trusted devices. Devices with operating permission can type into terminals and send agent instructions. A compromised paired browser could therefore affect your computer. Explicitly select read-only access; new Cloud devices without an existing pin default to operating scope. Device permissions
- Cloud endpoint trust. Cloud is optional and documented as end-to-end encrypted, but your computer, paired browsers and the web application remain trusted endpoints. The private backend and production configuration cannot be verified from this repository. Cloud trust boundary
There are substantive protections: the installer verifies an Ed25519 signature using a pinned public key, then checks the archive’s size and SHA-256 before extraction and execution. The HTTP gate also checks authentication and applies origin and permission checks to changes. These reduce risk; signatures still require trusting the publisher and signing key. Installer source, HTTP gate
For v2.1.2 specifically: GitHub associates the release with 239adc8, but I could not retrieve its manifest or independently verify the downloaded binaries, attestations or notarization. Also, the README at that commit installs v2.1.1, so following it verbatim does not install your requested release. Release, README installation steps
My recommendation: first try it under a separate OS account without production credentials, leave Cloud disabled initially, and use explicit read-only grants when remote viewing is needed. Before installing on a sensitive workstation, verify the v2.1.2 release evidence using the project’s verification procedure.
Fixed but not yet released (awaiting review): Nothing.