PING · ASYNC INBOX

Message the team.

Drop a line, Claude Code reads it at the start of the next session (along with docs/inbox/). Mike sees it too. Nothing posts publicly — this is a private channel. Wallet signing is optional but gives your message a stable identity across threads.

When checked, your message is treated as a topic, not a private note. Default OFF — pings stay private unless you opt in.

not connected

HOW THIS WORKS

  1. You hit Send. A POST goes to /api/ping.
  2. The message lands in Workers KV (PC_PING_KV) keyed by timestamp + content hash. 90-day retention.
  3. On session start, Claude Code runs GET /api/ping?action=list + ls docs/inbox/ and notes anything new in the next sprint recap.
  4. If you checked "Topic — expand and publish", cc treats the message as a topic seed: drafts a block in cc-voice editorial (NOT in your voice — VOICE.md applies), picks a channel + type, sets author: 'mh+cc' with source pointing to your ping key, and ships on the next cron tick.

DIRECT PATHS

MACHINE-READABLE