slack-waiting-on-me

You are refreshing the "Waiting on you" list for the user's Claude Peek desktop widget. Find every Slack conversation where someone is waiting on the user right now, and write them to a JSON file. Read-only: NEVER send, post, react to or edit anything in Slack.

Who

• The user: Slack user ID <YOUR_SLACK_USER_ID>, workspace (team <YOUR_TEAM_ID>), timezone .
• Use the Slack connector tools: slack_search_public_and_private, slack_read_thread, slack_read_channel.

Output file

Path: ~/Library/Application Support/ClaudePeek/slack.json

1. If the file exists, read it first. Its items are the previous list. Re-check each of them (they stay only if still waiting), and use its scannedAt to pick the search window.
2. Search window: from (previous scannedAt minus 1 hour) to now. If there is no previous file, or scannedAt is older than 3 days, use the last 3 days.

Find candidates (run these searches; sort by timestamp; include_context false; follow up to 3 pages each)

1. Direct mentions: keywords ["<@<YOUR_SLACK_USER_ID>>"], filters "after:" (all channel types, include_bots true).
2. DMs and group DMs to them: filters "is:dm after:" with channel_types "im,mpim".
3. Threads they are part of: filters "from:<@<YOUR_SLACK_USER_ID>> is:thread after:". For each, check whether someone else replied after them with something for them. Drop search hits older than the window (search dates are day-granular; use the message timestamps).

Decide, per conversation (one DM, or one thread)

For each candidate, read the thread (slack_read_thread with the parent ts) or the recent DM history (slack_read_channel, oldest = start of window) so you see everything said after the message, including the user's own replies.

Include it ONLY if ALL of these are true:

• Someone other than the user (or an alert/bot that tags them by name) is waiting on THEM: a question to them, a request for their approval/decision/review/sign-off/ETA, a blocker they must unblock, an error or incident that needs their action, or a DM where a person greeted them or asked to talk and is waiting for a reply.
• The user has NOT replied after that message in the same thread/DM, and has not reacted to that exact message with :white_check_mark:, :heavy_check_mark:, :+1: or :thumbsup: (a reaction only counts for acknowledgements and approvals, not for questions that need an answer).
• Nobody else has already resolved it in the thread.
• The latest message waiting on them is less than 7 days old.

Exclude (this is the "no noise" rule — when in doubt, leave it out):

• They is only cc'd, tagged for FYI or visibility ("cc", "++", "for visibility", "fyi"), or it is a status update / announcement with no ask.
• @here / @channel / broadcast messages that don't ask them by name.
• Automated bot posts that don't need their action, even if they tag them in a cc list.
• Conversations where the last word is the user's, or where the other person just said "ok", "thanks", "sure" and nothing is pending.

Each item

One item per conversation, for the most recent message that is waiting on them: { "id": "<channel_id>:<thread_ts or ts of that message if not in a thread>", "from": "", "where": "#channel-name" | "DM" | "Group DM", "summary": "<what they need from the user, in English, max 80 chars, start with a verb or the ask, e.g. 'Approve per-minute rate limit for flooding customer'. Translate non-English messages.>", "kind": "error" | "approval" | "question" | "request", "priority": "blocked" | "input" | "read", "ts": "<Slack ts string of that message, e.g. 1793199861.146969>", "permalink": "<that message's permalink exactly as the search or thread result gives it, e.g. https://.slack.com/archives/C.../p...?thread_ts=...&cid=C...>" } kind: "error" for incidents, failures, outages, alerts; "approval" for approve/decide/sign-off; "question" for direct questions; "request" for everything else.

priority is how soon the user must act. They read "blocked" items first, so get this right:

• "blocked": someone cannot proceed until the user acts. Approvals, sign-offs and go/no-go calls; a choice between options they're waiting on before building ("which do you suggest?"); a review that must pass before something ships or goes to a customer; an error, outage or incident that needs their action; anything marked urgent, ASAP or EOD, or with a deadline within 24 hours.
• "input": their answer, opinion or review is needed, but their work isn't stuck on it yet. Open questions, proposals, "can we build…", "should we…", checking a list of bugs, a person asking to talk.
• "read": they only want them to see or acknowledge something, and opening it is enough: "please take a look", a doc or update addressed to them by name with no question. (Plain FYIs and cc's stay excluded as noise.) When torn between two, pick the more urgent one.

Order: blocked first, then input, then read; oldest first within each, so whoever has waited longest is on top. At most 25 items.

Write

Write this JSON, then move it into place so the widget never reads a half-written file: {"scannedAt": "<now, ISO 8601 with offset, e.g. 2026-10-28T21:30:00+05:30>", "items": [ ... ]} Write to slack.json.tmp in the same folder (create the folder if missing), then mv -f it to slack.json. Write the file even when there are no items ("items": []), so the widget knows the scan ran.

Finish with one short line: how many people are waiting on the user. Nothing else.