**Yes—there is meaningful security risk. Treat Clawdline as a remote-control tool with access to your development environment, not merely a session viewer.** I found security safeguards in the sampled source, but cannot certify v2.1.3 as safe.

### Main risks

- **Sensitive-data access and command execution.** It reads agent conversations, project files and terminal content; paired browsers can send instructions and use terminals. Compromise of an authorized endpoint could therefore expose secrets or execute commands with your user’s permissions. [Pinned README](https://github.com/sainteye/clawdline/blob/fcc9059142485514d54683adb769710abb96e1ab/README.md)
- **Cloud encryption does not remove endpoint trust.** The project explicitly notes that malicious browser-delivered application code could disclose plaintext after decryption. Its inventory also identifies traffic metadata, notification-display exposure and network-address disclosure during direct-connection negotiation. That inventory covers an earlier revision, so it is not complete verification of v2.1.3. [Data boundaries](https://github.com/sainteye/clawdline/blob/fcc9059142485514d54683adb769710abb96e1ab/docs/security/data-flows.md)
- **Installer and publisher trust remain necessary.** Signing authenticates a publisher’s release; it does not establish that its code is harmless. The installer ultimately executes the downloaded program’s setup routine. [Installer source](https://github.com/sainteye/clawdline/blob/fcc9059142485514d54683adb769710abb96e1ab/install.sh)

### Positive evidence

The sampled installer verifies an **Ed25519-signed manifest using a pinned key**, then checks the archive’s size and SHA-256 **before extraction or execution**. It also checks an explicitly requested version. These are substantive supply-chain protections. [Installer source](https://github.com/sainteye/clawdline/blob/fcc9059142485514d54683adb769710abb96e1ab/install.sh)

The HTTP gate implements token authentication, same-origin checks for changes and capability checks. Pairing-code access and device management require the machine’s local credential. This is evidence of defensive implementation—not proof that every route is secure. [HTTP gate](https://github.com/sainteye/clawdline/blob/fcc9059142485514d54683adb769710abb96e1ab/internal/transport/http/gate.go), [authentication handlers](https://github.com/sainteye/clawdline/blob/fcc9059142485514d54683adb769710abb96e1ab/internal/transport/http/auth.go)

### My recommendation

**Test it first in a separate OS account or disposable environment without production credentials.** Keep Cloud and terminal integration disabled until needed; pair only trusted devices, avoid public port exposure, and do not bypass Gatekeeper.

For v2.1.3, verify the actual download’s signature, provenance and source revision before running it. The release advertises a signed/notarized DMG, but I did **not** independently verify that artifact. Also, the README at your specified commit still directs installation to **v2.1.2**, so its copy-paste command does not install the release you asked about. [v2.1.3 release](https://github.com/sainteye/clawdline/releases/tag/v2.1.3), [pinned installation instructions](https://github.com/sainteye/clawdline/blob/fcc9059142485514d54683adb769710abb96e1ab/README.md)

**Reading limitations:** This was a limited public-source review, not a full audit. The GitHub tree/API and security website were inaccessible through the available reader; selected raw source files were accessible. I did not install or execute the tool, audit all dependencies, test exploits, verify release binaries, or inspect the private Cloud deployment. **I did not establish a specific exploitable vulnerability, but that is not a clean bill of health.**

Fixed but not yet released (awaiting review): Nothing.