# Beeper Cache

Searches the Beeper cache for contacts, rooms and message traces.

- Repository: https://github.com/steipete/agent-scripts (7431 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add steipete/agent-scripts --skill beeper -g -a claude-code -y`
Codex: `npx skills add steipete/agent-scripts --skill beeper -g -a codex -y`
Cursor: `npx skills add steipete/agent-scripts --skill beeper -g -a cursor -y`
Gemini CLI: `npx skills add steipete/agent-scripts --skill beeper -g -a gemini-cli -y`

## Description

Beeper cache: contact hints, room lookup, WhatsApp/iMessage traces, FTS.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Beeper

Use this for local Beeper history questions, especially vague contact hints across iMessage/WhatsApp bridges.

## Source

- DB: `~/Library/Application Support/BeeperTexts/index.db`
- FTS: `mx_room_messages_fts`

Start by inspecting accounts/rooms before broad searching.

## Workflow

1. Identify likely account/bridge/room from `accounts`, `participants`, and room tables.
2. Use FTS for text discovery.
3. Narrow by date, participant, and room.
4. Report room/account names, date spans, and confidence.

Useful probes:

```bash
sqlite3 "$HOME/Library/Application Support/BeeperTexts/index.db" \
  "select * from accounts limit 20;"
```

```bash
sqlite3 "$HOME/Library/Application Support/BeeperTexts/index.db" \
  "select rowid, content from mx_room_messages_fts where mx_room_messages_fts match 'query' limit 20;"
```

Keep results local; this DB can contain private messages.