Beeper CLI

PassAudited by ClawScan on May 10, 2026.

Overview

This is a straightforward Beeper CLI guide, but it can access and modify private messages through a user-provided Beeper API token.

Before installing, make sure you trust the beeper-cli binary and are comfortable letting the agent use a Beeper API token. Use it for explicit chat/message tasks, and require confirmation before any message sending, editing, chat changes, or file upload/download.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Note

ASI03: Identity and Privilege Abuse

What this means

If installed and used, the agent can use the token-backed CLI to read/search chats and send or modify messages in the user's Beeper account.

Why it was flagged

The skill requires a Beeper API token, which is expected for this integration but grants access to the user's Beeper Desktop account and messages.

Skill content

Env var: `BEEPER_ACCESS_TOKEN` set (get from Beeper Desktop: Settings > Developers > API Access Token)

Recommendation

Only use this skill with a Beeper token you are comfortable delegating to the agent, keep the token secure, and revoke or rotate it if no longer needed.

Note

ASI02: Tool Misuse and Exploitation

What this means

A mistaken or overly broad instruction could send, edit, archive, create, or attach content in the user's messaging account.

Why it was flagged

The documented CLI commands include actions that can mutate chats, send or edit messages, and upload files. These are related to the Beeper purpose, but they are high-impact actions if run without clear user intent.

Skill content

beeper chats archive "<chatID>" ... beeper chats create ... beeper messages send ... beeper messages edit ... beeper assets upload /path/to/image.png

Recommendation

Require explicit user approval before any send, edit, archive, chat creation, reminder change, upload, or download action, and verify chat IDs and message text before execution.

Note

ASI04: Agentic Supply Chain Vulnerabilities

What this means

Installing an unexpected or changed CLI release could affect what commands the agent is able to run against Beeper.

Why it was flagged

The skill depends on an external CLI installed by the user, and the Go install example uses '@latest' rather than a pinned version. This is normal setup documentation but leaves provenance/version verification to the user.

Skill content

Download from [releases](https://github.com/foeken/beeper-cli/releases), or build:

go install github.com/foeken/beeper-cli@latest

Recommendation

Install beeper-cli from a trusted release, consider pinning a known version, and review the upstream project before providing your Beeper token.